Repository navigation
fix: keep artifacts as items and follow catalog item changes - #26
Conversation
Recovered artifacts can no longer be placed as blocks. A placed block loses the archive tag, so the player is told that artifacts only go on displays. Item frames and shelves keep the whole stack. Plain items on the same base material still place normally. Finds still in the ground re-pick their item, with the same stable seed, when the catalog no longer lists the item stored on them. Without this, existing sites would keep producing the old vanilla items after a catalog switch. Recovered finds keep the item they became. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
@coderabbitai review |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Summary
Merge Risk: ⚪ Minimal · up to No actionable merge-blocking risk is established; the change is mergeable after normal checks.
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
✅ Action performedReview finished.
|
Summary
Artifacts can only be placed on displays.Displays (item frames, shelves) keep the whole stack. Plain items on the same base material place as usual. The check lives inRecoveredFindListener#onPlace.The second change matters for the switch from vanilla items to MMOItems (TF-Minecraft/ServerAssets#54): TFMC Main has 642 hidden finds that store the old vanilla tokens and would otherwise keep producing them.
Tests
RecoveredFindListenerTest.artifactsCannotBePlacedButPlainItemsOnTheSameBaseCanRecoveredFindItemTest.piecesStillInTheGroundFollowACatalogChangeButRecoveredPiecesKeepTheirItemmvn verifyon Windows: all tests pass except twoSiteRepositoryTestfilesystem-permission tests that fail locally without this change as well.🤖 Generated with Claude Code