Repository navigation
fix: reword player messages in character - #30
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)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 0 remain after this review. 📝 SummarySummary by CodeRabbit
WalkthroughGoldsmith access denials now use a shared message constant in permission checks and station interactions. Feedback for excess materials, unneeded materials, and invalid tools has revised wording. Permission-denial tests now check the exact message. ChangesGoldsmith messages
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~5 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to Goldsmith denials now use profession-specific wording, while the interaction behavior remains unchanged. No material merge risk is established.
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.
All four skill checks share one constant,
Permissions.NOT_SKILLED_GOLDSMITH.Before and after
Colour codes are omitted; the code keeps them.
Testing
mvn -o verifypasses: 99 tests, 0 failures.🤖 Generated with Claude Code