Features
The whole toolkit,
in one record.
Fracture is not eight tools bolted together. Punishments, logs, reports, profiles and purchases all hang off the same player, so answering “what actually happened” takes one page and no guesswork.
Punishments
A punishment is a record, not a line in a text file. Every ban carries its evidence, its issuing staff member, its expiry and its appeal — and it follows the player across every server you run.
- Bans, kicks, warns, mutes and gags from in-game or the panel
- Cross-server sync — one ban covers the whole network
- Automatic escalation rules (three warns becomes a ban)
- Appeals with a threaded reply history
- Evidence attached to the record: screenshots, log excerpts, clips
Logging & forensics
Most log systems give you a wall of text. Fracture gives you a timeline you can filter, pivot and share — reconstruct an incident in a minute instead of scrolling for twenty.
- Kills, damage, chat, purchases, entity spawns and staff actions
- Filter by player, region, server, time window or event type
- Pivot from any line to that player's full session
- Shareable incident links for your staff channel
- Retention set by your plan, exportable as CSV or JSON
Live dashboard
Player counts, staff on duty, open reports, response times and server health on one screen — updated live, readable on a phone at two in the morning.
- Live player list with join, leave and playtime history
- Staff activity: actions taken, reports closed, time on duty
- Report queue with age and first-response time
- Server health, restarts and crash markers on the same timeline
Player profiles
Open a player and see everything: sessions, punishments, notes, linked accounts, purchases and the last thing they did before you were called.
- Full punishment and note history, staff-attributed
- Alt account detection on IP, hardware and behaviour signals
- Private staff notes that never show to the player
- Purchase and playtime history alongside the record
Web panel
Granular roles mean a trial moderator can warn but not ban, and read logs but not payments. The panel works on a phone, because that is where half of moderation happens.
- Per-permission roles, not fixed staff tiers
- Discord and Steam sign-in
- Audit trail — every panel action is itself logged
- Mobile-first layouts for the whole moderation flow
Rules & automation
Write the rule once and let the server enforce it. Escalation, prop limits, chat filters and scheduled announcements all run with no staff member online.
- Automatic escalation on repeat offences
- Chat and name filters with per-word actions
- Prop, entity and spawn-rate limits
- Scheduled announcements, restarts and wipes
Built for tick budget
Fracture is profiled against a live server, not written and hoped for. Hook dispatch is cached, entity lookups never run per frame, and writes are batched off the main thread.
- Cached hook dispatch — no walk of every listener per call
- No per-frame entity searches anywhere in the hot path
- Batched, asynchronous writes; the tick never waits on a database
- A profiler command that shows you exactly what Fracture costs
Integrations
Fracture reads from and writes to the tools your community already lives in, and exposes an API for the ones we have not thought of.
- Discord: punishment feed, report alerts, role sync
- Import from ULX, SAM, LiteBans and Oxide's own bans
- Webhooks on any event, REST API for everything else
- Tebex and PayPal purchase records on the player profile
In practice
A report, answered in three minutes.
The panel opens on the moment that was reported, not on a search box. Pivot to the player, read the surrounding minute, attach the clip, issue the ban — without leaving the page.
- Jump straight from a report to its timeline
- Every line is a link to that player's session
- Punishments issue from the timeline itself
- Share the incident with your staff channel in one click
- 21:04:12damageVoss hit Karin for 46 (ak47, headshot)
- 21:04:15killVoss killed Karin — 12m, no line of sight
- 21:04:16lootVoss took 4 items from Karin's body
- 21:04:41reportKarin filed a report: “killed through a wall”
- 21:05:02staffmod:Ilse opened the incident timeline
- 21:07:33banmod:Ilse banned Voss — 30d, wallhack, clip attached
Everywhere you run
The same feature set on every game.
Where a platform genuinely differs — Rust wipes, Minecraft block history — the suite adapts. Everything else is identical, on purpose.
Garry's Mod
Lua addon · srcds
- DarkRP
- Sandbox
- TTT
- Helix
- nutscript
- Custom
Rust
Oxide / Carbon plugin
- Oxide/uMod
- Carbon
- Vanilla+
- Modded
Minecraft
Paper / Spigot / Purpur 1.16 – 1.21
- Paper
- Spigot
- Purpur
- Velocity
- BungeeCord
FiveM
Server resource · ESX / QBCore
- ESX
- QBCore
- qbox
- Standalone
Take your server back.
Fourteen days, every feature, no card. If it does not make your staff team faster, walk away and keep your logs.