Skip to content

docs(thievery): left-click on a container, display or furniture lock is now logged - #66

Open
ryanbarlow97 wants to merge 2 commits into
mainfrom
docs/thievery-lock-change-logging
Open

ryanbarlow97 wants to merge 2 commits into
mainfrom
docs/thievery-lock-change-logging

Conversation

@ryanbarlow97

@ryanbarlow97 ryanbarlow97 commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor

Documents TF-Minecraft/Thievery#31 (lock state changes logged to CoreProtect) and TF-Minecraft/Thievery#30 (staff can rotate locks they do not own).

  • SYSTEM.md: new Lock change logging section covering the lookup wording (Steve set chest lock to Private., plus (staff override)), that entries are never rolled back, double chests logging on the clicked half, display and furniture changes logging on the supporting block, first-toggle claims not being logged, and the CoreProtect API 14 (25.1.0) requirement. Replaces the outdated "Only the owner rotates state" line.
  • TEST_MATRIX.md: adds L13 (lookup/inspector entries) and L14 (staff override).

python -m unittest discover -s scripts -p 'test_*.py' and python scripts/check-indexes.py pass.

🤖 Generated with Claude Code

ryanbarlow97 and others added 2 commits September 27, 2026 08:52
…is now logged

Shift-left-clicking a lock to cycle its state is logged to CoreProtect
through logLockChange. Document the lookup wording, the staff override
marker, where display and furniture changes are logged, and the API 14
requirement. Also note that staff can rotate locks they do not own, and
add test matrix checks for both.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant