Repository navigation
Document member positions and moving and attacking for 2.3.0 - #221
Merged
Merged
Conversation
The adaptations register now describes the battle round as issue #209 built it. Each member has a place on the range track, the party line moves back when the party falls behind it, and each combatant moves at its encounter rate. A member can close and attack in one round, a caster can't move, and a melee attack that position stops fizzles. Monsters close on the nearest member they can see, strike only their front rank within 5', and close and attack in one round. Monster missiles resolve at 5', NPC archers shoot at the first row, and areas and breath cover rows by distance. The view reports light and sight without refusing anything. The withdrawal, back-stab, area footprint, default policy, gaze, ring of protection, and formation width entries now match the code, and each entry names the SRD text and the tests that check it. The changelog's Unreleased section adds the bullets for #209, written for a game developer upgrading from 2.2.0. The spec's battle bullets and the views and ruleset guides no longer describe ranks by marching order or a close that moves the whole party, and the views guide points battle screens at each group's front_rank and at preview_battle_round. Claude-Session: https://claude.ai/code/session_01V7ErtnsmhaP7aLwcfmzohD
A reader new to the project read the battle section and the views guide one paragraph at a time. These fixes answer what it found unclear: the forms of a move on a declaration, the view fields for declarers, held members, and reloading, what a battle screen redraws after a formation move or a shift of the party line, the order of the round's steps, the trade's conditions, what "pass" means, what a fizzle is and which event reports each kind, and whether a blind member can be in seen_by. Claude-Session: https://claude.ai/code/session_01V7ErtnsmhaP7aLwcfmzohD
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.
This documents osrlib 2.3.0's battle changes from issue #209 for game developers.
docs/adaptations.md: the battle round entries now cover each member's place on the range track, moving and attacking in one round, ranks by distance, how monsters close and whom they reach, areas by distance, the formation width rule, light and sight in the view, and the melee fizzle. Each entry quotes the OSE SRD and names the tests that check it. The entries say plainly where osrlib reads the SRD more strictly, such as an attack with a fighting withdrawal, and where an SRD reader will expect something else, such as monster bows reaching the back row.CHANGELOG.md: the[Unreleased]bullets for Let party members stand at different distances from a monster group in a battle #209, beside the existing quest-item bullet. They cover what's new, what changed meaning (aclosemoves only its member,replacement_idonly trades places, monsters close and attack a round sooner), the codes added and removed, the new view fields, andpreview_battle_round.docs/spec.md: two battle bullets that had become false.docs/guides/views-and-visibility.mdanddocs/guides/ruleset-options.md: the new view fields, the per-groupfront_rank, the dry run, and what turning offformation_width_limitdoes.A reader new to the project read the battle section and the views guide, and a fix pass answered what it found unclear.
https://claude.ai/code/session_01V7ErtnsmhaP7aLwcfmzohD