Thanks for the kind words, it means a lot! The TODO message signifies that something called isn’t implemented; that being said it’s possible for some commands to still work even if some calls fail, as you’ve discovered.
Regarding dontaions, to quote a previous message of mine:
I’m not sure that many of the more complex plugins really work with Pore yet… Any idea how far along Pore really is? It is almost a year from its start date. 30%? 15%? Or will things go more rapidly as sponge is now out?
I’m just trying to figure out how much of a reality Pore really is…
A quick search with IntellIJ reports 2,439 instances of @Override and 1,243 instances of throw new NotImplementedException in blue.lapis.pore.impl, which would imply that about 49% of Bukkit is implemented, However, this is a pretty rough figure and isn’t an terrific representation of the work that still needs to be done. Regardless, it’s at least something quantifiable.
What would it be like if I downloaded and installed the very latest version of pore to my server? I see that it isn’t stable, but is it better to use than the 237th build? Does it have more features?
Whoops, looks like I accidentally broke the build. Failed builds don’t produce artifacts, so currently the artifacts listed on the job’s main page are from #237 rather than #239. Also: typically each build will have more functionality than the last, but they’re all currently considered more or less unstable due to the fact that we’re still relatively early in the development cycle.
As soon as I can get the damn thing to compile, which will hopefully be in a few minutes.
Edit: Just pushed it. This build should implement a good number of entity events, as well as fix projectile launching methods which were previously broken.
Is there a way to have it so plugins that are no yet implemented show up red in the /plugins list? Then it would be a lot easier to figure out which ones work, and I could make a list.
We’d have to essentially analyze every call a plugin makes to see if it’s implemented, and even if we could do that efficiently, most would be red anyway since typically there would be at least 1 unimplemented call in each plugin.
Could the people @ Pore please please work on some more implementation for Essentials 2.x and Groupmanager 2.x especially? I only ask because I would LOVE to have a choice from using PEX which in my opinion is waaay to complicated and non-user friendly, i think a lot of people would benefit from having the option to choose from either SpongePex or the original Groupmanager
I also want to note that i know the people @ PORE are working very very hard and i greatly appreciate all that has been done so far, just would be nice to add Groupmanager to my pore arsenal on my server! thanks to anyone who took the time to read this
I haven’t tested GroupManager yet, but Essentials uses a very large subset of the Bukkit API, so it’s not really possible to target it while implementing. We’re essentially (ha) just going through and implementing what we can currently.
Same, it’s the only reason I plan on really using sponge, without Pore i would just stay on spigot or something, it’s basically the only option for a 1.8 server to operate well with mods.
why i got this error?
Unrecognized option: --tweakClass
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.