- Home /
Too subjective and argumentative
Is it a good idea to use static classes?
Is it a good idea to use static classes in Unity? And by this i mean a lot of static classes. Like having a lot of classes named "InputManager", "MapManager", etc. to manage stuff. I know this is not a good idea in object oriented programming, but from what i know, Unity is component based, so is it a good idea to use a lot of static functions in a component based architecture, and if not what is a good architecture for a Unity game? I am also using an event system.
I am also using a static class to communicate between scenes, but i don't think this is a bad idea.
The component system is just another system. Unity uses .NET C# and Boo which are both object oriented program$$anonymous$$g languages. The same principles apply no matter what environment they are in, but none the less this should get asked on the forums
Follow this Question
Related Questions
Unity architecture 3 Answers
How to avoid one engine class controlling the game flow getting too large 3 Answers
Decoupling state & graphics, while sequentially executing graphic updates 1 Answer
How should I integrate the MVC pattern? 1 Answer
Is it good practice to have GameManager singleton in charge of highest level things? 1 Answer