Releases: Protonull/CivChestTracker
v0.0.3 - Minor updates and fixes
Nightly (Unstable)
Commits
- 6826ca5: Bump to 0.0.2 (Alexander)
- f7c2b48: Fix mixin name (Alexander)
- 5d751f5: Update dependency versions (except Fabric) (Alexander)
- 4a1b5ea: Use shadowed level reference instead of getting it through Minecraft (Alexander)
- 646f7bf: Update Fabric Loom version (Alexander)
- 67ecd31: Update Gradle wrapper (Alexander)
- d8d1449: Ensure plain hover text (Alexander)
- 1fdaf1b: Bump to 0.0.3 (Alexander)
v0.0.2 - Massive simplification
Massively simplifies CivChestTracker.
Prior to this, CivChestTracker attempted to refactor ChestTracker through mixins to coerce an identifier-based storage system rather than a location-based storage system, using the inventory name as the identifier. This meant that players would have to name their chests (or what have you) in anvils. It also required players to specify a container location through a GUI with a raycast-style block selection.
But then I was reminded that /cti messages contain the clicked block's location as hover text and died a little inside. I copium'd that at least my version didn't have the "bug" where, if you clicked on a block and then opened a custom GUI like /config or /ja, you'd have the GUI's name now floating in front of you until you manually delete it from the NBT file. Which tbf is annoying, and is still a problem with this new version, and something I intend to fix at a later time. I'm still reeling though over how much code was unnecessary.
The only problem is that you have to have /cti enabled or otherwise CivChestTracker will not work at all. And there's no real way to test that /cti is enabled because the information is not sent to the client in a way that's legal to read. The client could attempt to send a /cti command, but that's... automatically sending commands to servers upon connection is probably not very wise.