Add player-only relationship custom info - #736
Merged
Merged
Conversation
RANGROO
marked this pull request as ready for review
August 25, 2026 03:43
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.
Screenshot
Requested behavior
Add a small Custom Info paragraph field to each relationship. It is empty by default, editable only by the player, and must never be sent to or changed by relationship AI.
Implementation
extended_data.relationships[target].custom_info.custom_infovalue.No database migration is required. Existing relationship data remains compatible.
Validation
RelationshipTypeValidationTest.php: 12 tests, 36 assertions passed.git diff --checkpassed.Review notes
lib/relationship_manager.phpand PR Support distinct profiles for same-named actors #735 inui/api/chim_npc_manager.php; merge conflict review may be required.Deployment and limits
26dcec67d0bd72ba2c4f8f44b380e89914fdb000to/var/www/html/HerikaServer; all five changed-file SHA-256 hashes match and the server/API return HTTP 200.