We will build the interactive world map first. It was acceptable to the broadest group, and every region and boss is already in the database.
One player question becomes a shipped tool.
Follow one synthetic Ashen Vigil decision from the contract that fixes the promise through the ballot, the revealed evidence and the team's response to the public outcome.
One decision. Five inspectable states.
The promise is visible before anyone takes part.
Question, participants, method, result meaning, response date, and escape conditions stay together.
The team can build one new tool before the winter season. Players who used the site in the last 30 days may take part. The other tools stay on the board.
- Participants
- Signed-in players who used the site in the last 30 days
- Method
- Approval: mark every tool you would use
- Result
- Implementation-binding
- Response
- 14 days after the ballot opens
- Commitment
- Build the most broadly accepted tool first. Publish any data, licence or schedule blocker.
Approval asks for every option a player would accept.
The same participant rule and the team's commitment stay beside the choice.
Mark every tool you would use this season.
Scores remain hidden while the decision is open.
Broad acceptance is visible without pretending the tally is the decision.
The team still owes an interpretation and a response.
The team publishes the decision and its reading of the evidence.
The response is not detached from the original contract or result.
The build planner also had majority acceptance, so it comes next. The boss timer overlay did not reach broad support, and the game already shows boss timers in play.
The interactive world map is live.
The interactive world map went live before the winter season with every region, boss and sealed door. The build planner is in progress.
The original promise stays attached to every later state.
This expanded view shows the same product facts without turning the result into a detached leaderboard.
Fix the promise before voting starts.
The team states who may take part, how the ballot works, what the result means, and what can block delivery.
Which tool should Ashen Vigil build before the winter season?
The team can build one new tool before the winter season. Players who used the site in the last 30 days may take part. The other tools stay on the board.
- Participants
- Signed-in players who used the site in the last 30 days
- Method
- Approval: mark every tool you would use
- Result
- Implementation-binding
- Response
- 14 days after the ballot opens
- Commitment
- Build the most broadly accepted tool first. Publish any data, licence or schedule blocker.
Ask the players it affects.
The player sees the contract, signs in, and marks every tool they would use.
Reveal evidence, not a naked winner.
Approval counts show broad acceptance. The team still owes an interpretation and a decision.
Explain what the evidence changed.
The response names the decision and how the team read the other credible path.
We will build the interactive world map first. It was acceptable to the broadest group, and every region and boss is already in the database.
The build planner also had majority acceptance, so it comes next. The boss timer overlay did not reach broad support, and the game already shows boss timers in play.
Record what happened after the answer.
The public record closes the loop only when the shipped tool is visible beside the original question.
The interactive world map is live.
The interactive world map went live before the winter season with every region, boss and sealed door. The build planner is in progress.
Write your own contract before you publish it.
Set the question, who takes part, the options, the answer date and what could block delivery.