Multiverse-Inventories

878k Downloads

Disabling optionals_for_ungrouped_worlds breaks optionals

lloydtao opened this issue ยท 9 comments

commented

Hey, I'm trying to set up Multiverse so that I have consistency between the world, world_nether and world_the_end dimensions, while remaining separate from lobby.

Toggling last_location will keep the player in the correct dimension, even if they try to teleport to a different dimension. However, it becomes impossible to exit the dimension.

Using /mvm set respawnWorld world, /mv modify set respawnWorld world, /mv tp world, /kill, or even just jumping into the End fountain, will not work. Toggling off last_location and then using the above will put the player in world at their spawn.

I assume something with last_location messes up the world group's spawn.

commented

Is there an estimated time when this will be resolved?

commented

Unfortunately, no, there's no estimate. It's a tricky bug to figure out.

commented

Have you disabled optionals_for_ungrouped_worlds?

commented

Have you disabled optionals_for_ungrouped_worlds?

Yeah, as well as changing the world group's shares from all, to stats and inventory, with optionals_for_ungrouped_worlds both enabled and disabled.

Logs
Enable last_location.
Step into End portal.

2020-05-17 20:03:20 [INFO] [Multiverse-Core-Debug] Player 'TVAsriel' was allowed to go to 'lobby_the_end' because enforceaccess is off.
2020-05-17 20:03:20 [INFO] [Multiverse-Core-Debug] TravelAgent not available for PlayerPortalEvent for TVAsriel
2020-05-17 20:03:20 [INFO] [Multiverse-Core-Debug] Player 'TVAsriel' was allowed to go to 'lobby_the_end' because enforceaccess is off.
2020-05-17 20:03:20 [INFO] [Multiverse-Core-Debug] MV-Core is allowing Player 'TVAsriel' to go to 'lobby_the_end'.
2020-05-17 20:03:20 [INFO] [Multiverse-Core-Debug] MV-Core is allowing Player 'TVAsriel' to go to 'lobby_the_end'.
2020-05-17 20:03:20 [INFO] [Multiverse-Core-Debug] Handling gamemode for player: TVAsriel, Changing to SURVIVAL

Use /kill.
Respawn.

2020-05-17 20:04:04 [INFO] [Multiverse-Core-Debug] MV-Core is allowing Player 'TVAsriel' to go to 'world'.
2020-05-17 20:04:04 [INFO] [Multiverse-Core-Debug] Handling gamemode for player: TVAsriel, Changing to SURVIVAL
2020-05-17 20:04:04 [INFO] [Multiverse-Core-Debug] Player 'TVAsriel' was allowed to go to 'lobby_the_end' because enforceaccess is off.
2020-05-17 20:04:04 [INFO] [Multiverse-Core-Debug] TravelAgent not available for PlayerPortalEvent for TVAsriel
2020-05-17 20:04:04 [INFO] [Multiverse-Core-Debug] Player 'TVAsriel' was allowed to go to 'lobby_the_end' because enforceaccess is off.
2020-05-17 20:04:04 [INFO] [Multiverse-Core-Debug] MV-Core is allowing Player 'TVAsriel' to go to 'lobby_the_end'.
2020-05-17 20:04:04 [INFO] [Multiverse-Core-Debug] MV-Core is allowing Player 'TVAsriel' to go to 'lobby_the_end'.
2020-05-17 20:04:05 [INFO] [Multiverse-Core-Debug] Handling gamemode for player: TVAsriel, Changing to SURVIVAL

Still in The End.
Disable last_location.
Use /kill.

2020-05-17 20:05:26 [INFO] [Multiverse-Core-Debug] Handling gamemode for player: TVAsriel, Changing to SURVIVAL

Back in World, but not at spawn point ("Your home bed was missing or obstructed").
Use /kill again.

SURVIVAL
2020-05-17 20:06:03 [INFO] [Multiverse-Core-Debug] Spawning TVAsriel at their bed

Spawn at my bed in World.

Something must be wrong here:

  • The fact that dying in The End takes me back to World but not to my bed, and dying in World takes me to my bed.
  • The fact that changing world within a world group while last_location is enabled takes you straight back to that world.

These don't sound like expected behaviours.

commented

This is known issue we're working on right now, which is that optional sharables do not work as expected when optionals_for_ungrouped_worlds is disabled. Sorry for the trouble.

commented

This is known issue we're working on right now, which is that optional sharables do not work as expected when optionals_for_ungrouped_worlds is disabled. Sorry for the trouble.

It's cool, thank you for the quick responses.

commented

This should be fixed in version 4.2.2.

commented

I have an experimental fix for this issue available in this test build. But please read the warning.

commented

This should be fixed in our latest CI build. It'd be nice if someone could confirm.