Invasive Optimizations

Invasive Optimizations

Invasive optimizations for other mods. If you experience any issues, disable this mod first!

by
248 Downloads
neoforgeoptimization
Rent Server with this Mod

About this Mod

Invasive Optimizations

Logo

Invasive optimizations for other mods, aiming to reduce server-side (tick) lag.
The invasive nature of these changes makes them more likely to crash or otherwise break.
Please report such issues to the issue tracker and I will try to respond to them in a timely manner.
Each change can also be individually toggled through the config and should solve any issues temporarily while you wait for a fix.

Optimizations included in this mod fall under one of the following categories:

  1. Patch has been sent but has not reviewed for a long time or expected to be useful in the time before the next release.
  2. Patch denied due to reasons unrelated to quality, such as non-maintenance, in which case future optimizations will also not be sent to that mod.
  3. Patch has no avenue of contribution (e.g. closed source mods)
  4. Patch already applied but not available in released versions.

Current optimizations:

  • Botany Pots
    • botanypots.hopper_insertions (1): Hopper Botany Pot exponential insertion backoff and emptiness tracking (PR)
  • Create
    • create.fail_fast_clipboard_migration (1): Fails fast when attempting clipboard migration in ItemStack.<init>, reducing impact to this extremely common operation. (PR)
  • Pastel
    • pastel.nuke_item_predicate_mixin (4): Nukes Pastel's ItemPredicateMixin as it is unnecessary and expensive
  • Pipez (Also see Pipez Lag Fix by AlmanaX21 for exponential backoff)
    • pipez.constant_fullness_checks (2): Turns connection/inventory fullness into O(1) operations
    • pipez.early_exits (2): Reduces unnecessary work done by exiting targeted functions early if the right conditions are met
    • pipez.extract_looped_work (2): Move some work out of loops to avoid duplicated work
    • pipez.nbt_comparisons (2): Drastically improves performance of NBT comparisons by minimizing serialization/deserialization operations
    • pipez.stream_abuse (2): Reduces abuse of Streams in hot paths to reduce allocation rate (PR)
  • Xycraft Machines
    • xycraft_machines.unnecessary_resorting (3): Extractors resort their recipes every so often but is usually not necessary
    • xycraft_machines.redstone_checks (3): Extractors check for redstone signals every tick rather than only when their neighbours update

Available Versions

Invasive Optimizations 1.0.14 for 1.21.1release
MC 1.21, 1.21.1neoforge
May 21, 2026
Invasive Optimizations 1.0.13 for 1.21.1release
MC 1.21, 1.21.1neoforge
May 19, 2026
Invasive Optimizations 1.0.12 for 1.21.1release
MC 1.21, 1.21.1neoforge
May 19, 2026
Invasive Optimizations 1.0.11 for 1.21.1release
MC 1.21, 1.21.1neoforge
May 18, 2026
Invasive Optimizations 1.0.10 for 1.21.1release
MC 1.21, 1.21.1neoforge
May 7, 2026

How to Install Invasive Optimizations on Your Server

1

Order Server

Order a Minecraft Java server with at least 3 GB RAM (4 GB recommended).

2

Set neoforge Loader

In the panel under "Egg", select the neoforge loader and matching Minecraft version (1.21.1).

3

Install Mod

Open the mod browser in the dashboard and search for "Invasive Optimizations". Click "Install" – done! Alternatively, upload the .jar via SFTP to the /mods folder.

Compatibility

Mod Loaders

neoforge

Minecraft Versions

1.21.1, 1.21

Server-side

Required

Recommended RAM

4 GB(min. 3 GB)

Frequently Asked Questions

Invasive Optimizations server crashes on startup – what to do?

Most common cause: wrong neoforge version or insufficient RAM. Check the server log (latest.log) for "OutOfMemoryError" or "Mixin" errors. With Mado Hosting: ensure at least 3 GB RAM is allocated and the loader matches the mod version (1.21.1). You can switch loaders with one click in the panel.

Is Invasive Optimizations compatible with neoforge?

Invasive Optimizations officially supports neoforge for Minecraft 1.21.1, 1.21. The Mado dashboard automatically detects incompatible loader combinations.

Server lagging with Invasive Optimizations – how to optimize performance?

Recommended RAM: 4 GB (per 8 players). Use /spark profiler to check if Invasive Optimizations consumes the most tick time. Common fixes: reduce server view-distance to 8-10, install "performant" or "starlight" as supplementary mods on Forge. With Mado Hosting, your server runs on NVMe SSDs with dedicated CPU cores for minimal latency.

Rent Modded Server

Install Invasive Optimizations with just one click on your server.

Recommended RAM
4 GBab €8/mo
Min. 3 GB | +1 GB pro 8 Spieler
Create Server Now
1-Click Mod Install
NVMe SSD Storage
DDoS Protection included

Details

License
MIT License
Server-side
Required

Supported Versions

1.21.11.21