English
Français
Deutsch
Español
Português
Italiano
Polski
Русский
Türkçe
日本語
한국어
中文（台灣）
中文（中国）
हिन्दी
Connect
Should I say it? The test
You have a solution, a shortcut, a remark. Before it goes into chat: five questions, one verdict.
1 / 5
Did anyone ask for your input?
2 / 5
Is there a real risk? A password, an address, personal information showing on screen.
3 / 5
Does your message reveal something the game has not shown yet?
4 / 5
Is it a choice, or is it being stuck?
5 / 5
If nobody says anything, will they work it out alone?
Verdict
Answer, it is for you.
This is the one case where the answer is a plain yes. Answer what was actually asked, not what you wish had been asked, and stop there.
Verdict
Say it right away.
Safety comes before chat etiquette. One calm message, once: “your password is on screen”. Not ten, not in capitals, no panic.
Verdict
That is a spoiler, even wrapped as advice.
“Watch out for the corridor on the right” already says what is in it. What the game has not shown yet is not yours to give: the discovery is exactly what people came to watch.
Verdict
They decided to paint their base red.
Then you have nothing to say. It is their base, their red, their stream. A colour, a build or an order of play is not a mistake to be corrected: it is someone playing their own way, which is precisely what you came to watch.
Verdict
Stay quiet for two minutes.
You may just have saved the best moment of the stream. The “ohhh of course!” of someone who has finally understood beats every message in chat — and it can only happen once.
Verdict
Offer, and take the no.
Twenty minutes of being stuck earns a “can I help?”, not a solution dropped in one go. They will say yes, or they will say no, and the no deserves as much respect as the yes.