Thank you very mucho for all your comments, I liked the idea on Performance vs Maintainability, also because a lot of the code I do is also read by other team members so it's important to have maintanable code
I'll take a look at the Game Engine book
Until know there's no clear best one, it appears as everyone has different approaches, that's what I am searching, how people create the architecture of the code.
Does anyone has an example on how MVC pattern will work in a videogame? particulary on Unity
No idea about unity, but:
- You can think about your game state Update function as Controller.
- You can think of your Draw as View.
- You can think of your game objects as Model.
The main point here is to never Draw from Controller or Model, never Update game state from View, keeping game-state related things only in Model.
Separation of Concerns.