Neruina Mod FAQ

Neruina works silently in the background, so you usually only notice it when a crash would have happened but didn't. When it suspends a mob, block, or item, it logs the event and gives you in-game actions to inspect or resolve the problem.

A suspended mob is one that was causing a ticking crash, so Neruina froze its ticking to keep the game running. You can still walk up to it and interact with it, but you can't attack or kill it normally until the issue is resolved.

Use the Neruina actions on the suspended mob to teleport to its location, view the crash info, or kill it outright. Killing it through Neruina's action menu is the clean way to remove it without triggering the crash again.

Neruina disables attacking on suspended mobs on purpose, because hitting them can re-trigger the ticking error and crash your world. Use the mod's kill action instead of normal combat.

No, Neruina stopped that block or block entity from ticking because it was throwing errors. You can still open it and access its inventory, so your items aren't lost — you just need to resolve the underlying issue or remove the block.

Yes, items that would crash the game while sitting in an inventory are still usable in crafting recipes. Neruina only prevents them from causing a ticking crash in storage, not from being used normally.

You were kicked because one of your actions was causing a ticking crash that would have taken down the server for everyone. Rejoin and check the crash info Neruina logged so you can avoid repeating whatever triggered it.

Neruina remembers every ticking issue it has handled and exposes the crash details through its in-game actions. You can copy that crash information to your clipboard directly from there to share with server staff or a mod developer.

It doesn't fix the root cause — it contains the symptom so your world keeps running. The crash info it saves is what you use to actually track down and fix the broken mod, block, or entity.

Neruina targets ticking crashes specifically, so it generally coexists with other performance mods. If you run multiple crash-handling mods, test them together and check logs, since overlapping crash interception can produce confusing results.

Neruina adds a keybind you can check in your controls menu, usually unbound by default. Once bound, pressing it opens the list of every ticking issue it has recorded.

You don't need to configure anything for it to work — just install it and it silently suspends anything causing a ticking crash. When something does get suspended, open the issue list to teleport to it, kill it, or copy the crash info.

That mob is suspended by Neruina because it was causing a ticking crash. You can still interact with it, but attacking is disabled to keep it from triggering the crash again — use the kill action from the issue list instead.

Open the Neruina issue list, find the entry for that mob, and use the kill action. This removes it cleanly without re-triggering the crash.

Neruina only catches ticking crashes, not crashes from world generation, rendering, or other mods loading. Check your crash log — if the stack trace isn't from a tick event, Neruina won't intercept it.

Open the issue list and select the teleport action for the entry you want. It moves you to the location of the suspended block, mob, or item so you can deal with it directly.

Yes. Neruina stops the block entity from ticking but leaves its inventory accessible, so you can open it and take your items out normally.

Your actions caused a ticking crash, so Neruina kicked you to keep the server running for everyone else. Rejoin and avoid repeating whatever you did — check the issue list or server logs to see what triggered it.

Yes, and it's most useful there. It needs to be installed on the server side; clients don't strictly need it, though having it on both sides gives you the issue list UI in-game.

It has minimal overhead because it only activates when a ticking error occurs. It doesn't scan or modify normal ticks, so you shouldn't notice any impact during regular play.