A new version has been released for Nucleus, it is available for download here.
This is a major release for Nucleus for Sponge API version 7.1
This was built from Nucleus commit: d294457d
If you’re having trouble, visit our Discord channel: https://discord.gg/A9QHG5H
Updated version checking
A lot of issues have come up recently due to people updating Nucleus but not their Sponge servers. I’ve updated
the version check to gracefully fail if Sponge API 7.1 is not found.
This will also fail with bleeding Sponge builds - but Nucleus doesn’t work with them anyway.
You can disable this check by setting the
nucleusnocheck property (
/unsign) for making written books writable
Note that this feature requires SF/SV 7.1.3 or above, or the equivalent implementation
This command requires that you hold the book in your (or the target’s) hand.
This event is fired when a
NucleusTextTemplate is sent to command sources. If the originator is the
broadcast or plain broadcast commands, this event will be
[API] Relaxed requirements for the cause for the Home events
They used to require the
PluginContainer at the root, now they don’t.
Under the Hood Changes
These are changes that should not affect players, but are here for informational purposes,
and may be of interest to developers working on the Sponge platform seeking greater understanding
The way the chat messages are handled by Nucleus has been changed slightly. This is due to research
after an issue opened by XadepSDK concerning compatibility with Nanochat. Nucleus now uses the
Sponge modular chat system and does less to break compatibility with other plugins that might want
to add tokens to chat.
If you wish for maximum compatibility with Nucleus, please either:
- Use the Nucleus Message Tokens system
SimpleTextTemplateAppliers to the event formatter, rather than unilaterally changing the body/header/footer.
-b flag for
/tp, it didn’t do anything anyway. Use
- Fix class cast exception when using some chat plugins in combination with Nucleus
- Fix cooldowns on
/tpa being created regardless of success (now it’ll only start when a teleport has occurred).
- Sometimes, an incorrect custom prefix might be selected. Nucleus uses whatever the permission plugin hands back, check your inheritance with the permissions plugin.