AddonModule#canLoad

[TheAbsolutionism]

Description

This PR aims to add a default method #canLoad(SkriptAddon) within AddonModule allowing addon developers to specify conditions that need to be met in order for the addon to be loaded.
This ensures an addon is not loaded when it should not or can't.

Also, combines the two for loops of init and load into one loop because it simplifies it and there's no need to loop it twice.

---

Target Minecraft Versions: any
Requirements: none
Related Issues: #7539

[Fusezion]

Very nice, much needed, good words, #7541 also completed in this

[APickledWalrus]

Also, combines the two for loops of init and load into one loop because it simplifies it and there's no need to loop it twice.

I'm against this simply because, if we desire to change this, it should be replaced with a most robust load order system. I do not think two loops is a major issue given it provides a basic load order system

[TheAbsolutionism]

I'm against this simply because, if we desire to change this, it should be replaced with a most robust load order system. I do not think two loops is a major issue given it provides a basic load order system

So you're just against the combining the two loops? If so, I can just undo that part alone, but I would believe a canLoad would still need to be called within that loop as well.

[APickledWalrus]

So you're just against the combining the two loops? If so, I can just undo that part alone, but I would believe a canLoad would still need to be called within that loop as well.

Yeah, the canLoad is fine. I would filter a list of the addon modules that can load, and use that for the two loops

[TheAbsolutionism]

Yeah, the canLoad is fine. I would filter a list of the addon modules that can load, and use that for the two loops

Okie dokie, all done

[cheeezburga]

What do we think about shouldLoad instead?