Invasive Optimizations

Invasive Optimizations

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

von
2.4K Downloads
neoforgeoptimization
Server mit dieser Mod mieten

Über diese 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.
  5. Patch is experimental or of dubious usefulness (these are disabled by default)

Current optimizations:

  • Accessories
    • accessories.roundabout_collection (1): Avoid iterating Map entrySet by directly accessing underlying keySet. (PR)
  • Applied Energistics 2
    • ae2.cache_fuzzy_search_max_value (4): Cache AEItemKey::fuzzySearchMaxValue during init. (PR)
  • Botany Pots
    • botanypots.hopper_insertions (1): Hopper Botany Pot exponential insertion backoff and emptiness tracking (PR)
  • Create
    • create.fail_fast_clipboard_migration (4): 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.filter_caching (2): Caches tag filters using BitSets, integer arrays, or single integers. Uses more memory and causes loading pipes to take marginally longer.
    • 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)
  • Placebo
    • placebo.lazy_string_concatenation (1): Pass a Supplier to Object#requireNonNull in DynamicHolder#get as it is a cold path in hot code. (PR)
    • placebo.streamless_hashing (1): Replaces CachedObject#hashComponents with equivalent code that does not use the Stream API. (PR)
  • SFM
    • sfm.filter_caching (5): Caches item and fluid filters (regular/regex and tag filters for now) using BitSets, integer arrays, or single integers. Uses more memory and causes first compiles to take longer.
  • Xycraft Machines
    • xycraft_machines.redstone_checks (3): Extractors check for redstone signals every tick rather than only when their neighbours update
    • xycraft_machines.unnecessary_resorting (3): Extractors resort their recipes every so often but is usually not necessary

Verfügbare Versionen

Invasive Optimizations 1.0.23 for 1.21.1release
MC 1.21, 1.21.1neoforge
2. August 2026
Invasive Optimizations 1.0.22 for 1.21.1release
MC 1.21, 1.21.1neoforge
25. Juli 2026
Invasive Optimizations 1.0.21 for 1.21.1release
MC 1.21, 1.21.1neoforge
22. Juli 2026
Invasive Optimizations 1.0.20 for 1.21.1release
MC 1.21, 1.21.1neoforge
22. Juli 2026
Invasive Optimizations 1.0.19 for 1.21.1release
MC 1.21, 1.21.1neoforge
19. Juli 2026

Invasive Optimizations auf dem Server installieren

1

Server bestellen

Bestelle einen Minecraft Java Server mit mindestens 3 GB RAM (4 GB empfohlen).

2

neoforge Loader setzen

Wähle im Panel unter "Egg" den neoforge-Loader und die passende Minecraft-Version (1.21.1).

3

Mod installieren

Öffne den Mod-Browser im Dashboard und suche nach "Invasive Optimizations". Klicke "Installieren" – fertig! Alternativ: Lade die .jar via SFTP in den /mods Ordner.

Kompatibilität

Mod-Loader

neoforge

Minecraft-Versionen

1.21.1, 1.21

Server-seitig

Erforderlich

Empfohlener RAM

4 GB(min. 3 GB)

Häufige Fragen

Invasive Optimizations Server crasht beim Start – was tun?

Häufigste Ursache: falsche neoforge-Version oder zu wenig RAM. Prüfe im Server-Log (latest.log), ob ein "OutOfMemoryError" oder "Mixin"-Fehler auftritt. Bei Mado Hosting: Stelle sicher, dass mindestens 3 GB RAM zugewiesen sind und der Loader zur Mod-Version passt (1.21.1). Über das Panel kannst du den Loader mit einem Klick wechseln.

Ist Invasive Optimizations mit neoforge kompatibel?

Invasive Optimizations unterstützt offiziell neoforge für Minecraft 1.21.1, 1.21. Im Mado Dashboard werden inkompatible Loader-Kombinationen automatisch erkannt.

Server laggt mit Invasive Optimizations – wie optimiere ich die Performance?

Empfohlener RAM: 4 GB (+1 GB pro 8 Spieler). Prüfe mit /spark profiler, ob Invasive Optimizations den meisten Tick-Time verbraucht. Häufige Fixes: Server-View-Distance auf 8-10 reduzieren, bei Forge "performant" oder "starlight" als Zusatz-Mod installieren. Bei Mado Hosting läuft dein Server auf NVMe-SSDs mit dedizierten CPU-Kernen für minimale Latenz.

Modded Server mieten

Installiere Invasive Optimizations mit nur einem Klick auf deinem Server.

Empfohlener RAM
4 GBab €5.2/Monat
Min. 3 GB | +1 GB pro 8 Spieler
Jetzt Server erstellen
1-Klick Mod Installation
NVMe SSD Speicher
DDoS-Schutz inklusive

Details

Lizenz
MIT License
Server-seitig
Erforderlich

Unterstützte Versionen

1.21.11.21