Repository navigation
docs: explain CompanionPets character ownership and recovery - #229
Merged
Merged
Conversation
ryanbarlow97
marked this pull request as ready for review
October 14, 2026 00:39
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 CompanionPets character ownership, preserved relationships, account-wide capacity, reviewed-heir migration and guarded estate transfers. Add staff inspection/creation rules, conservative stopped-server rollback and the isolated Paper native follow/owner-assist/taming fixture.
Source: TF-Minecraft/CompanionPets#41
Validation: navigation/index check passed 903 local links and anchors across 224 Markdown pages; all 5 documentation script tests, strict MkDocs build and
git diff --checkpassed. Describe unresolved ownership and historical receipt holds, the older provider smoke helper's pre-character fixture limitation and the physical inventory/world interruption boundary accurately. No server rollout is included.