Multiverse autoload: false incompatibility

[Kryniowesegryderiusz]

Expected behavior

Worlds loading as soon as possible or at least before MV5.

Observed/Actual behavior

Since MV5 hook disables auto-load the Bentobox handles world loading by itself. The problem is most of multiworld aware plugins depend on multiverse and on the fact that after MV5 is enabled all additional worlds are already loaded and accessible. So when BB disable MV5 autoload and postpone world loading many plugins cannot load or deserialize locations.

Steps/models to reproduce

BentoBox version

01.10 05:07:07 [Server] INFO Running PAPER 26.3 .
01.10 05:07:07 [Server] INFO (26.3-9fbed58 (MC: 26.3))
01.10 05:07:07 [Server] INFO BentoBox version: 3.23.1
01.10 05:07:07 [Server] INFO Database: MARIADB
01.10 05:07:07 [Server] INFO Loaded Game Worlds:
01.10 05:07:07 [Server] INFO caveblock ( CaveBlock ): Świat, Piekło, End
01.10 05:07:07 [Server] INFO skyblock ( SkyBlock ): Świat, Piekło, End
01.10 05:07:07 [Server] INFO waterblock ( WaterBlock ): Świat, Piekło, End
01.10 05:07:07 [Server] INFO Loaded Addons:
01.10 05:07:07 [Server] INFO AcidIsland 1.20.1-SNAPSHOT-LOCAL ( ENABLED )
01.10 05:07:07 [Server] INFO Biomes 2.2.1 ( ENABLED )
01.10 05:07:07 [Server] INFO Border 4.8.2 ( ENABLED )
01.10 05:07:07 [Server] INFO BSkyBlock 1.19.1 ( ENABLED )
01.10 05:07:07 [Server] INFO CaveBlock 1.20.1 ( ENABLED )
01.10 05:07:07 [Server] INFO DimensionalTrees 1.8.0 ( ENABLED )
01.10 05:07:07 [Server] INFO Level 2.22.0 ( ENABLED )
01.10 05:07:07 [Server] INFO Limits 1.27.1 ( ENABLED )
01.10 05:07:07 [Server] INFO SkyIslandUpgrades 0.1 ( ENABLED )

Plugin list

No response

Other

No response

[tastybento]

Thanks, you're right, and the cause is on our side.

BentoBox creates and loads its own worlds on the first server tick, after every plugin has enabled. To stop Multiverse racing it, the hook registers BentoBox worlds as auto-load: false. Until 3.22.0 that flag was only applied on first import, so long-running servers kept auto-load: true. Multiverse then loaded the worlds early and plugins that enable after it could use them. In 3.22.0 (while fixing #3037) we started forcing auto-load: false on every startup, which removed that early loading and also undid any manual change.

Fix (f38087a, in 3.23.3): BentoBox now sets auto-load: false only when it registers a world with Multiverse for the first time, and leaves existing entries alone. The default is still false, but you can turn it back on and it will stay on:

/mv modify caveblock set auto-load true
/mv modify caveblock_nether set auto-load true
/mv modify caveblock_the_end set auto-load true
/mv modify skyblock set auto-load true
/mv modify skyblock_nether set auto-load true
/mv modify skyblock_the_end set auto-load true
/mv modify waterblock set auto-load true
/mv modify waterblock_nether set auto-load true
/mv modify waterblock_the_end set auto-load true

(Names taken from your /bentobox version output. Check plugins/Multiverse-Core/worlds.yml if any of them differ.)

On 3.22.0–3.23.1 BentoBox will reset these to false at every startup, so you need a 3.23.3 build (or a current dev build) for the setting to stick. Your game modes (CaveBlock, BSkyBlock, AcidIsland) build their generators before Multiverse enables, so early loading by Multiverse is safe for them. It is not safe for Boxed.

FAQ entry: BentoBoxWorld/docs#110

[Kryniowesegryderiusz]

Awesome, thanks ^^