- Add dimension support to teleport action
- Fix version ranges
- Add Minecraft 1.21 support
- Migrate gradle to kotlin dsl
- Update stonecutter to 0.4
- Fix excessive memory usage for tracking errored blockstates
- Downgrade records in 1.19.2 and below to allow java 6 gson to serialize them
- Fix missing translation for item stack error id not found
- Fix 1.19.2 on dedicated servers
- Recompile of .7 as published versions had corruption ... I have no idea how
- Add 1.19.1-1.19.2 jar
- Fix 1.19.1/2 compat
- Fix minecraft version deps on published builds
- Migrate to custom_data component for persistence on item stacks
- Add Russion Translations (mpustovoi)
- Actually fix the crash on dedicated servers
- Fix crash on dedicated servers
- Fix Command Permissions
- Added NeoForge support
- New ticking suspension system:
- Entities, block entities, block states and item stacks will no longer be killed or removed but will instead be suspended until an operator takes action.
- This should mitigate the undesired outcome where an important or useful entity is killed.
- Added new actions to the ticking entity broadcast
What Is This?
: Opens the Neruina wiki page on what Neruina is and what it doesCopy Crash
: Copies the cause of the ticking exception to your clipboardTeleport
: Teleports you to the location of the ticking entityTry Resume
: Attempts to resume the ticking of the ticking entityKill
: Immediately kills and removes the ticking entityReport
(1.19+): Opens a new issue on the NeruinaAutoReports GitHub repository and any mods that opt-in to the reporting system
- Persitance:
- Ticking entity tracking will now persist across server restarts
- When the world is first started Neruina will broadcast all tracked ticking entities that need addressing
- Ticking Threshold:
- When a certain number of ticking excpetions occur within a certain time frame, Neruina will deliberately crash in order to prevent the server from becoming unusable.
- A comprehensive report will be generated with every ticking exception that occurred with instructions on what to do next.
- The default threshold is 10 exceptions within 5 minutes, this can be changed in the config.
- Improved performance and memory usage by delegating the ticking state to the ticking entity
- Migrated to Stonecutter to ease multi-loader multi-version development
- Added a new system for mods to opt-in to the auto reporting system
- See the schema here
- These are designed to be used internally by Neruina as it is a server-side mod and allows the client messages to interact with the mod, but they are available to operators as well.
/neruina resume <entity|pos|player>
entity
: Resumes the ticking of the specified entityblock_entity
: Resumes the ticking of the block entity at the specified positionblock_state
: Resumes the ticking of the block state at the specified positionitem_stack
: Resumes the ticking of the held item of the specified player
/neruina kill <entity>
: Immediately kills and removes the specified entity/neruina id <entity|pos>
entity
: Returns the report UUID of the specified entity if it is being trackedpos
: Returns the report UUID of the block entity at the specified position if it is being tracked
/neruina info <uuid>
: Sends the error message of the specified report UUID to the player/neruina clear_tracked
: Clears all tracked ticking entities/neruina show_suspended
: Displays all suspended ticking entities/neruina report <uuid>
(1.19+): Automatically generates a report for the specified ticking entity via it's tracked report UUID/neruina cancel_login
(1.19+): Cancels the current in-progress github authentication process
- New
log_level
option that replacesbroadcast_errors
operators
(default) - Only operators will receive the broadcasteveryone
- Everyone will receive the broadcastdisabled
- No one will receive the broadcast
- New
ticking_exception_threshold
- The number of ticking exceptions that can occur within the specified time frame before Neruina will deliberately crash
- Default is
10
-1
will disable the threshold
- New
auto_kill_ticking_entities
- If true, ticking entities will be immediately killed and removed rather than suspended
- Default is
false
- Fixed a crash with newer versions of Forge
- Fixed a crash with does potato tick 1.18.2