Common Errors

Common Errors — Downtown Mechanic | Quasar Store | Quasar Store

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.

bash

add_ace group.admin command.mechanicmap allow
add_principal identifier.license:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx group.admin

Nine times out of ten the ace is there but the player's identifier is not in , or belongs to a different account from the one in game.

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:

bash

mechanicmap 0
mechanicmap 2

The 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.

Message	Where	Means
`[MECHANIC MAP] State loaded: N`	Server, on start	Layer N was restored from `map_state.json`.
`[MECHANIC MAP] File not found, creating default state.`	Server, on start	There was no file. It was created with layer 0.
`[MECHANIC MAP] Invalid JSON, creating default state.`	Server, on start	The file had no `activeMap`. It was rewritten with layer 0.
`[MECHANIC MAP] State updated: N`	Server	The command switched to layer N, saved it and sent it to everyone.
`[MECHANIC MAP] Active map set to: N`	Client (F8)	This player now sees layer N.
`Usage: /mechanicmap [0-2] …`	Chat or console	The value was missing or not 0, 1 or 2. Nothing changed.

Common Errors

Installation and Access#

The Event Layers#

Conflicts With Other Maps#

Console Messages#