When attempting to use LocationSerializer.getLocation but such world does not exist, it would attempt to create a new world out of it. But I find myself that this somehow causes conflicts and overrides existing worlds into generating a new one. Maybe the recent minecraft update on dimension changes have something to do with it?
Regardless, I'm not really sure what benefits there are into creating a new world when it's only a generic world that's unworkable for a game. There is an exception that having Multiverse-Core plugin does not attempt to create a new world, while I have my own world management plugin to handle it in my server, so really there should be an option in config to allow disable world creation, instead of only taking into account with Multiverse-Core.
Also, if such world doesn't exist and plugin does not create a new world, LocationSerializer.getLocation really should be returning null instead of "valid" Location with a null world, which causes error log all over the place in code that thinks location is "valid" to be used.
When attempting to use
LocationSerializer.getLocationbut such world does not exist, it would attempt to create a new world out of it. But I find myself that this somehow causes conflicts and overrides existing worlds into generating a new one. Maybe the recent minecraft update on dimension changes have something to do with it?Regardless, I'm not really sure what benefits there are into creating a new world when it's only a generic world that's unworkable for a game. There is an exception that having
Multiverse-Coreplugin does not attempt to create a new world, while I have my own world management plugin to handle it in my server, so really there should be an option in config to allow disable world creation, instead of only taking into account withMultiverse-Core.Also, if such world doesn't exist and plugin does not create a new world,
LocationSerializer.getLocationreally should be returning null instead of "valid"Locationwith a null world, which causes error log all over the place in code that thinks location is "valid" to be used.