Built into Cipher ClientOn by default

Crash Guard Stop Minecraft crash exploits before they reach your game

Crash Guard inspects what a server sends before your client processes it, and handles anything dangerous quietly instead of letting it freeze or crash Minecraft.

Runs locally 3 profiles Server whitelist
01

How Crash Guard works

Many Minecraft "crash" or "lag machine" exploits work by sending the client more data than it can handle: thousands of particles in one packet, a flood of sounds, hundreds of primed TNT, books and items with huge NBT, or a resource pack that unpacks into gigabytes.

Crash Guard sits between the network and the game. It checks incoming data before Minecraft processes it, clamps or merges what is excessive and skips what is invalid. Everything happens on your own client; nothing is sent anywhere.

An emergency particle safety net stays active even when you switch Crash Guard off, so a single malicious packet cannot lock up your game.

02

What Crash Guard protects against

PARTICLES

Particle floods

Oversized particle packets are clamped and particle work is budgeted per second.

SOUND

Sound floods

Duplicate and excessive sounds are merged instead of played hundreds of times.

TNT

TNT and explosion floods

Only a set number of primed TNT is created on your client and extra explosion effects are skipped. Knockback and block changes stay correct.

FIREWORKS

Firework floods

Firework bursts are budgeted instead of all being rendered at once.

ENTITIES

Equipment floods

Rapid armour and hand swapping of entities is merged.

TEXT

Chat, title, bossbar and scoreboard floods

Message and overlay spam is limited before it overwhelms the client.

DATA

Oversized text, NBT, items and books

Data that would take seconds to process is rejected instead of freezing the game.

NUMBERS

Invalid values

Impossible positions, velocities and explosion values are ignored.

NETWORK

Network abuse

Malformed packets, oversized compressed frames and bundle abuse are stopped.

RESOURCE PACKS

Unsafe resource packs

Bad URLs, private-network addresses, archive bombs and oversized textures are blocked.

03

Profiles and settings

Every Crash Guard setting is adjustable under Settings → Crash Guard. Three presets, Compatibility, Balanced and Strict, set all limits at once; you can fine-tune individual settings afterwards. If a server with heavy but legitimate effects looks wrong, try a less strict profile or whitelist that server.

Trusted servers can be whitelisted, and an optional HUD panel shows live Crash Guard status. The panel is off by default. Crash Guard also has its own chat command, .crashguard.

04

What Crash Guard does not do

Crash Guard protects your client from data it receives. It does not change what the server does, it cannot stop a server from kicking or banning you, and it does not protect other players. No protection can guarantee that every future exploit is caught; Crash Guard is designed to catch the known categories above with as little impact on normal play as possible.

05

Crash Guard FAQ

Is Crash Guard enabled by default?

Yes. Crash Guard runs locally and is on by default. You can adjust it under Settings → Crash Guard.

Does Crash Guard change gameplay?

Crash Guard limits how much dangerous data your client processes. For TNT and explosions, knockback and block changes stay correct; only extra visual effects and duplicate entities are skipped.

Can I trust a server and turn Crash Guard off for it?

Yes. Trusted servers can be whitelisted. An emergency particle safety net stays active even when Crash Guard is off.