Nitwit Stability First 1.2.6 — Stability Regression Guardrails

Compatibility metadata: Minecraft 26.0–26.3, Fabric Loader >= 0.18.4, Java >= 25, Fabric API required.

Changes
- Corrected the mod icon asset: assets/nitwit/icon.png is now an actual PNG image, not JPEG bytes with a .png filename.
- Disabled automatic render-distance changes. Changing render distance during a severe slowdown can trigger extra chunk loading, mesh rebuilding, and network chunk traffic.
- Disabled automatic simulation-distance changes. This avoids Nitwit changing local simulation work while the game is already overloaded; the client cannot change a remote server's simulation distance or TPS.
- Retained adaptive entity-distance and particle reductions.
- Slowed the adaptive settings cycle from every 5 client ticks to every 20 client ticks, reducing how often the controller re-reads and applies options.
- Added stability guardrails: overload response requires at least 90 frames, recovery uses at least 900 frames, and the rapid-spike escalation now needs a higher score and longer cooldown.
- Migrates the configuration to schema 6. Other unrelated config entries are preserved, while the four stability-related settings above are normalized.
- Keeps the existing Fabric callbacks and does not replace Minecraft's renderer or install invasive rendering mixins.

Important limitations
- This is a stability-first adaptive options controller, not a Sodium-style renderer replacement. It cannot guarantee a fixed FPS, eliminate all stutter, control GPU driver scheduling, force other mods to use fewer threads, lower network ping, prevent input latency under every workload, or force a remote server to maintain 20 TPS.
- Real-world improvement depends on the client hardware, renderer, other installed mods, world, and server. The build must still be tested in-game on the user's exact Minecraft/Fabric setup; this environment cannot run a live Minecraft server/client test.

Installation
1. Close Minecraft.
2. Back up and remove the previous Nitwit 1.2.5 JAR from the mods folder.
3. Install Nitwit-1.2.6-Stability-First-26.0-to-26.3.jar.
4. Back up config/nitwit.properties before launch. On first launch, Nitwit normalizes adaptive_render_distance=false, adaptive_simulation_distance=false, overload_frames=90, recovery_frames=900, and sets config_schema=6. Other unrelated settings are preserved.
5. Test in the same world and compare the F3+2 frame-time chart and integrated/server tick times.
