maniator / maniator/verticopolis
[P3] The boot conflict bulletin does not survive a tower swap
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
From the D4 adversarial review (PR #750). The both-moved conflict bulletin is emitted into the BOOT sim''s log. If the player then loads the conflicted slot from the splash picker (or starts a new tower), adoptSim swaps the sim and the explanation is gone at exactly the moment the unexpected slot state matters.
Wanted: re-emit (or re-queue) the conflict bulletins into an adopted sim during the same session, or surface them through a channel that survives adoption.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace adoptSim and the BOOT sim bulletin emission, then reproduce the conflict through the splash picker and by starting a new tower. Check how the conflicted slot state and bulletins are transferred during adoption; done means the conflict explanation remains visible after either swap path in the same session.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100