Nucleus is occasionally not loading properly

[dualspiral]

http://pastebin.com/abK7gt3e
SpongeForge: spongeforge-1.8.9-1808-4.1.0-BETA-1282

Normally, I don't like the idea of backporting to older versions, but in this case, I'm going to look into why there seems to be a failiure when loading Nucleus on said older version with Pixelmon, as there seems to be a problem with Sponge/Forge/Pixelmon that prevents using older versions.

It seems that Nucleus isn't hitting the post-init phase, but there is no indication why.

Excerpts from the forum thread for the rationale:

Alot of us in the pixelmon community have refrained from updating to the latest builds of sponge as they have alot of bugs and I personally have had issues with when upgrading or downgrading; sponge goes and changes the forge blocks in my worlds. from something like pixelmon grass to unknown blocks or from the ruby ore to ruby blocks and so forth; I don't know why sponge likes to change the block data though... its retarded. Sponge should not take it upon themselves to screw with that kind of info, let alone changing it and messing peoples worlds up.

---

I think the issue with that build is that every time a legendary spawns, it crashes the server. That is why most of us are using outdated builds.

(informing you, not saying it is your fault.)

---

the pixelmon devs are pretty aware and they are actually the ones along with ras who've suggested using outdated builds over the newer builds as they're more stable for pixelmon. I had alot of complications with the build 1815 build which caused a memory leak on my server.

[dualspiral]

java.lang.NoClassDefFoundError: org/spongepowered/api/event/game/GameReloadEvent

Just going to write a quick mechanism to check for declared classes before trying to get Guice to load them - this will be useful for x.1 additions.