Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Loading of Multiverse-Core by Residence #262

Closed
tastybento opened this issue Jan 31, 2019 · 1 comment
Closed

Loading of Multiverse-Core by Residence #262

tastybento opened this issue Jan 31, 2019 · 1 comment

Comments

@tastybento
Copy link

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:

  1. Residence
  2. BentoBox (has a loadbefore: Multiverse-Core in plugin.yml)
  3. Multiverse-Core

The enable order actually becomes:

  1. Residence / Multiverse-Core (Residence forces MV to enable here as a part of Residence enabling)
  2. 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:

  1. BentoBox (has a loadbefore: Multiverse-Core)
  2. Multiverse-Core
  3. Residence (has a softdepend on MV)

Thanks!

@Zrips
Copy link
Owner

Zrips commented Apr 15, 2019

Will add mutliverse and some other multiverse plugins as soft depend to avoid this issue in future.
a03d65d

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants