4 ms·
You can't do this for games. Sometimes a game needs a particular feature that has a ton of states and complexity. The only thing you can do is 1)Mitigate that
by seivan 12y ago
You can't do this for games. Sometimes a game needs a particular feature that has a ton of states and complexity.
The only thing you can do is
1)Mitigate that by isolate it
2)Separation of concern
You could have a component that's fuck-all complex, but as long as it's a single, isolated component, that can be disabled by
messedUpComponent.isEnabled = false, then I'm ok.
- yuliyp 12y agoYou can't do what for games? Avoid complexity? You can certainly try! Some bits of complexity will creep in. The important thing is to be aware of the cost and judge it appropriately, don't give low estimates for complexity-adding features. Include efforts to refactor complex stuff in the time budget. This is the same for games as other things.
- ars 12y ago> You can't do this for games. Sure you can. For example people need to move around in the game. You can add rideable objects - or not. Usually you don't need to ride something for the game - it's just cool. So this is complexity you can remove. You can take it a second step - assume riding is required. Do you want various types? Say you ride a horse - do you need multiple colors and sizes of horses? Or something as simple as allowing the character to change hats.