Spoiler Etiquette

Spoiler etiquette is the set of informal norms a community uses to keep narrative surprises intact for players who have not reached them yet. The core convention is the spoiler tag — a marked block, a warning header, a platform-level blur — part of a broader Taxonomy of community tagging, paired with a convention that matters more than the markup: gating discussion by progress rather than release date. A thread tagged "spoilers for the ending" is no use to a reader three hours in; the healthier norm asks posters to state where they are and matches the reply to that point, which is why long-running communities settle on chapter- or act-based tags instead of one blanket warning. Community wikis tend to run a stricter, opt-in policy than forums do, since a wiki is reference material a reader chooses to open rather than a feed a reader scrolls past.

Tiered hint systems are the designed alternative to the walkthrough. A system offering a vague nudge, then a specific nudge, then the answer, lets a stuck player take only as much help as needed without handing over the Ground Truth outright — the same problem Metroidbrainia design and the Fair-Play Mystery both solve, since a walkthrough for either does not shorten the experience, it deletes it.

Leaks rarely come from the obvious place. Voice-cast credits filed before release name characters nobody has announced; achievement and trophy lists, often live before a review embargo lifts, describe late-game events in their titles; Datamining of a patch surfaces content marketing has not shown; and a staggered rollout, an ordinary consequence of Video Game Localization schedules, lets one region spoil another by existing first. None of these register as spoilers to the platforms that publish them.