
Rubble Trouble
A small mod to add visible rubble that can not be broken until a command is run.
Screenshots




About this Mod
Rubble Trouble (Forge 1.20.1)
Turn mines into actual worksites. RubbleTrouble adds break-resistant rubble that reforms inside protected zones, plus tools that speed clean-up without letting automation grief your base.
🪨 What it does
Rubble blocks that can reform in locked zones (claims/regions) when broken, slowing trespassers and griefers.
Loose Rubble (decorative drop) for building debris piles, paths, or set dressing.
Vibration Motor: place near rubble to “shake” it loose and speed up manual clearing.
Create compatibility (optional): motors on contraptions can affect nearby rubble without allowing drills to mine inside locked zones.
Creative bypass: real creative players can manage rubble in protected areas; automation and fake players can’t.
Configurable behavior so servers can tune strictness and performance.
✨ Highlights
Spoiler
Anti-grief friendly: inside locked zones, normal breaking pops rubble back in—optionally progressing through visual stages before finally clearing.
Performance conscious: chunk-safe motor scanning, lightweight events, and no forced chunk loads.
Plug-and-play: works on dedicated servers and singleplayer. Clients don’t need the mod for basic protection effects if the server enforces them (but textures/visuals require the client).
🔧 Configuration
Spoiler
A server config is generated on first run:
config/rubbletrouble-server.toml
You can tune (names may vary slightly by release):
lockedZone.enabled – enable/disable protected behavior
lockedZone.creativeBypass – allow true creative players to break
rubble.stageCount & visuals – number of visual stages (if enabled)
motor.radius, motor.pokesPerTick – effect range & strength
compat.create.enableContraptionSupport – toggle Create hooks
debug.logging – quiet or verbose
🤝 Compatibility
Spoiler
Forge: 1.20.1 (47.x)
Create: optional; detected at runtime (no hard dep)
Works alongside most claim/protection mods; point your “locked zone” hook at their region checks.
Designed to ignore fake players unless explicitly allowed in config.
📦 Blocks & Items
Spoiler
Rubble — the sturdy, re-forming block (with optional stage visuals).
Loose Rubble — decorative block; servers can allow it to always drop itself.
Vibration Motor — boosts nearby rubble breaking speed; chunk-reload safe.
🧭 Intended gameplay
Builders/admins: keep spawn, museums, and vaults tidy without turning off fun entirely.
Adventure servers: gates, ruins, and dungeons that feel “lived in” and recover after raids.
Create enjoyers: bring a motor along to chew through debris—without drilling through claims.
⌨️ Commands
Spoiler
Scope & perms: Most commands are server-side and require OP (permission level 2+) or a compatible perms plugin.
Help: /rubbletrouble help [page]
Zone management
Manage locked/protected zones that control rubble behavior.
/rubbletrouble zone list
/rubbletrouble zone info
/rubbletrouble zone lock
/rubbletrouble zone unlock
(Some builds may also include create/delete/member commands; check /rubbletrouble help for your version.)
Admin tools
Quick controls for operators.
/rubbletrouble bypass <on|off> # Temporarily ignore locked-zone checks for yourself
/rubbletrouble debug <on|off> # Toggle verbose logging
/rubbletrouble reload # Reload server config (if supported in your build)
Utilities (if present)
Handy helpers that may be included depending on the build.
/rubbletrouble stage set <0-3> # Force rubble visual stage at your crosshair
/rubbletrouble give <loose_rubble|...> # Give registered items (admin testing)
Tip: if a subcommand isn’t recognized in your build, use /rubbletrouble help (or /help rubbletrouble) to see the exact commands that shipped with this version.
❓FAQ
Spoiler
Q: Why does rubble “come back” in certain areas?
A: You’re in a locked/protected zone. That’s intended—motors and manual effort can still help, but drills won’t grief protected builds.
Q: My creative player can’t break rubble!
A: Ensure lockedZone.creativeBypass = true (server config). Only real players (not fake/deployer) qualify.
Q: Do I need Create installed?
A: Nope. If present, contraptions near motors will still “poke” rubble. Without Create, everything else works the same.
Q: Can I use the rubble textures/stages purely for aesthetics?
A: Yes—enable stage visuals and place rubble/loose rubble anywhere for ambience.
🛠 Troubleshooting
Spoiler
Drops vanish in protected areas: your drop-cleanup plugin/mod may be too aggressive. Whitelist loose_rubble or use the provided “allowed drops” tag if included in your pack.
Motor doesn’t work after relog: fixed in recent versions; make sure you’re on the latest build so motors re-register on chunk load.
Textures purple/black: verify your blockstate property (stage or crumble) matches the blockstate JSON and texture names.
📜 License & Permissions
Server packs and modpacks: allowed—please link back to this page.
You may make forks for your server; credit is appreciated.
Available Versions
How to Install Rubble Trouble on Your Server
Order Server
Order a Minecraft Java server with at least 3 GB RAM (4 GB recommended).
Set forge Loader
In the panel under "Egg", select the forge loader and matching Minecraft version (1.20.1).
Install Mod
Open the mod browser in the dashboard and search for "Rubble Trouble". Click "Install" – done! Alternatively, upload the .jar via SFTP to the /mods folder.
Compatibility
Mod Loaders
Minecraft Versions
1.20.1
Server-side
✓ RequiredRecommended RAM
4 GB(min. 3 GB)Frequently Asked Questions
Rubble Trouble server crashes on startup – what to do?
Most common cause: wrong forge version or insufficient RAM. Check the server log (latest.log) for "OutOfMemoryError" or "Mixin" errors. With Mado Hosting: ensure at least 3 GB RAM is allocated and the loader matches the mod version (1.20.1). You can switch loaders with one click in the panel.
Is Rubble Trouble compatible with forge?
Rubble Trouble officially supports forge for Minecraft 1.20.1. The Mado dashboard automatically detects incompatible loader combinations.
Server lagging with Rubble Trouble – how to optimize performance?
Recommended RAM: 4 GB (per 8 players). Use /spark profiler to check if Rubble Trouble consumes the most tick time. Common fixes: reduce server view-distance to 8-10, install "performant" or "starlight" as supplementary mods on Forge. With Mado Hosting, your server runs on NVMe SSDs with dedicated CPU cores for minimal latency.
Similar Mods
Rent Modded Server
Install Rubble Trouble with just one click on your server.