Repository navigation
fix: reword player messages in character - #28
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 (3)
Limit details: You’ve used all 10 included reviews currently available. 📝 SummarySummary by CodeRabbit
WalkthroughThe permission-denial and unusable-tool messages now use updated wording. Tests check the updated messages. The permission-denial cancellation and cooldown flow remains unchanged. ChangesWoodworking message updates
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The changes update two gameplay messages without a supported indication of altered interaction behavior. No actionable merge risk remains.
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.
Both skill checks share one constant,
Permissions.NOT_SKILLED.Before and after
Colour codes are omitted; the code keeps them.
Testing
mvn -o verifypasses: 31 tests, 0 failures.🤖 Generated with Claude Code