We hit a problem with Residence because it force-enables Multiverse-Core out of order from when it should be enabled according to the contract plugins have with the Server via plugin.yml declarations. For example, if the load order of plugins is:
Residence
BentoBox (has a loadbefore: Multiverse-Core in plugin.yml)
Multiverse-Core
The enable order actually becomes:
Residence / Multiverse-Core (Residence forces MV to enable here as a part of Residence enabling)
BentoBox
The problem with this is that some plugins, like BentoBox, have a loadbefore dependency on MultiverseCore in plugin.yml because they contain a world generator or many world generators. If MV starts before they exist, then it throws errors.
Expected
Ideally, add Multiverse-Core as a softdepend in your plugin.yml so that the Server will correctly load in this order:
We hit a problem with Residence because it force-enables Multiverse-Core out of order from when it should be enabled according to the contract plugins have with the Server via plugin.yml declarations. For example, if the load order of plugins is:
The enable order actually becomes:
The problem with this is that some plugins, like BentoBox, have a loadbefore dependency on MultiverseCore in plugin.yml because they contain a world generator or many world generators. If MV starts before they exist, then it throws errors.
Expected Ideally, add Multiverse-Core as a softdepend in your plugin.yml so that the Server will correctly load in this order:
Thanks!