tsunanaaAdminThis category has one promise: somebody actually replies here. Making that
easy is mostly about four lines.
The four lines
What you were doing. Not "it broke" — what you were trying to do when it
broke.
What you expected. Obvious to you, not to us.
What happened instead. The exact message if there is one. Copy it, do not
paraphrase it — the difference between two error messages is often the whole
answer.
What you already tried. So nobody spends their reply on something you did
twenty minutes ago.
Details that are almost always relevant
- Your Minecraft version, and whether it is the current one.
- Which mode you were on.
- When it happened, roughly. Timestamps let us look in the logs.
- Whether it happens every time or happened once.
That last one changes everything. "Every time" is a bug. "Once, yesterday" is
usually something transient and gets a different answer.
Formatting an error message
Wrap it in backticks so it stays readable:
```
the exact text here
```
Mark the answer
When something solves it, mark that reply as the solution. Two things
happen: the topic gets a badge so the next person with your problem knows this
one is worth opening, and it leaves the Unsolved tab, so people looking for
something to answer can find the questions that still need it.
Mark the reply that solved it, not the most polite one.
Come back and say what worked
Even if you solved it yourself. A thread that ends with "never mind, fixed it"
is worse than no thread — it shows up in search for the next person and tells
them nothing.
When to use Discord instead
Anything urgent. Server down, cannot connect, rank did not arrive. Discord
answers in minutes; here it might be a day. Come back afterwards and post the
answer if it was something other people will hit.