This is it! After the first commit on 12th January 2016, with the mission to provide Sponge with the Essentials like plugin it deserves, we’re here. 1.0! The first truly stable build for the Sponge API.
You might be thinking “but, Nucleus has been stable for a long time!” Yes, but the plugin has been growing and with it, its fair share of bugs have appeared, and it’s always felt a little rough. Not so much any more, it’s finally time to shed the 0.x numbering system and present a shiny 1.0! For those of you who have used Nucleus over the past 17 months or so, thank you for making it what it is. For those of you who have contributed, be it code, support, bug reports, or just the odd conversation in Discord, you all made this happen.
It is intended that now, the release schedule will change, and owners will have two options, standard and LTS (longer term support) versions.
- Standard versions: Work will continue on providing features like normal, the next feature build after 1.0 will be 1.1. These will be released semi-often with new features, but will not necessarily see bug fix point releases, except in the case of critcal bugs. There may be more daring changes on this branch now, as we will have an LTS branch with those who don’t need to take the risk.
- LTS versions: The 1.0.x builds are designated LTS. Not all feature builds will become LTS builds, one will be designated every two months or so (most likely). The plan is that LTS builds will receive greater testing, and will be supported in a bug fix mode for longer, parallel to standard versions. The hope is that server owners that don’t like to update for fear of breakages will use LTS versions and be supported with a bug fix, low risk development train.
Only one LTS release branch will be supported at a time, support for a previous LTS branch will end when a new LTS feature build is pushed.
Why am I doing this? I noticed that a lot of more established networks and servers tend to stick with older versions of Nucleus for a while, and because they don’t update, they don’t get the bug fixes. So, I wanted to be able to support the larger networks with LTS versions that allowed them to stick with these older versions, but get support. I do not anticipate that the LTS versions will take a lot of my time! I hope…
Important Note about Nucleus Mixins: Nucleus Mixins is a mod not a plugin, that can be used on SpongeForge and SpongeVanilla servers. It MUST be in your MODS directory, NOT any other plugin directory.
If you’re having trouble, visit our Discord channel: https://discord.gg/MC2mAuS
main.conf will go through a bit of a transformation when you start up 1.0. The modules section will be renamed to
-modules to put it at the top of your config file, and fancy headers will appear. This makes this version incompatible with all
0.x series builds, so once you use this, unless you want to make manual changes to revert them, you’re not going back.
So please, for the love of everything that is right with the world. Backup your Nucleus configs.
This was a notice for 0.29.x where the Blacklist module was deprecated. It’s now removed, the migration commands remain.
The blacklist module is a module that was broken as it was and just not essential. It came from EssCmds, and it was largely ignored. While we recognise that it’s not a popular decision with some people, it was conflicting with some mods and potentially breaking GP functions, and possibly other plugins because of how overzealous it was.
You can now migrate to ProtectionPerms and GriefPrevention
/gm, gamemode specific permissions now default to
true and will be hidden from future releases.
This does not affect existing installations, but new installations have the config option
admin.separate-gamemode-permissions set to
true - and it is hidden.
The blacklist module has been removed. An attempt at a ProtectionPerms and GriefPrevention migrator has been made. An API is also available to get the blacklist restrictions.
This command teleports a player one block away from where they are if the location they are standing in is deemed to be “unsafe”, and there is a safe location to stand next to them.
This command sets whether the attributes of the item currently in your hand when it is hovered over are shown or hidden.
Now, you can control who can modify an ender chest inventory.
nucleus.enderchest.modify(allows player to modify)
nucleus.enderchest.exempt.modify(prevents player from having chest modified)
Note that if you get a read-only view, it will not refresh if the target player updates their enderchest. You will need to re-open the chest using
This allows users who want to create a world using
/world create) to see what generators (for
-g), modifiers (for
-m) and presets (
Turning on debug mode and forgetting to turn it off is a thing of the past!
/nucleus debug setsession [true|false] allows you to turn debug mode for the server session only - it will turn off automatically on the next restart if you don’t remember to turn it off yourself.
Repository: ‘http://repo.drnaylor.co.uk/artifactory/list/minecraft’. Dependency (1.10.2): ‘io.github.nucleuspowered:nucleus-api:1.0.0-S5.1’ Dependency (1.11.2): ‘io.github.nucleuspowered:nucleus-api:1.0.0-S6.0’
Deprecated methods have now been removed.
This allows plugins that want to prevent players from going AFK, but aren’t necessarily going to move, to send a “keep alive” signal, resetting the AFK timer.
- Updated the configuration file to make it easier to find some modules
- Updated DocGen to generate Ore markdown files
- Updated DocGen to print the default config
- Updated QSML to 0.8.1
- Reoragnised some of the command behaviour
- Updated Neutrino to 1.0
- Removed the collision listener
/backfor forcing a teleport, even if unsafe
- Fixed ArmorStands being prevented from being placed when vanilla mobs are blocked from spawning
- Set first spawn force logic to run 3 ticks after the player joins, rather than one.
- Cleaned up some logic
- Improve AFK logic
- Fix some mutes accidentally being permanent
- Fix NPE in server list code
- Sometimes, an incorrect custom prefix might be selected. Nucleus uses whatever the permission plugin hands back, check your inheritance with the permissions plugin.
- The use of Boop causes issues with staff chat formatting.