tsunanaaAdminSuggestions are welcome. Most of them fail for the same three reasons, so
here is how to avoid them.
Start with the problem, not the feature
The single most common failure is a suggestion that describes a solution and
never says what it fixes.
"Add a teleport command."
We cannot evaluate that. There is nothing to weigh it against.
"Getting back to your base after dying on the other side of the map takes
fifteen minutes, and I usually just log off instead."
Now there is something to work with — and the answer might be a teleport, or a
bed change, or something nobody thought of, but it will address the actual
problem.
Say who it helps and who it hurts
Every change has a loser. A suggestion that names its own downside is taken
far more seriously than one that pretends there isn't one, because it shows
you thought past your own use case.
On HeartSMP especially: anything that makes travel, escape or recovery easier
also makes raiding harder. That is not a reason to say no. It is a reason to
say it out loud.
Check it is not already answered
Search first. The roadmap thread has planned, in progress and *not
promised*, and that third section is where a lot of suggestions already live.
If yours is there, argue for moving it up — that is more useful than a fresh
thread.
How it gets decided
Three questions, in order:
- Does it make the server worse for someone who is not asking for it?
- Does it cost anyone money to keep working? Not just to build.
- Is it pay-to-win? If yes, it is dead, no matter how good it is.
Then it lands somewhere on the roadmap, or gets a written no. A no with a
reason is a real answer. Silence is not, and you should not have to accept it.
Where to post
General, unless it is specific to one mode — then the mode's category, so
the people it affects see it.