Game Simplification

Abstract

Problem: Games increasingly add features that make them easier to use β€” yellow-painted climbable surfaces, aim assist, map icons β€” but many players label these as "handholding." Where should designers draw the line?

Approach: Tim Cain examines the full spectrum of game simplification, from subtle aiming reticles to bullet magnetism to microtransactions, and explores the designer's dilemma: should you add features that increase sales even when vocal players say they don't want them?

Findings: Handholding exists on a continuum, and every player draws their personal "too much" line at a different point. Players often say they don't want simplification features but then use them and preferentially buy games that include them. Many simplification features overlap with genuine accessibility needs.

Key insight: The best approach is to build the base game as the designer intends it, then provide options β€” accessibility options for players who physically need them, and difficulty/simplification toggles for those who want them β€” rather than arguing about whether simplification should exist at all.

Source: https://www.youtube.com/watch?v=lEyMipiH7qE

The Designer's Eternal Dilemma

Game simplification refers to features that make games easier to use but that some players perceive as handholding. This tension has always existed in game design: no matter how many clues you provide about where to go or what to do, some players rage-quit in frustration because it wasn't enough, while others complain it was insultingly obvious.

The dilemma has sharpened in profit-driven times. The core question: should a designer add a feature that increases game sales even if players say they don't want it?

The Yellow Paint Example

The now-infamous yellow paint on climbable surfaces is a perfect case study. It adds zero functionality β€” the surface is climbable whether it's painted or not. All it does is make it easier for the player to identify where to go. For players with color blindness (like Tim himself), the yellow may not even be distinguishable from the surrounding gray rock. It's pure visual signposting.

The Handholding Spectrum (Shooting as a Case Study)

Tim walks through the full spectrum using shooting mechanics as an example, from least to most "handholdy":

Aiming Reticles

Nearly every shooter has a crosshair showing where your bullet will land. There's no reticle in real life β€” this is a form of simplification. Almost nobody complains about it, and most would complain if it were absent.

Aim Assist

Takes multiple forms:

  • Sticky aim β€” the reticle "remembers" the last target you aimed at and still hits it even if you've drifted slightly off
  • Reticle magnetism β€” the crosshair physically sticks to and follows targets you pass over
  • Enlarged hitboxes β€” creatures have bigger-than-visual hit areas; higher "aim assist" settings simply mean bigger invisible hitboxes

Bullet Magnetism

The most extreme form: your bullet literally curves toward a nearby enemy you never actually aimed at. The projectile re-aims itself mid-trajectory.

These features were largely introduced because console controllers offer far less precision than a mouse, making PC vs. console PvP wildly unbalanced. Now players not only expect them β€” they justify them. Everyone has a point on the continuum where everything below is "fine" and everything above is "handholding," but that point varies wildly between players.

The Behavioral Paradox

Players often say they don't want simplification features, but their behavior tells a different story:

  • They use the features when available
  • They buy games that include them over games that don't
  • This pattern extends beyond handholding to difficulty sliders, story modes, and even microtransactions

This creates a real design tension: do you listen to what players say, or what they do?

Common Objections

The main objections to game simplification:

  • It reduces challenge β€” and does so differently depending on whether individual players enable the options
  • Nobody should have access to it β€” some argue everyone should play the same game the same way. Tim finds this argument understandable for competitive PvP but puzzling for single-player games
  • "Don't give me the option, I can't control myself" β€” Tim finds this one particularly unconvincing

The Accessibility Overlap

Many simplification features cross into genuine accessibility territory. Without color blindness options, Tim literally cannot play certain games. Without aim assist, some players physically cannot engage with shooters. What looks like handholding to one player may be the difference between playable and unplayable for another.

Tim's Design Approach

Tim's recommended approach:

  1. Build the base game β€” either with no options or with defaults set to the designer's intended experience
  2. Provide accessibility options β€” so players who physically need changes can play at all
  3. Provide difficulty/simplification options β€” making things easier to notice or perform, not adding new capabilities, just lowering the barrier
  4. Accept the spectrum β€” no matter what you choose, some players will say it's too much and others will say it's not enough

Game simplification is ultimately no different from any other design decision. You decide your design point of view, build to it, and give players room to adjust.