Repository navigation
Conversation
Each bullet now leads with what changed and what a developer upgrading from 2.0.1 has to do, with the detail in short sentences and nested lists for bullets that cover several cases. Every link, code span, issue number, and SRD quotation is unchanged. Three claims are corrected against the code: a rest checks for wandering monsters on the level's interval, not every turn; a 2.0.1 log that declares a close move or an area spell at a fled group no longer replays; and only sleep, not every hd_budget mode, ignores the area footprint when aimed at a group. Mentions of golden files are cut. Claude-Session: https://claude.ai/code/session_01V7ErtnsmhaP7aLwcfmzohD
Three cold readers found osrlib terms used without a definition, steps a developer must take left implicit, and dangling references between entries. Each term is now defined once where it first appears, by a clause or a link to the API member or docs page that defines it. Each entry that needs a change in a game says so in its first sentences. The replay entry now says how to reproduce a 2.0.1 game, and the withdrawal entry lists its four refusal codes. Claude-Session: https://claude.ai/code/session_01V7ErtnsmhaP7aLwcfmzohD
Each fix answers a question two fresh readers still had. The rest and routine-label entries now state the behavior change and the default. The withdrawal entry names its three new codes. The petrified-party entry is split into cases, with the recovery path marked optional. The replay entry says how to replay under 2.0.1. Several Fixed entries now give the numbers and defaults the readers asked for. The DungeonState.door entry is left for the lead's door fix. Claude-Session: https://claude.ai/code/session_01V7ErtnsmhaP7aLwcfmzohD
Owner
Author
|
Replaced by a pull request from docs/unreleased-changelog, whose commit messages avoid the jargon the maintainer has asked me to drop. The changes are identical. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Unreleased section had grown dense, hard-to-read bullets over the backlog run. This rewrites it for a game developer upgrading from 2.0.1.
What changed
replacement_too_far.How it was checked
A fact checker compared the old and new text against the code, and found no dropped or wrong facts. Then two rounds of readers with no project context read every bullet one at a time and summarized each in their own words. I fixed what they misread or couldn't answer, until their summaries matched the facts.
The
DungeonState.doorbullet will change in a follow-up code fix, because of a door defect found during this pass.https://claude.ai/code/session_01V7ErtnsmhaP7aLwcfmzohD