3 ms·

> It is practically always the smallest part of the final product. What do you base this statement on? There are several classes of games where this is definit

• hannasanarion 8y ago
  In what class of game?
  • gmueckl 8y ago
    Adventures and RPGs are the most obvious ones. There, the story-based interactions quickly turn into tons of game logic corner cases that must be handled. Also, the rule sets for RPG character stats and fighting interactions (strengths, weaknesses, immunities, temporary effects, combos...) generally are pretty insane. Oh, and lest we forget: game logic does not stop once you figured out at a high level that X has to happen. It still needs to set up and drive all the presentation that goes with it on top of the pure bookkeeping. The subtleties of this can be really amazing. To just name some trivial things that come to my mind: doors and elevators should stop when players stand in the way, players and objects should move with the platforms they're standing on (harder than it looks, esp. in 3D), enemies can't just be deleted from memory when their health goes below 0 (but their hitboxes might still go away immediately) and so on.
    • TeMPOraL 8y ago
      > It still needs to set up and drive all the presentation that goes with it on top of the pure bookkeeping. Yup, a lot of "game logic" is in fact bookkeeping, i.e. self-inflicted complexity. It's not necessary, but is what happens when you overdo it (though IMO it's more often a symptom of using more frameworks and libraries than less).