Most garage scripts handle the basics — store a car, take it out — and call it done. mGarage by CodeM goes further: it tracks odometer readings per vehicle, ties storage access to job grades, and pulls Discord profile pictures into the UI so players see actual squad avatars next to their fleet. That last detail sounds cosmetic, but it’s the kind of polish that makes a server feel built rather than assembled.

What mGarage Handles

• Unlimited vehicle slots with class-based weight organisation
• Job-restricted garages with grade-level access control — only the right rank gets in
• Impound management with configurable release fees and money types
• Shared garage support for gang and faction vehicle pools
• Mileage tracking displayed in KM or MI, configurable per server
• Repair cost system with adjustable pricing per vehicle class
• In-UI vehicle transfer and secondhand sale — no external script needed
• Discord profile picture integration via bot token (optional but clean when live)
• Fuel system compatibility with Legacy Fuel or custom resource bridges
• Interaction handler choice: drawtext, drawmarker, or qb-target

Framework and Database Compatibility

mGarage runs on ESX, QBCore (both legacy and newer builds), and Qbox. Database support covers oxmysql, ghmattimysql, and mysql-async — your existing stack stays intact. The script requires FiveM artifacts at gamebuild 2699 or above and OneSync enabled, which is standard for any modern server. Custom and modded vehicles are supported through the configuration files without any core edits.

Configuration Depth

The config exposes pricing, money types, fuel bridge selection, notification style, camera positioning per garage, and the vehicle plate format for job bays. There’s enough surface area here to adapt mGarage to a strict police fleet system or a civilian lot with equal ease. The camera angle control alone saves the back-and-forth of editing source files for every new garage location.

Why It Fits a Managed Server

CodeM built mGarage as part of their M-series essential resources — the same team behind a cohesive set of FiveM infrastructure scripts. That design lineage shows in the way job-garage access ties cleanly into existing ESX/QBCore job tables without a custom bridge layer. Server owners running multiple CodeM resources get consistent config patterns across the board, which cuts setup time significantly when expanding.