Force my plugin to disable before another one?

Discussion in 'Plugin Development' started by orange451, Sep 18, 2012.

Thread Status:
Not open for further replies.
  1. Offline

    orange451

    So I have a human spawning API that I've been writing, and I have a plugin that utilities it.
    Now, it all works really well, however, when the plugins disable (from /stop) the api disables and despawns all human entities in the world, so when MY plugin disables, all the entities are already gone.
    What I need, is for a way to force my plugin to disable before the API disables.
     
  2. Offline

    Jnorr44

    No, what you need is to save data on your NPCs onDisable. Save it to a .bin file.
     
  3. Offline

    orange451

    No, what I need is a way to make sure my current plugin calls the onDisabled method before my API does.
     
  4. Offline

    Sagacious_Zed Bukkit Docs

    Plugins should be disabled in reverse load oder.
     
  5. Offline

    orange451

    Why is it that you can choose what order they're loaded in, but not unloaded in?
    example for load order change (in the yml file):
    softdepend: [SpawnHuman]
     
  6. Offline

    Sagacious_Zed Bukkit Docs

    You can't choose because it is the reverse of what you choose as the load order.
     
  7. Offline

    orange451

    Why does it have to be in reverse order?
    It shouldn't have to be
     
  8. Offline

    Sagacious_Zed Bukkit Docs

    It is that way so that a plugin does not have its dependency pulled out from under them.
     
  9. Offline

    orange451

    I guess that makes sense :/
     
Thread Status:
Not open for further replies.

Share This Page