Repository navigation
docs: explain character-bound warbands and recovery - #230
Merged
Merged
Conversation
ryanbarlow97
marked this pull request as ready for review
October 14, 2026 00:38
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
1 participant
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.
Document recorded-character warband membership, leadership and invitations, outgoing-session cleanup and generation-bound delayed work. Describe reviewed-heir expansion, immutable source/fixed plans, held-file preservation, precise manual recovery and conservative stopped-server rollback while keeping combat account routing and muster deduplication.
Paired implementation: TF-Minecraft/SimpleFactions#164
Validation: five documentation tests passed; 902 local links/anchors across 224 pages and navigation passed. Commands, file formats and capability behavior checked against the paired implementation. Part of RPCharacters#89 stage6c; no deployment changes.