Closing does not mean deleting. Lock from changes, if you so clear.
Working on the ore, we contribute to the development.
First try. I’m talking about the section of Ore on the forum. No different from section Releases.
Complete.
But it does mean that because there’s no change updates, that it will be pushed down in the thread. Ie: Go to Plugin Releases - Sponge Forums and find permissionsex. It’s now easier to find other, much less popular permission plugins than pex.
(Guess which one new sponge users who don’t know much about sponge or Ore will use… the first one they see, because they think it’s the most popular.)
Nucleus is already on ore, you’re not contributing to the development by forcing people to go there.
IDK what you mean.
I don’t speak for everyone, but any new thing requires study. Than it is harder to look for pex? The theme of the releases is closed. Last post clearly says where to look for the sequel.
I’m talking about the Ore. Using it we find mistakes. Thereby we give developers the wonderful feedback. Testing. The bug reports.
I’ve already showed a few times with pictures and text.
This is my last message for you. Closed.
If someone is new, they won’t know to look for PEX, they’ll go to the newest things they see. People generally don’t go snooping around everywhere to find some solution, if a shortcut can be taken, they’ll take it, because not taking it usually just wastes time.
Only testing this does is if the discuss page works… users don’t have much interaction with the site or or, unless you’re making the plugin, where there’s more options available for you. Unless the discussion page only breaks every 1000 comments or something, you’re not gonna find mistakes this way.
You showed me that there’s two different places to get updates. Not a single place for them all. A person has plugins that are all (or almost all) on plugin releases (since there’s way more plugins here than on there) will usually check the plugin releases forum. If nucleus moves, they’ll miss those updates unless they go onto the ore page/forum.
Although I do now see that there is a ore thread, was unaware of that, so thanks for that little bit of info. Still slightly [not by much] harder to get to and also like I said before:
#closed
Woah - I didn’t expect this.
I’m keeping this open for now. I’ve not been very good at keeping it up to date - though most owners will also see the Ore thread.
Which reminds me:
Version 0.25.0 is now available!
If you haven’t seen it already, it’s available on Ore (for Minecraft 1.10.2) (for Minecraft 1.11.2) and on Github Releases!
And, you can always pop on our Discord and join the party! https://discord.gg/MC2mAuS
1 Like
OK, now I have that post out of the way, let me say a few things about Ore and why closing this thread isn’t necessarily the right thing to do yet.
Ore is going to be a wonderful tool for managing releases. Windy and the team are doing a fantastic job with it so far. By using Ore now, I’m helping test and refine it. I have found bugs and I have suggestions. By commenting on the Ore thread, yes, there is an element of testing there too. But it’s also far from perfect - and I don’t say that to upset anyone, everyone knows there is a lot to do with it yet.
If you look at my Ore thread, you will see that there are lots of posts that are release notes, I spend a lot of time writing them to try to show case what you can do, and how you do it, because that’s really important in the usability of a plugin! However, as well as having huge release notes, you get them twice because I can’t attach two versions to one Ore release, I have to release a 1.10.2 and 1.11.2 version (but there is a ticket open by someone else to change this, thankfully). So whenever I release a feature release, I break the flow considerably, and it just means that things don’t get responded to.
Here, I have control over that, a quick message, and back on my way.
Because of this, the replies inbetween do get lost, and it’s easier to see the flow of the conversation here. Thus, I will keep it open for the time being, but encourage bugs and feature requests to go to GitHub and quick help can be sought from our Discord channel where I am so thankful for the community that’s been so helpful when I’ve just not been there, or in a bad mood!
4 Likes
Well, that’s all decided. 
error in spongeforge-1.10.2-2221-5.1.0-BETA-2210
Could not pass FMLServerStoppingEvent to Plugin
Link error code :
- Pastebin - http://pastebin.com/YiDpdTuS
- Github - Nucleus: The Ultimate Essentials Plugin · GitHub
error nucleus could not save data
Details :
[10:32:55] [pool-2-thread-9/ERROR] [nucleus]: The file 666fcb5c-d023-482d-8829-c56c9873be65.json has not been saved.
Configuration Node has no children.
[10:32:55] [pool-2-thread-9/ERROR] [nucleus]: Could not save data for 666fcb5c-d023-482d-8829-c56c9873be65
I’m gonna need the output of /nucleus info, please
For those of you using NucleusMixins and SpongeForge
PLEASE make sure that NucleusMixins is in your mods folder. It is essentially the same as a Forge CoreMod - putting it in your plugin folder will ensure that the mixins will not work!
How set blacklist for craft only.
Hey - I’m unsure if you can restrict crafting, but I know that you can restrict possession.
Not in a position to test for you at the moment but depending on how dualspiral set it up, the restriction on possession could potentially disallow crafting as well. If not, people will waste the resources to craft items they can’t pick-up - but as long as you let people know what they can’t make, that’ll just be their own choice.
Nucleus has their modules defined pretty clearly on the website.
Unsure on the precise link but try either nucleuspowered.org/docs/modules/blacklist.html or nucleuspowered.org/documents/modules/blacklist.html
Pretty sure it’s the first, but may be the second.
Or may be neither.
Link to the webpage is up top - should be easy to navigate from there
Easier than on a phone anyway 
“plugins” folder?
Sponge doesn’t have “plugins” folder. I think. XD
You are mistaken. Sponge Servers can use a /plugins folder. It’s right there in the global.conf file
Being a bit lazy here as have to run, just hoping for a quick answer before I can invest some time in it myself.
On dying, I’m being sent to what I’m assuming is a generic spawn point.
I’ve tried using /setspawn /setworldspawn /spawnpoint NAME but still death results in being dropped in somewhere else.
Anyone have thoughts on this?
Check the config, there’s an option to set it to spawn or home
1 Like
Hi dualspiral,
I’m trying to import an existing world with custom generatorOptions. Unfortunately these are being lost on import and even if I create a new world and adjust those later on in the level.dat, they are not being taken into account.
Is there any way to get this working?
Ah.
I am an idiot u.u
Just checked my /home and yep that’s it.
Must have moved it to the ocean without realising for some reason.
Danke
New question / quandary
Issue having a command based-kit execute its commands.
Kit contents:
give {{player}} minecraft:stone
Command being ran via console:
kit give USERNAME KITNAME
This processes as the client chat has the printout:
The kit KITNAME was added to your inventory.
Yet the give commands do not seem to run as no items are added.