About drs_Dev

Mostly one person,
with some help behind the scenes.

drs_Dev is a FiveM development label used by DrSnyder. The name is simple: drs is short for DrSnyder, and _Dev is the development side. Most of the work comes from one person, with help from a few private contributors when a project needs it.

01 / ORIGIN

How it started.

There was no single moment that started drs_Dev. It grew out of a long history with GTA, a return to gaming, and the need to make different server systems work together.

  1. 01
    Late 1990s

    GTA from the early days

    DrSnyder has played Grand Theft Auto since the original PlayStation and PC era.

  2. 02
    During COVID

    Back to GTA through LSPDFR

    After a long break from games, returning to GTA led to LSPDFR, modding, and a closer look at how the game could be changed.

  3. 03
    FivePD

    Trying to make the experience multiplayer

    The next step was running a FivePD server in an attempt to create a multiplayer version of the LSPDFR experience.

  4. 04
    First resource

    ers_integration

    The first drs_Dev resource connected Emergency Response Simulator with the dispatch, duty, inventory, and server systems around it.

02 / APPROACH

Why build any of this?

The short version: useful FiveM resources should be understandable, practical, and available without making every server pay forever.

01 / AN ALTERNATIVE

Free and open when possible.

A lot of useful FiveM assets were escrowed, tied to subscriptions, or simply overpriced. That became a reason to learn how the systems worked and try to build practical alternatives.

The goal is to release work for free and as open source whenever the project and its licensing allow. Every resource page lists its actual source and license status.

02 / HANDS-ON BACKGROUND

Common sense before complexity.

The technical and mechanical side started young and later grew into hands-on experience across electrical, mechanical, automotive, manufacturing, and construction work.

The approach is pretty simple: understand what something is supposed to do, work out why it does not, and find a practical way to make it work.

03 / TOOLBOX

How the work gets made.

Different projects need different tools. The groups below explain what they are used for before listing the exact software and technologies.

01Core development workflowEveryday tools for finding, changing, moving, checking, and versioning files.10 items
  • Codex
  • PowerShell
  • ripgrep
  • Git
  • GitHub CLI
  • curl
  • Robocopy
  • SSH
  • WinRAR / UnRAR
  • Archive and hash utilities
02Languages and runtimesThe code, scripting, markup, and data formats used across different projects.9 items
  • Lua / luac
  • Node.js / npm
  • JavaScript
  • TypeScript
  • Python
  • C# / .NET
  • HTML / CSS
  • JSON / XML
  • PowerShell
03FiveM and GTA toolsTools for resource development, debugging, game files, textures, and map data.6 items
  • FiveM / CitizenFX
  • F8 console
  • CodeWalker.Core
  • SharpDX
  • DirectXTex
  • Custom YMT, YTD, RPF, and RBF command-line tools
04Website and interface toolsLibraries and build tools used for websites and in-game interfaces.11 items
  • Svelte
  • React
  • Vinext
  • Vite
  • Tailwind CSS
  • PostCSS
  • DaisyUI
  • Leaflet
  • Lucide
  • ESLint
  • Svelte Check
05Testing and verificationChecks used to catch broken code, bad data, changed files, and unreliable rebuilds.8 items
  • Lua parsing and assertions
  • Node checks
  • npm build, test, lint, and type checks
  • .NET builds
  • Custom PowerShell validators
  • File hashing
  • Deterministic rebuilds
  • CodeWalker round-trip tests
06Browser checksTools used to inspect pages, test interaction, and check browser behavior.4 items
  • Playwright
  • Headless Chrome
  • Microsoft Edge
  • Codex in-app browser
07Images, audio, and videoTools used to create, inspect, convert, and verify media files.8 items
  • OpenAI ImageGen
  • Pillow
  • NumPy
  • Sharp
  • FFmpeg
  • FFprobe
  • MediaInfo
  • FFmpeg filtergraph scripts
08Publishing and hostingServices used to package releases, run checks, host sites, and share updates.9 items
  • GitHub Actions
  • GitHub Releases
  • Cloudflare Pages
  • Cloudflare Workers
  • Wrangler
  • OpenAI Sites
  • Discord
  • Tebex
  • Google Search Console
09FiveM integrationsFrameworks and community resources connected to individual drs_Dev projects.9 items
  • Qbox / QBCore
  • ESX compatibility
  • ox_lib
  • ox_target
  • ox_inventory
  • oxmysql
  • ox_fuel
  • pma-voice
  • ps-dispatch

These tools have been used across different projects. That does not mean every resource uses or supports every item. Each resource page is the source of truth for its own requirements and compatibility.

See the work

The resources explain the rest.

Each page shows what a resource does, where it came from, what it works with, and where to inspect the files.