obliterate.gg is a private macro platform for server-specific automation. It is built by one operator with years inside FiveM, proprietary tooling for skillcheck mapping, a low public profile, and a bias toward precise tools over noisy marketing.
3+
years inside FiveM
1:1
server-specific builds
30d
controlled access cycles
Clean screenshots, recordings, routes, inventory layouts, and skillcheck examples.
Timing windows, randomisation, input thresholds, failure states, and recovery paths.
A dedicated implementation for that server instead of a recycled generic macro.
Short-run testing, edge-case fixes, and controlled rollout through licensed accounts.
01
Every build starts with direct footage, timing data, and repeated manual testing. I also use proprietary custom software to simplify the creation and mapping of skillchecks, so each macro is shaped around the server, not the other way around.
02
Configurable registration, per-product licenses, and dashboard downloads keep access controlled and support manageable.
03
The alias is intentional. Less public noise means more focus on shipping stable, server-specific tools.
The alias
The name stays detached from my public identity because the project works better that way. Server developers and community staff do not need a personal profile to study. Customers need stable builds, clear access, and useful support.
Background
I have been around FiveM long enough to understand the servers, the grind loops, and the tiny visual/timing details that make automation either reliable or useless. obliterate.gg is not the first toolset I have shipped in this space, but it is the most controlled version of the work.
Method
I do not start with a generic clicker and force it across servers. I created proprietary custom software that simplifies the creation and mapping of skillchecks, then use that mapped data alongside the actual UI, route, inventory state, and timing window the server uses.
Access
Registration can be invite-gated, products are licensed one at a time, and downloads stay inside user dashboards. That keeps the project smaller, support cleaner, and updates easier to manage.
I pay for clean skillcheck footage from servers I have not covered yet. Good captures can turn into a product, and scouts get a finder's percentage on every sale that follows.
Useful scouting means steady footage, readable UI, clear resolution, and enough context to reproduce the job loop. Use the scout banner when it appears to apply.