SpoilerWarning

ec2-3-133-12-172.us-east-2.compute.amazonaws.com | ToothyWiki | RecentChanges | Login | Webcomic

: "Warning, the following text will tell you something you might not want to know in advance of being told it by the show/game/book/etc."

Note that this alone is probably not sufficient warning unless the spoiler is extremely small. For anything larger than that it is recommended that SpoilerSpace be used or that the spoiler be separated onto its own 'spoilers' sub-page (e.g. /MinorSpoilers?, /MajorSpoilers?, etc.).

After Vitenka's comments on BatmanBegins which he thought were "being nice and vague", is it worth aiming for a bit of a clearer definition here? I know it will vary subjectively a lot, both what one considers spoily and how one reacts to them. But to prevent regrettable browsing occurrences, perhaps some guidelines could be worked out?

AlexChurchill would say that anything indicating an outcome that might be in doubt by partway through should count. For example, indication of what happens to a McGuffin is likely to need a SpoilerWarning (other than "People chase it"). Disclosure of something that becomes a major point when it would have been initially thought to be a minor point also counts. Information of any kind about the climactic ending scenes should probably be avoided.
In thinking about whether a comment about "so-and-so does/doesn't get the girl" would need a SpoilerWarning, I thought that in a lot of cases "so-and-so does get the girl" probably really doesn't need a SpoilerWarning, especially in JamesBond-type cases where you know that's going to happen. But anything to the contrary of this probably should be SpoilerWarninged, because that's against people's expectations. Can this principle be extrapolated? --AC

CategoryTag