37
You're misunderstanding the point of spoiler tags. It does not matter how old a game is (or a movie, book, TV show or other form of narrative art). Putting a deadline on how old something needs to be before it no longer needs spoiler tags is nonsensical if you think about it. It means that anyone who discovers the artwork after that period, be it through age,...
16
Here's the golden rule:
Feel free to spoiler protect things, but if you don't heed the golden rule, you are doing it wrong. An example is this suggested edit of yours; hopefully now you can understand why it was rejected.
I encourage people to edit posts that go astray of this golden rule.
If you get bit by spoilers due to carelessly browsing through ...
10
The spoiler tag has existed in the past, but was deemed problematic and removed:
Spoiler alert: [spoiler] dies
9
I think If you don't put everything in spoiler tags you can go ahead. Basically the most secure ways to tell if something is worth to put into a spoiler tag are:
If you don't know the part and just got spoiled
If you already know the part and it is a major plot twist.
Don't use it on stuff that's already 5+ years old and commonly known. Nobody wants a
...
8
I would not spoiler the whole answer. If you consider all, or most of the answer a spoiler, the question is usually asking for one, and it should be obvious that reading it and its answers can spoil something. I'd add a clear warning at the top of the answer that is sure to catch the reader's attention first, if needed, and only use the spoiler markdown for ...
7
There are no rules for the use of spoilers on Arqade. Use your judgement. In general, if everything in your post, whether it be a question or an answer, then nothing is a spoiler, because it's impossible to determine what's behind that mouseover without the context of a broader answer.
4
EDIT: Implementation feature-request
I've found an idea that is really easy to implement to make this work:
Add <details>, <summary> and the open attribute to the HTML whitelist.
The <details> tag is, by default, a collapsible section with a customizable title. Take a look at some HTML and its output.
<head>
<title>How the &...
3
I don't think we need a separate solution for this.
When you encounter a post that should obviously be spoilered, you can just edit in the spoiler tag yourself and leave a comment for the user.
3
In some cases, you encounter someone in the story at a point where it wouldn't make sense for them to become your companion, but a twist at some point makes it happen. You could consider that a spoiler, but it's up to you. I don't think it's nearly severe enough for anyone to complain about it if you don't use the spoiler markup to hide names.
2
Good spoiler etiquitte also dictates that if you ARE going to be posting spoiler information, and you know what it's spoiling, you warn the person in your answer AND use the spoiler tag. Like this:
Here is my answer, note that it contains spoilers for the Prequel in Scene 3, Part 2, when playing as the combo platter chef.
If I can, I include the answer ...
1
This applies to both questions and answers:
Spoiler Markup should be used to cover up accidental spoilers. Imagine you clicked the question to read about A, and got spoiled about C: plot-related stuff tangential to the question/answer, which is mainly there for context or to build up to a larger point.
The post should be able to stand on its own without ...
1
status-declined* as we no longer have a spoiler tag anyway. Use Spoiler markdown to denote spoilers instead, e.g:
>! spoiler text
resulting in:
Only top voted, non community-wiki answers of a minimum length are eligible
