Map Editor Commands

In game

Command	Does
/mapeditor	Open the editor
/mapedit	Same
/medit	Same
/rm_unstick	Reset the camera and interface focus
/rm_diag	Run diagnostics

All three opening commands are the same thing. Rename them:

Config.Command = 'mapeditor'
Config.CommandAliases = { 'mapedit', 'medit' }

/rm_unstick

Puts you back in your body and releases the interface focus.

Worth telling your builders about before they need it — a client that loses focus mid-edit looks like a frozen game, and this fixes it without a relog.

From the server console, for someone else:

rm_mapeditor_unstick <id>

/rm_diag

The one to run before asking for help. It checks the editor against itself and prints what it finds.

Form	Reports
/rm_diag	A general check
/rm_diag keys	What every key binding resolved to
/rm_diag perf	Performance figures
/rm_diag net	The network side
/rm_diag all	Everything

/rm_diag keys is the one people need

A binding whose name the game does not recognise does nothing and says nothing. This prints what each one actually resolved to, which turns "my undo key is broken" into "that is a typo in config.lua".

Diagnostic extras

Also registered client-side, and useful mainly when you are reporting something:

Command	Does
/rm_perf	Performance figures
/rm_selftest	A self-test pass
/rm_trace	Tracing output
/rm_mapeditor_debug	Debug output
/rm_mapeditor_diag_problems	Problems the resource has noticed

These are verbose and aimed at diagnosis rather than daily use.

Server console

Command	Does
rm_mapeditor_stats	Maps, objects and open editor sessions
rm_mapeditor_reload	Re-read every map from the database
rm_mapeditor_unstick <id>	Reset a stuck player
rm_mapeditor_diag	Server-side diagnostics

rm_mapeditor_stats

The quickest health check. If object counts are growing faster than you expected, that is where you see it first.

rm_mapeditor_reload

Needed whenever something changed the tables behind the resource's back — a row edited in a SQL client, a backup restored, or a second server writing to the same database. The resource does not poll.

rm_mapeditor_diag

Reports the permission configuration, the database state and the export/import settings as the server sees them. When a player is refused and you expect otherwise, this tells you what the server believes, which is the half that matters.

Hold-to-act bindings

Four internal commands exist for held keys — +rm_lift / -rm_lift and +rm_smooth / -rm_smooth. You do not type these; they are what a hold-style binding is wired to.

Opening it from another resource

TriggerEvent('rm_mapeditor:openEditor')

The event name is a setting:

Config.OpenEvent = 'rm_mapeditor:openEditor'

Pick a name the resource does not already use

It checks at start-up and prints a red warning naming the clash — but the editor will not open from it. See the Developer API.

Or use the export:

exports.rm_mapeditor:open()

Both honour the same permission check as the command. Neither is a way around it.