fix: reword player messages in character - #23
Conversation
Replace out-of-character wording in gameplay messages (permissions, containers, entities, chunks, plugin tags) with in-world phrasing. Staff commands, usage help and setup errors keep their plain wording. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Limit details: You’ve used all 10 included reviews currently available. 📝 SummarySummary by CodeRabbit
WalkthroughTwo player-facing messages have revised wording: the surgery permission message now refers to skill, and the vision message says the next move will be steadier. ChangesPlayer-facing messages
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Bug fix Suggested reviewers: Merge Risk: ⚪ Minimal · up to This is a wording-only change to two player-facing messages, with no change to permission checks or surgery behavior. The risk of merging is minimal. Servers with their own messages.yml copy need matching edits to see the new text. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 1 system. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
Usage-based review receipt
Note This review exceeded your plan’s limits and used usage-based reviews—free during trial, billed after paid activation unless disabled. Manage usage-based reviews. Comment |
Summary
Rewords player-facing gameplay messages that broke immersion with server terms (permissions, access, containers, entities, chunks, plugin names) so they read in character. Staff and admin commands, usage help and setup errors keep their plain wording. Wording only: no permission checks or message routing change.
Before and after
Colour codes are omitted; the code keeps them.
Live config
Deployed servers keep their own copy of this file, so Dev and Main need a matching edit when this ships:
messages.yml:command-no-permissionandvision-cleared.Testing
mvn -o verifypasses: 7 tests, 0 failures.🤖 Generated with Claude Code