ChestShare+

A stability and correctness release. No new commands or features — everything here fixes real bugs found while shaking out 0.3.2's structure-recovery tooling, several of them critical. If you're running 0.3.2, this is a should-update release.

Critical fixes

• A player's own chest, when placed next to a shared loot/structure chest, could be silently converted into shared storage — and if it was completely empty instead, opening the resulting double chest would crash the server outright. Neither can happen anymore: the ordinary half of a mixed double chest is now never touched, and it opens normally either way.
• Carved Wood, Handcrafted, and similar Container-based modded storage could be silently converted into a shared container the first time a player opened their own freshly-placed one. This was a second instance of the exact bug already fixed in 0.3.1 for Sophisticated Storage, missed the first time because it lived in a different code path. Registration for these now only ever happens through the passive world-gen scan, never on open.
• A newly-shared vanilla-style container could silently fail to persist across a server restart. A missing internal setDirty() call meant a fresh registration looked completely successful for the rest of that session, but was never actually saved — the next restart made it vanish as if it never happened, and whatever registered it (the passive scan, convert, import, or adopt-structure) would just do it again, discarding whatever players had already collected from it.
• A just-registered shared container could be silently deleted the very next time anyone opened it — no restart required. Four places that check whether a container is shared were treating a stale, cached flag as more trustworthy than the real, saved data, and deleted the real data to match the flag whenever the two disagreed. This is what caused /chestshare adopt-structure to report a container "restored" over and over, forever, even within one continuous session.
• The world-generation safety gate — the thing that keeps installing this mod on an existing world from ever sweeping up a player's own modded storage — could be defeated across dimensions. Two different dimensions share the same chunk coordinate system, so a chunk freshly generated in one dimension could get "consumed" by an unrelated, already-existing chunk loading at the same coordinates in another dimension.

Other fixes

• Structure scanning could silently fail on several real, large structures (the regional leagues, team_galactic_hq, stark_mountain, secret_garden, sky_pillar, newmoon_island, fullmoon_island), some by only tens of bytes — an overly conservative read-size cap has been removed for both the structure scan and /chestshare import.

• adopt-structure could confirm a container's contents were genuinely wrong, and then silently fail to fix it anyway. A comparison bug and a write-path bug, both fixed — restoring a confirmed mismatch now actually happens.

• A container correctly shared from a structure could get needlessly rebuilt if its internal bookkeeping drifted out of sync after a chunk reload, discarding a player's in-progress looting. The passive scan no longer does any repairing of already-registered containers at all — reconciliation like this is now something only an explicit admin action does, not something that happens silently on chunk load.

• Sophisticated Storage and CobbleFurnies reflection lookups are now cached per block-entity class instead of repeated on every scan and every right-click — no behavior change, just less redundant reflection work.