A map without saving is over in one game, and if it is never updated nobody minds much - the match was the whole thing. Saving changes that. Players are now carrying tens of hours, and those hours depend on the author staying around.
| 변수 이름 규칙 | Start with names like A10, A11, E20 and the map becomes impossible to tidy later. Use distinguishable names from the beginning, and keep a record outside the map of what each value is. |
|---|---|
| 재화 쪽 점검 | A map that saves - especially one with a leaderboard - will attract macros and hacks. If you are unsure, have someone look at it; that is far easier before release than after. |
| 제작자용 관리 화면 | You need a way to restore a player whose data broke and to stop an account that is causing problems. Requests pile up, and with no way to act on them players read it as abandonment. |
One conflict is guaranteed: the update the author planned and the update the players want are not the same. It would be strange if they were.
On balance specifically, the players are usually more accurate. There is one author and many of them, they are the ones actually playing, and the author spends their time updating rather than inside the game. Following the suggestions alone is not the answer either - the job is making room for both.
Take a request to lower a difficulty at face value and the people who already passed it lose something: the time they spent getting through is worth less. When you lower one, decide at the same time what the people who came before get - leaving that out is a common reason the long-term players go.
The same players are the ones who leave when hacks and macros go unaddressed, because the people who built up honestly are the ones who lose by it. On a map with a leaderboard it becomes a question of whether the board can be believed, and a board nobody believes is a board nobody reads.
Shutting out the obvious cheats