What goes wrong most often, what it actually means, and what to do about it. Nearly every case comes down to one of three things: a missing permission, another map in the same spot, or a client that has not picked up the new files yet. The map prints a line for every step it takes — check them against the table at the bottom before opening a ticket.
Installation and Access#
/mechanicmap does nothing in chat
The command is restricted, and the player lacks command.mechanicmap. Test it from the server console first: if mechanicmap 1 works there, the map is fine and only the permission is missing.
add_ace group.admin command.mechanicmap allow
add_principal identifier.license:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx group.adminNine times out of ten the ace is there but the player's identifier is not in group.admin, or belongs to a different account from the one in game.
The old building is still there, or the shop is empty
Look for [MECHANIC MAP] State loaded in the server console. If it is missing, the resource never started — check that the ensure line matches the folder name exactly.
If it is there, the player is still running on the files from before the install. Have them reconnect; if it persists, clear their FiveM cache and join again.
A key cabinet and a dog bowl are missing
Correct behaviour on an older game build. Those two props come from the Money Fronts update and exist only on build 3570 or newer; everything else loads regardless. Set sv_enforceGameBuild 3570 or higher to see them.
Other props are invisible, or the shop looks half built
A file in stream/ is missing or was renamed — often by an upload that stopped halfway or a tool that "cleaned" the folder. Download the resource again from the CFX Portal and replace the whole stream folder. Keep your map_state.json if you want to keep the current layer.
The Event Layers#
The command ran, but nothing appeared
Open F8 on that player and look for [MECHANIC MAP] Active map set to: 2.
The line is there — the layer is loaded. Event pieces are drawn within about 200 metres, so a player watching from further away sees them appear as they get closer.
The line is missing — that client never received the change. Have them reconnect; on joining, the client asks the server for the current layer by itself.
Some players see the meet and others do not
Reset everyone in two steps:
mechanicmap 0
mechanicmap 2The first clears both layers on every client, the second loads the one you want from scratch. If it keeps happening, another script is triggering mechanicmap:setState directly — see the warning in Commands and Exports.
The layer goes back after a restart
Compare the State loaded line on start with the layer you set. If they differ, the server could not keep map_state.json:
The resource folder is read-only for the server process.
A deploy or sync tool restores the folder from a copy on every start, bringing the old file with it.
A scheduler of your own applies its layer on start, by design.
I edited map_state.json and nothing changed
Correct behaviour. The file is read once, when the resource starts, and overwritten the next time the command runs. On a live server, use the command.
I want the food without the event tables
Not possible, by design. The food is laid out on the event tables, so layer 2 always includes layer 1, and words such as mechanicmap food only print the usage line.
Conflicts With Other Maps#
Players fall through the floor or walk through walls
Another resource replaces the same collision files — sc1_03_0.ybn or hi@sc1_03_0.ybn — and started after Downtown Mechanic, so its version won. Search your other maps' stream folders for the names in Other Maps Nearby and keep only one of the two maps.
Another interior shows through the workshop
Two MLOs are built at the same address. They cannot share it — remove the other one, or move this one off your server.
The building looks wrong from far away
The distant versions of the block — sc1_03_slod_children.ydd and sc1_lod_00bef_01_02_03_children.ydd — are being replaced by another map as well. Same fix: keep one of the two.
Console Messages#
Every line the map prints, and what it means:
Message | Where | Means |
|---|---|---|
| Server, on start | Layer N was restored from |
| Server, on start | There was no file. It was created with layer 0. |
| Server, on start | The file had no |
| Server | The command switched to layer N, saved it and sent it to everyone. |
| Client (F8) | This player now sees layer N. |
| Chat or console | The value was missing or not 0, 1 or 2. Nothing changed. |
Still stuck? Open a ticket and include the server console lines that start with
[MECHANIC MAP], the F8 line from an affected player, yoursv_enforceGameBuild, and the other maps you run near the workshop. A screenshot of the problem in game helps for anything visual.