java 8 windows

sorry Jumpin Carrot, took a long break from coding. Ya a ServerLoadEvent listener is one way to do it. If you want to do it without registering a ServerLoadEvent listener you can also schedule a task with a delay of 0 inside of your onEnable(). This works (i think) because tasks don't run until after the server has finished loading. This feels like a much more jankey way of doing things though.

Nevermind.

The solution is to register a ServerLoadEvent listener.

gizmo , could you post your workaround, please?

A ServerEvent that is called when the info message:

"Done (2.059s)! For help, type "help""

is printed would be a good alternative to adding an onEnableLate method.

hmm, nope, i misunderstood your text diagram, however I did misunderstand the order and after re-reading your diagram i understand. However onLoad() is not a viable solution. Having a method named something like onEnableLate with the order:

onLoad STARTUP < onLoad DEFAULT < onEnable STARTUP <<< onEnableLate STARTUP < onEnable DEFAULT

would provide load: startup plugins a way to do tag/datapack things.

I have tried to do e.getWorld().setKeepSpawnInMemory(false); in the onWorldInit(e) event and it does not work unless load: startup is specified. (the method is never called because the worlds have all already initialized by the time the plugin has been enabled)

wouldn't the regular loadtime plugin need to overwrite all of the spawn chunks in order to re-generate them again? since the server preloads (and generates) the spawn chunks before regular load time plugins are enabled.

If onEnable doesn't work, then onLoad won't work for recipes.

I think the advice in that Bukkit post is outdated(2011...), and generators will work for regular load time plugins.

Thanks for clearing up the order for me, as i was under the impression that onLoad() was always called immediately after onEnable(), seems as though i understood it both upside down and backwards.

I will attempt adding the recipes via onLoad() then and if it works then this feature request is invalid and i apologize for wasting your time.

ill reply soon. 

>do you mean that onLoad() is always called when regular plugins are loaded, regardless of if load: startup is specified?

Yes.

onLoad STARTUP < onLoad DEFAULT < onEnable STARTUP <<< onEnable DEFAULT

custom chunk generators and the WorldInitEvent seem to require load: startup in order to  function properly.

an old post on the bukkit forums by dinnerbone from when he added custom chunk generators states that load: startup is to be used.

https://bukkit.org/threads/chunkgenerators-blockpopulators-faq.22795/

im slightly confused by your reply:

do you mean that onLoad() is always called when regular plugins are loaded, regardless of if load: startup is specified?

How come you're using load: startup anyway.
Given this ticket and some other tickets recently, I think it should just be removed.

Bukkit already provides onLoad(..) which fires at the same time as onEnable(..) for STARTUP plugins.

perhaps an onInitialized() method for use with load: startup that is called when the onEnable() method of plugins that do not have load: startup specified or something? Otherwise, just a callback or method that allows plugins to know when the server is prepared enough for things like tags and recipes to be modified.

load: startup is not for the general use case.
The server is not initialized much at all at this point.

I agree it shhouldn't silently fail, but I also don't think it should be allowed (similar to tags... datapacks are only loaded after)