@Txk I haven’t written a converter, no, but your other issue concerns me. I’ve fixed multiple issues with kits - that should not be happening. I feel like I’m going to have to just start from scratch with the Kits stuff, because it’s just a myriad of fix over fix over fix, and I think we can do better.
However, the fact you have problems with managing the kit once you’ve create the kit does not make sense. Are there any errors or stack traces? Were you running Kits at the same time?
The permission thing - make sure you have nucleus.kit.base too.
As I sometimes do, a shoutout for the community. This plugin was created for the community, and I enjoy the challenge of creating it. I must reiterate that I’m not looking for monetary gain, this is just fun for me. While it’s not perfect, and there have been frustrating bugs at times for you all and I, please be assured that I am doing my best to stamp them out. Thanks to all the reports and help people have given. Thank you all for sticking with me, hopefully I can harden the plugin over the next few releases!
Version 0.13.1 is now available for Minecraft 1.8.9 and 1.10.2
This is a bug fix release that many people will probably welcome!
If a data file fails to save, Nucleus will use a backup to return the previous state of the file, this should prevent files from being blanked, so in case of error, not everything will be lost.
Allow kits to have items that have no enchantments but have the enchantment shine (thanks to @ryantheleach for the report).
I have an issue where I have a general.json file that wont read my warps after updating Nucleus. they are still in the file but completely will not show in game when using /warp list or /warp warpname
I have tried clearing it and just putting back in the warps, however it will not work…
I have also tried going back to the previous version but it wont show on that one either.
[Edit-Fixed] Had to manually recreate the warps ingame going to each location and using my old config to find them. Also updated to 1844 from 1843 build of SpongeForge.
Players who have the correct perms for the kit are not able to use it. Their inventories are also empty at the time. Using the most recent 1.10.2 build.
@Dank_Sinatra@SnowBlitzz The only reason I can think of is that your world UUIDs changed. Are the warps in red when you use /warp list? If you create a new warp, and check the UUID of an old and a new warp, are they the same?
@Nathan_Rabbe It’s not a permission issue, that message is either due to a full inventory, or a kit that has no (redeemable) items in it. If you’re using MC 1.10, run /kit edit on the command, see what’s in the kit.
Pixelmon did some ID changes in beta 10, so when I updated there were still wrong IDs in nucleus’ blacklist (things I’ve blacklisted). After I fixed that the warps are back.
i think this may have been the same issue i was having. Had corruption occur on level_sponge.dat so i reverted to the last backup(from earlier today) and went back to B9 for Pixelmon and its working fine. (having still updated all my mods from earlier)
So apparently upgrading to B10 breaks warps when FML updates the world files.
also worth noting i could see in an old log from B10 that GriefPrevention was throwing a warning confirming this. The error read something like “World Claim data is mismatching for World UUID 848w8ry3iq9ehfhblahblah changing to 84u4jejenjwkejblahblah”
I’m going to rewrite the Blacklist system, and give it its own config file, I think, or even fold it into items.conf to avoid this sort of problem. However, that’s really good to know, thanks - that’s the problem with Beta versions, things change!
@Dank_Sinatra That’s also good to know. I think I ought to start storing the world name as a fallback too - because I think this happens more often then it should.
