Only happens of mv-inv is install. I am running on ACF beta, but shouldn't be the issue. If possible, do help test with release builds.

Error: https://pastebin.com/h8jTsaS7
version info: https://paste.gg/8a47e759513342f699ba7c0718c7de8a

Possibly some issue with last location, as the issue only happens when last location is enabled.

So after more digging, here is what I found.

Let say we have 2 worlds: default (UID 1) and test (UID 2).

When regening test (UID 2), this happens:

1. Players in test (UID 2) teleports to default (UID 1).
2. World test (UID 2) is unloaded and deleted.
3. A new test (UID 3) is created.
4. Players teleport back to the newly created test (UID 3).

mv-inv caches the PlayerProfile data of test (UID 2) since the player has entered that world before. However, this cache is from test (UID 2) and not the new test (UID 3). This results in shares relating to Location object store such as last_location to have Location#getWorld to be the old test (UID 2) instead of test (UID 3).

5. Player teleports to last_location in test (UID 3).

Here is where the issue occurs, since the Location object in last_location share is for test (UID 2), it is effectively a teleport from test (UID 3) to test (UID 2), triggering a WorldChangedEvent as such:

[11:47:24] [Server thread/INFO]: [Multiverse-Inventories-Debug] FROM WORLD: 310052bb-4f16-4183-9f65-2ebea8832c66
[11:47:24] [Server thread/INFO]: [Multiverse-Inventories-Debug] TO WORLD: 2acb041a-161c-49a7-92e0-a51fb791a6f0
[11:47:24] [Server thread/INFO]: [Multiverse-Inventories-Debug] === Benji_0224 traveling from world: omg to world: omg ===