https://serversidedev.com · serversidestudio@gmail.com The software game communities run on — the servers, the bots, the automation and the monitoring.
Not games. The things that keep the people playing them organised, supported and online. The customer is whoever runs a community: a FiveM server owner, a WoW guild officer, a Discord admin.
🎮 FiveM server engineering — script installs and framework ports, database work, vehicle fleets, economy balancing, crash diagnosis to root cause, live deploys.
⚔️ World of Warcraft guild tooling — built on Blizzard's Game Data API. Drop lookups, gear checks, talents and rotations from live SimulationCraft data, roles that assign themselves from real character data.
💬 Discord builds — whole servers: structure, roles, permissions, onboarding, ticket systems, Linked Roles, and the bots behind them.
🤖 Automation — the part that makes one operator run like a team. Reporting, monitoring, billing, scheduled jobs, alerts that fire before anyone notices.
Why did my FiveM server crash? Paste your console log. 31 diagnostic rules read it and name the cause — pool exhaustion, a resource ensured but not installed, two scripts fighting over the same command. No account, nothing stored.
fivem-fleet-texture-audit Measures what a vehicle fleet costs in texture memory, and how much of it is waste. On a real 203-car fleet: 17.6 GB of textures, 37% recoverable by compression alone.
wow-transmog-index Reverse-indexes WoW item sources from Blizzard's API — item to boss, profession and transmog set. 19,065 items in about 120 KB, small enough to ship inside a Worker.
A popular carry script was a Discord token stealer. Circulating widely, caught in a pre-deploy scan before it reached a live server. Every third-party pack gets read first, regardless of how popular it is or who recommended it.
A server nobody could join, and it wasn't the car. Players crashed on connect and on
mounting vehicles. The obvious suspect was a bad vehicle — pulled twice, no change. The
actual cause was the engine's texture pool ceiling, a hard clamp that ignores what
gameconfig.xml asks for. Model-count headroom was fine, which is exactly why every
earlier fix looked reasonable and changed nothing.
A garage that emptied itself, with no error anywhere. No player could withdraw a car. Resources started clean, queries ran, zero errors across 31,000 log lines. The server was healthy; the database believed all 454 vehicles were already out being driven. Reported to me as "the dealership is broken", which it was not.
Three exploits inside a script I was only asked to convert. The worst let any player give themselves any item, in any quantity — no job, no cost, no log entry. Fixed and reported rather than silently patched.
A black screen nobody could get past, on a server with a clean console. Players
connected, the loading screen finished, and then nothing — no crash, no error, no kick.
Two unrelated faults stacked. An inventory crash from a database table whose columns had
been hand-typed wrong, two of them literally named 0 and 1, was hiding the real one:
twenty-two paid resources silently refusing to start because a subscription had lapsed,
the character selector among them. Nothing was crashing. It was waiting. Found in an
evening, from logs, with no prior access to the server.
Flat quotes in writing before anything starts. Nothing installed on credit. Work you've paid for is never removed, for any reason — a payment problem pauses labour, it never touches your players' experience.
"HE GOT IT TO WORK!!!!" — server owner, after a three-resource install that had already crashed his server once
📬 Open a ticket in the Serverside Discord