Not currently.
Please try this build and let me know if it works
What are you talking about? I know of 2 large pixelmon servers running LATEST build with no issues.
Updating any version tends to change block data also all ore in my world that are forge items (such as ruby ore, ends up changing to ruby blocks); those servers must also have legends disabled from spawning wilderness and bosses disabled. idk.
1 Like
It works, thanks. But still please don’t forget to make a localization file, something simillar to locale.yml, 'cause i am missing good old Essentials for Bukkit which have multi-language/localization support
@Khaoz that doesn’t make any sense and noone has reported such issues. Create a ticket on
Provide the world data and proof that the issue happens so I can verify. Have you tried loading latest Forge 1.8.9 WITHOUT SpongeForge? But still, ALWAYS create a ticket on our github or nothing will be fixed as we are not magical creatures that can read minds.
Release v8.1.7:
Tested on SpongeForge 1380
Changes:
- Bug fixes with teleport commands not working.
Enjoy this Update! 
+tested on SpongeVanilla 328
Should nucleus update as well?
Hello
The Import Folder server root is the Sponge or Essetialcmd.
With Essetialcmd you can import a world in version 1.8.
If we can import a world do I do?.
Nope, because the bug was not a plugin one, it was a Sponge bug, as @blood said.
That fixed the teleport issue.
As an aside:
I checked the EssentialCmds commit history to see if there were any fixes Nucleus might need, just in case. It turns out that v8.1.7 adds /kittycannon and doesn’t have any bug fixes for teleporting in - so the changelog for v8.1.7 is wrong and should read should include:
- Adds
/kittycannon- permission essentialcmds.kittycannon.use
and not “Bug fixes with teleport commands not working.” - Hassan didn’t have to fix his plugin Hassan only had to recompile his plugin, it was never EssentialCmds fault in the first place, blood had to fix Sponge.
EDIT: @blood explains what actually happened below, so whilst it wasn’t a bug on EssentialCmds’ end, it required rebuilding. So, while Hassan wasn’t incorrect in needing to bump a new version, there wasn’t any code bug fixes on EssentialCmds end. This was where confusion lies, I’m sorry for the finger pointing.
I had to break the API for our teleporter implementation. Entity setLocation changed from void to boolean which forces any plugin that uses setLocation to recompile so it was broken =).
1 Like
OK, I’ll accept that and take back what I said about Hassan’s changelog - that makes sense and I’ll apologise for the finger pointing. Sorry @HassanS6000, I’ll update my post accordingly.
However, I thought a break in the API should result in a major version change? A similar thing happened with requiring the EntitySpawnCause for spawning items in - that broke plugins too, even though the major version wasn’t bumped.
@blood Khaoz is certainly not the only one with these issues, and he does make sense, albait information was missing from his comment. You are right, most of the Pixelmon servers owners do not open tickets, as this is generally entities issues that are well known with the SpongeForge/Pixelmon combo. I for one have resisted updating because of those block changes that happened in @Khaoz 's server when he downgraded, and because of the crashes happening when pixelmons spawn without being processed correctly, making the chunk unloadable without a server crash.
Oh there is also a certain version (I do not know which for I have not personally experienced it) that causes a server crash when a Legendary spawns - as you know Legendaries are pixelmons that are triggered by a certain event. Or, another version that makes Ranch Blocks unusable. What I have been experiencing however, is massive memory leaks that often make my players time out. For that reason like many others, I am currently in a very outdated version - SpongeForge 1282 for Forge 1808. Pixelmon servers that I speak to often ended up trying my version to fix the questions previously stated, and it has worked.
Lastly, Pixelmon servers like mine do not have the ressources to constantly update for something to break whenever there is a change in the API, or when there is a serious bug that costs a complete reloading of the world. We understand the issues on the Sponge team’s end, and we accept those as soon as we use SpongeForge. I do need to point out however, that increased communication between the Pixelmon and Sponge communities would be ideal, it would really help all of us here. Pixelmon has a Discord, for which you, and other Sponge devs can pop in and hear and ask about these entity issues that have been causing the majority of your spongeforge downloaders issues. On our end, reporting these issues to Sponge instead of the Plugin devs here would definitely clear it out as well.
Here’s to progress.
1 Like
It’s alright, I see how it could have been confusing. All it needed was a quick rebuild, so there was nothing to push. I didn’t add /kittycannon to the changelog because it needs more testing.
Ah, user testing is the best testing anyway! Get 'em on it!
I can import a world in 1.8 if so with what command?.
I would suggest loading the map in singleplayer first, to 1.8.9.
Then use /world load [name as it appears in the file] - all you need to do is place the world file in the main directory of your server files.
@Rasgnarok Then you need to start creating tickets or nothing will ever be fixed as I already told Khaoz. I did just push a fix for something I guessed at causing the legendary spawn issue. Test the latest build and if there is a problem, CREATE a ticket on GitHub.
I but the new world in which folder at the root of the server?.
Yes, I like it that we can agree to what I have previously said. Though I myself will not be updating to the latest until 1282 becomes a problem for my server - so far it is lovely enough.
Again, here is to mutual communication!