How to post a systems question so it gets a useful answer

Systems design questions get vague answers when the post is vague. Bring specifics.

Include:

• What the player does — the actual verbs, second by second
• What the game does back
• Rough numbers, even bad ones. "Enemies have 100 HP, the sword does 25" gives people something concrete to reason about
• What is going wrong. "It feels boring" is a symptom — say when it starts feeling boring

A useful framing: describe your loop as enter → assess → decide → act → consequence → repeat. If you cannot fill in one of those steps, that gap is usually where the design problem lives.