Neruina is a utility mod that prevents ticking-related crashes from bricking worlds for Minecraft on Fabric, Forge, and NeoForge. Instead of letting one bad ticking entity, block entity, block state, item, or player tick bring everything down, it isolates the problem so your world can keep running.
The core problem this mod solves is brutal: one ticking error can lock you out of a world or keep a server in a crash loop. Neruina steps in at that exact failure point, suspends the source of the issue, and gives you clear actions to investigate and recover without immediate world loss. With nearly 5 million downloads on Modrinth (4,825,134 listed), it has strong social proof among players who want stability in real modpacks, not just clean test environments.
Key Features of Neruina
- Crash containment for entities, blocks, and items — When a ticking entity crashes, Neruina suspends its ticking instead of letting the world fall over, and you can still interact with it (though you cannot attack it). The same idea applies to block entities, tile entities, and random-tick block states: ticking is stopped while access remains available where relevant, such as inventories. For ticking items, the item stops ticking in inventory but still persists and generally remains usable in recipes and normal use cases, which helps prevent loss scenarios.
- Player tick crash handling — If another mod causes a player-related tick crash, Neruina can kick the player rather than allowing the whole process to keep crashing on that tick. This matters on servers where one broken player state can affect everyone online. Recent updates also add a config option to kill players instead of kicking them, giving admins stricter control when needed.
- Action tools for fast triage — Built-in actions like "What Is This?", "Copy Crash," "Teleport," "Try Resume," and "Kill" make troubleshooting practical during live gameplay. You can jump directly to the problem location, copy the exception cause, test recovery, or remove the source immediately. That workflow reduces guesswork and saves time when uptime matters.
- Integrated reporting workflow — The "Report" action (1.19+) opens a new issue flow on NeruinaAutoReports and supports mods that opt into the reporting system. This helps move from "server is broken" to a reproducible bug report with less friction. For pack maintainers, that can shorten the path from incident to fix.
- Persistence across restarts — Neruina keeps tracking ticking problem entities even after a server restart, so unresolved issues are not silently forgotten. On world start, it broadcasts tracked ticking entities that still need attention. This is useful for teams because cleanup tasks stay visible instead of being buried in old logs.
- Threshold-based fail-safe with detailed reporting — If too many ticking exceptions happen in a short window, Neruina can deliberately crash to prevent a server from becoming unusable in a degraded loop. The default threshold is 10 exceptions within 5 minutes, and it is configurable (or can be disabled with -1). Each exception contributes to a comprehensive report with guidance on what to do next, so even deliberate shutdowns produce actionable diagnostics.
Screenshots
How to Install Neruina
- Pick your mod loader first: Fabric Mod Loader, Minecraft Forge, or NeoForge, and make sure it matches your Minecraft version.
- Download the Neruina build that matches your exact game version (for example 1.21.11, 1.21.10, or 1.20.1) and loader variant listed for that file.
- Place the mod jar into your game or server
modsfolder, then launch once so config files are created. - Open the config and review key settings such as
log_level,ticking_exception_threshold, andauto_kill_ticking_entitiesfor your environment. - Restart and verify startup logs, then address any tracked ticking entities Neruina announces when the world loads.
Requirements & Compatibility
| Category | Details |
|---|---|
| Mod Type | Utility |
| Author | Bawnorton |
| Supported Loaders | Fabric, Forge, NeoForge |
| Minecraft Versions | 1.21.11, 1.21.10, 1.21.9, 1.21.8, 1.21.7, 1.21.6, 1.21.5, 1.21.4, 1.21.3, 1.21.2, 1.21.1, 1.20.1, 1.20 |
| Recent Download Entries | 1.21.4 through 1.21.11 builds listed for Fabric and NeoForge |
| License | MIT |
What's New
- Updated to Minecraft 1.21.11 in version 3.1.5.
- Version 3.2.0 backported support to 1.20.1 and re-introduced Forge support.
- Recent fixes include preventing crashes from invalid UUID handling and using a lenient UUID codec for occasional crash cases.
- A new config option was added to kill players instead of kicking them (disabled by default).
- Several compatibility and dependency fixes were shipped across 3.1.x and 3.2.x, including a 1.21.10 injection failure fix and dependency updates.
Pros and Cons
Pros
- Directly targets ticking crashes that can otherwise brick worlds or trap servers in restart loops.
- Gives practical in-game/admin actions for investigation and recovery instead of only writing logs.
- Persists tracked issues across restarts and surfaces them again on world start.
- Configurable threshold and behavior options let you tune risk tolerance for single-player or server use.
- Available across major loader ecosystems, including Fabric, Forge, and NeoForge.
Cons
- It mitigates ticking failures but does not replace finding and fixing the root mod conflict.
- Some suspended entities or forcibly removed problem sources may still require manual cleanup decisions.
- Deliberate crash threshold behavior can be disruptive if configured too aggressively for your server style.
- You still need version-accurate jar selection per loader and Minecraft version to avoid startup issues.
Alternatives to Neruina
- Spark — A complementary diagnostics mod you can use to profile server behavior when you are tracking down the deeper source of recurring exceptions.
- Debugify — A complementary bug-fix focused option that pairs well with stability-first setups where you want fewer edge-case failures overall.
- FerriteCore — A complementary optimization choice often added in practical modpacks to improve general runtime stability posture alongside crash-containment tools.
Download Neruina
| Minecraft Version | Fabric | Forge | NeoForge |
|---|---|---|---|
| For Minecraft 1.21.11 | Download | — | Download |
| For Minecraft 1.21.10 | Download | — | Download |
| For Minecraft 1.21.9 | Download | — | Download |
| For Minecraft 1.21.8 | Download | — | Download |
| For Minecraft 1.21.7 | Download | — | Download |
| For Minecraft 1.21.6 | Download | — | Download |
| For Minecraft 1.21.5 | Download | — | Download |
| For Minecraft 1.21.4 | Download | — | Download |
| For Minecraft 1.21.3 | Download | — | Download |
| For Minecraft 1.21.2 | Download | — | Download |
| For Minecraft 1.21.1 | Download | — | Download |
| For Minecraft 1.20.1 | Download | Download | — |
Always download mods from official sources to stay safe.
Frequently Asked Questions
Does Neruina delete my bugged entities or items automatically?
No — not by default. The default behavior is to suspend ticking so the world can continue, and you can decide whether to resume, remove, or report the issue; automatic kill behavior is configurable.
Can I still interact with something that was suspended for ticking crashes?
Yes — with limits. Suspended entities remain interactable but cannot be attacked, and affected block inventories can still be accessed when present.
Will Neruina work on both client setups and servers?
Yes — it is used in both contexts depending on your loader and version setup. Its persistence, broadcast behavior, and threshold controls are especially useful for server administration workflows.
Does it support Forge right now?
Yes — Forge support is listed and was re-introduced in the 3.2.0 changelog note alongside a 1.20.1 backport. The project also supports Fabric and NeoForge, so choose the jar matching your platform.
Can I control who sees ticking-exception broadcasts?
Yes — through configuration. The log_level setting supports operators (default), everyone, or disabled based on how visible you want alerts to be.
Does Neruina intentionally crash the server in some cases?
Yes — when the configured ticking exception threshold is exceeded. The default is 10 exceptions in 5 minutes, and this behavior exists to prevent the server from degrading into an unusable state while still generating a detailed report.
![[Let's Do] NetherVinery Mod (1.20.1) - thumbnail](http://mcinside.com/wp-content/uploads/2026/04/thumbnail-83-52x52.webp)
