Zexter

Zexter — A Peak Performance Client-Side Optimisation Engine for Minecraft

Mod ID: zexter Author: Zexter · License: MIT Supported versions: Minecraft 1.21 – 1.21.11 and 26.1 – 26.3 (Fabric)

What Is Zexter?

Zexter is an all-in-one, client-side performance engine for Minecraft. It does not add blocks, items, or gameplay — it makes the game itself run smoother by quietly removing work the renderer and the network do for things you can’t see.

Every optimisation is conservative: an object is skipped only when it is provably out of sight or out of range, so you lose frames at worst, never correctness.

What It Does

Auto-Tuned Graphics On first launch, Zexter probes your machine — CPU cores, RAM, GPU name, and max texture size — and derives a performance profile that fits. View distance, simulation distance, entity scaling, frame-rate cap, VSync, mipmaps, graphics quality, particle mode, clouds, entity shadows, and ambient occlusion are all set to values that match your hardware, then applied exactly as if you’d chosen them in the options screen.

Smart Entity Culling Entities outside your render distance and outside your field of view are skipped before they ever reach the GPU. The hook runs before the entity’s render state is built, so a rejected entity costs nothing — not even a draw call.

Block-Entity Culling (Experimental) Tile entities too far to be seen are skipped before their render state is extracted. Enabled only behind an experimental toggle, because it can rarely hide something in edge cases.

Particle Budget Particles are the single most expensive thing a client draws. Zexter caps how many can spawn per tick and scales the budget with your live FPS — when frames dip, spawn rates drop; when they recover, so does the budget. Distant particle packets from the server are dropped on the network thread before they’re ever parsed, which is far cheaper than creating them.

Adaptive Quality A frame-rate monitor drives a smooth adaptive scale in [0, 1]. Below the low-FPS threshold it slides toward a minimum spawn scale; above the high-FPS threshold it climbs back to full. The particle system and render-distance scaling both listen to it.

Lighter Options File Every game-option change is tracked. When nothing you touched has changed, the options file write is skipped entirely — no disk I/O on every tick.

Fail-Safe Everything Every optimisation that touches live game state is wrapped. If anything throws, Zexter falls back to vanilla behaviour and logs a warning. The mod will never crash your game because of its own optimisation code.

Consent First Zexter changes game options, skips work, and drops packets — so it asks before doing any of it. On the title screen, a popup shows what it detected about your machine and what it plans to do. Say “Allow” and it activates; say “Deny” and it stays silent. The answer persists across launches.

Requirements

• Fabric Loader and Fabric API
• Java 21+ (1.21) or Java 25+ (26.x)
• Minecraft 1.21–1.21.11 or 26.1–26.3

Configuration A JSON config file (zexter.json) lets you tune render distances, particle thresholds, worker threads, and toggle experimental features — all without touching code.

Safety Guarantees Consent first — nothing changes until you allow it. Conservative culling — an object is rejected only when provably invisible, with safety margins. Fail-safe wrapping — any exception degrades to vanilla behaviour. Experimental features gated — aggressive culling requires explicit opt-in. Purely client-side — server gameplay is untouched. Zexter is built to run on everything from integrated graphics to high-end GPUs, and to stay out of your way when you’d rather have vanilla.