Plugin Configs Vulcan + Grim Anticheat Premium Config v3.1

Confused With What to set in Config.yml ? Dont worry we got you covered | Updated 2026

WHY THIS CONFIG IS DIFFERENT

Most configs floating around BuiltByBit are barely-edited defaults — or blindly copy-pasted settings that false-ban legitimate players while letting actual cheaters slide. This pack fixes every critical mistake:

• 201+ individual checks tuned across Combat, Movement, and Player categories
• Critical default bugs fixed — settings that shipped broken and nobody told you
• Tighter thresholds that match the real-world performance specs each plugin was designed for
• Smarter punishments — Grim's original punishments.yml had NO autoban for flight, speed, or timer cheats
• Zero console spam, zero staff chat flooding, zero lag-spike false bans

VULCAN — CRITICAL FIXES

These were broken in every default Vulcan config. Most servers are running these mistakes right now:

• debug: false — Default shipped as true. Was flooding your console with [Vulcan Debug] spam every single second. The config's own comment tells you to disable it.
• maximum-ping: 1000ms — Default was 5000ms. At 5 seconds of ping, any player can bypass every detection by intentionally lagging. 1000ms is the sane ceiling.
• Reach threshold: 3.03 — Default 3.02 false-flags on 1.9+ due to attack-cooldown hitbox expansion. 3.03 still catches every blatant reach module.
• Velocity A/B/C — all punishable — Velocity is the single most reliable cheat signal in the entire plugin. The original config left it mostly silent.
• punishment-delay: 5000ms — Reduced from 10 seconds. Blatant cheaters get banned in 5s, not 10s.
• ignore-alerts-over-max-violations: true — Prevents staff chat from being spammed after a player has already flagged 50+ times waiting on a ban.
• Ban duration: 30 days — Strong deterrence for repeat cheaters (easily changed back to 5d if preferred).

VULCAN — DETECTION IMPROVEMENTS

• KillAura B/C: max-vl raised 3→4 and 2→3 — fewer rage-PvP false bans but instant-killaura still gets caught immediately
• Flight A/B/C: Buffers tightened (max 4–5, multiple 0.65–0.75) for faster setbacks on fly modules
• Speed B: Now punishable — was the only reliable speed check left completely silent
• Scaffold A: max-vl raised 3→4 to avoid false-bans on legit Bedwars bridging
• Timer A: minimum-tps raised to 19.5 — timer detection requires near-perfect TPS, otherwise lag = false bans
• Autoclicker A: max-cps tuned 22→20, max-vl bumped to 8 — more accurate, less false-flag-prone
• Aim checks: Buffers widened slightly so legit aim recovers faster, blatant aim still triggers in 4–6 violations
• Ghost-blocks fix: Ticks tuned 3→4 for better recovery on lag spikes

GRIM — PRECISION TUNING

Grim is prediction/simulation-based — not violation buffers like Vulcan. Tuning means hitting the actual performance specs the plugin was designed for. Your default config was missing those by a massive margin:

• Reach threshold: 0.0005 — Default was 0.05, missing the entire 3.01–3.04 range where most reach modules sit. With 0.0005, you catch reach hacks that other anti-cheats literally cannot see.
• Simulation threshold: 0.0001 — Grim's famous spec is "0.01% speed detection." Default value of 0.035 was 35× too lenient, allowing 3.5cm/tick offset. Fixed.
• Knockback threshold: 0.001 — Catches sub-millimeter velocity tampering. Grim is rated 99.99% anti-KB — but only when this is set correctly.
• TimerA setbackvl: 15 — Faster setback on timer abuse before it can be exploited for fast-bow or fast-heal
• Scaffold/Tower: cancelvl 1 — FabricatedPlace, FarPlace, PositionPlace, RotationPlace all cancel on the first violation instead of letting one slip through
• AirLiquidPlace enabled — Was disabled (cancelvl: 0) by default. Now cancels air/liquid placement hacks on first flag.

GRIM — PUNISHMENTS.YML REBUILT

This is the most impactful change. The original file had no autoban for entire categories of cheats:

• Simulation: Now bans at 200 violations — covers flight, speed, motion, timer, nofall, groundspoof. Was completely missing.
• Knockback: Now bans at 30 violations — covers anti-KB. Was completely missing.
• BadPackets: Now bans at 80 violations — covers crash exploits and chat exploits. Was completely missing.
• Post: Now bans at 60 violations — post-attack cheats that other anti-cheats miss entirely. Was missing.
• Phase: New category added — bans at 15 for noclip/phase cheats. Was never configured.
• Reach: Ban threshold lowered 10→8 — reach is Grim's most reliable check, no reason to wait longer
• Hitboxes: Ban threshold lowered 20→15
• MiscTwo: Now bans at 40 violations — previously alert-only despite catching NoSlow/Sprint/Vehicle cheats
• Baritone: Ban threshold lowered 30→20 — no legitimate player ever triggers this (bot-pathing detection)
• Combat: Ban threshold lowered 50→30

WHAT'S INCLUDED




🛡 DETECTION COVERAGE

Combat

• KillAura (A, B, C variants)
• Reach — 3.0005 precision threshold
• AimAssist
• Autoclicker
• Hitbox manipulation
• Velocity / Anti-Knockback

Movement

• Flight (A, B, C variants)
• Speed
• Timer abuse
• Scaffold / Tower hacks
• NoFall
• Phase / NoClip
• Elytra exploits
• Ghost-block bypass

Misc

• BadPackets / Crash exploits
• Baritone bot-pathing
• FastBreak
• NoSlow / Sprint exploits
• Vehicle cheats

SETUP — 60 SECONDS

1. Download and extract the ZIP
2. Drop Vulcan's config.yml into plugins/Vulcan/
3. Drop all 4 Grim files into plugins/Grim/
4. Run /vulcan reload and /grim reload
5. Done. Both plugins are live.

You can run Vulcan and Grim simultaneously — they complement each other. Grim excels at movement, simulation, and knockback. Vulcan is stronger on KillAura, aim, and scaffold. Together they cover almost every cheat module.

COMPATIBILITY

• Minecraft versions: 1.8 – 1.21.x
• Server software: Spigot, Paper, Purpur, Pufferfish, Folia (Grim)
• Geyser/Bedrock: Grim auto-exempts Bedrock players if Floodgate is installed
• Java: Java 17+ required for latest Grim builds
• Dependencies: Vulcan requires PacketEvents · Grim includes PacketEvents bundled