docs: warn against running a second inventory manager - #60
Merged
Conversation
Running InvSwitcher alongside Multiverse-Inventories (or PerWorldInventory, MultiInv, etc.) makes both plugins save and restore the player on every world change, so they overwrite each other's data. The symptom is disappearing items with nothing logged, and it is independent of the InvSwitcher version. Documents the Multiverse-Inventories case, including the two dead ends admins usually hit first - inventory groups do not control whether MV-I handles a world, and `/mv remove` is undone when Multiverse-Core re-registers the worlds on the next restart - plus the working bypass-permission fix. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YXnYDGiASdSUZFtNyS4jbc
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
A server admin reported island inventories being wiped on every world change — get an item on the island, go to the lobby, come back, item gone. They had tested InvSwitcher 1.15.1 and 1.17.1 with identical results, and had ruled out Multiverse-Inventories because none of their BentoBox worlds were in an MV-I inventory group.
Reproduced locally against BentoBox 3.21.1 with MV-Core 5.7.3 + MV-Inventories 5.3.5. It is a plugin conflict, not an InvSwitcher bug.
What the testing showed
With MV-I loaded and the BentoBox worlds in no group, the island inventory was not lost — it was misfiled. All 8 items were written under the lobby storage key and an empty inventory under the island key. Each plugin faithfully saves a player state the other has already rewritten, so nothing is logged and it presents as data loss.
Three things admins are unlikely to work out unaided:
acidisland_worldwhile it was in no group anddefault-ungrouped-worldswasfalse. Groups control which worlds share an inventory./mv removedoes not stick. Multiverse-Core re-registers BentoBox worlds as they load. From the server log: MV-Core enabled at 19:16:29, BentoBox created the worlds at 19:16:30,worlds.ymlwas rewritten at 19:16:31 with all of them back.auto-import-3rd-party-worlds: falseonly suppresses the sweep at MV-Core startup, which runs before BentoBox creates its worlds.Granting
mvinv.bypass.world.<world>(withshare-handling.enable-bypass-permissions: true) fixed it — verified from a cleared database, with InvSwitcher's own store holding the correct island contents afterwards.Changes
README-only. Adds a Do not run two inventory managers section after How to use, so it is found before an admin starts changing InvSwitcher settings that are not the cause. No code changes.
The same content is proposed for the docs site in BentoBoxWorld/docs#80.
🤖 Generated with Claude Code
https://claude.ai/code/session_01YXnYDGiASdSUZFtNyS4jbc