Game design is often a juggling act involving complexity and the audience’s attention. Every game needs some level of complexity to evoke specific emotions in their players, but humans only have a finite amount of attention that they can (or want to) give to your game at any given moment. Each specific element of a game should be evaluated against the added complexity that it will bring to the overall project.
This can create issues, however, especially when designers get attached to mechanics or assets that they might be better off cutting. The old adage “kill your darlings” applies to games just as much to creative writing, but it can be hard to quantify exactly how complex any given mechanic or how it’s purpose in the design affects how the idea should be evaluated.
Another hurdle every designer must eventually cross is deciding whether a specific action is healthier as a player decision. Often, it’s easy to get caught up in a cool sequence of actions and lose sight of the overall vision. Those moments have their place, but it’s also important to weigh the value of that decision point against the player’s overall attention. Is the player overwhelmed with choices? How does this affect the player’s experience? What is the reasoning behind this specific sequence? If the player already had enough to keep track of, adding another decision for them could ruin the experience, no matter how interesting or cool the resulting action could have been.
The goal isn’t always necessarily to simply things either. Decisions represent significant points in gameplay, moments that test the players skills and understanding. Throw too many of these at a player and they can start to feel discouraged, if not completely turned off, by the added opportunity. Humans don’t like messing up, especially when other people are watching, and no matter how you frame the question, there will always be a “right” and “wrong” answer, or at least the player will see it that way. The more questions, the more potential chances for them to embarrass themselves.
Sometimes it’s better to force the player to perform the desired outcome, rather than give them the chance to fail. Other times, creating mechanics that specifically check the players ability to overcome a challenge is the way to go. It’s a blurry line at best.
Recently, I went through the entire design document for my latest project with the intention of reducing the overall complexity of the average game state. What I found was that it was relatively easy to cut back on some mechanics, making certain actions simpler or more directed towards their desired outcome. In most cases, I removed superfluous effects that would only really matter once in a blue moon.
The resulting game should be cleaner, more elegant, and easier to play now that the average game state is less complex and, therefore, easier to grok. Sure, some moves lost a little luster, but it’s a cheap price to pay for the game being more easily approachable. Keep in mind, the first game decides whether a player will keep playing. Making the learning experience as smooth as possible is paramount for creating an experience that players will want to come back to.