Troubleshooting

Common problems and how to resolve them.

Most often more_lib or oxmysql isn't started before more_dispatch — check your server.cfg order and the console for "attempt to call a nil value" errors on start. Also confirm the sql/install.sql script was imported so the more_dispatch table exists.

Only jobs listed in MS.Jobs (backend/config/cl_config.lua) can open the board — you'll see the no_access locale message otherwise. If it still doesn't open for an allowed job, check the F8 client console for NUI errors and confirm frontend/index.html is included via the files{} block in fxmanifest.lua.

Set MS.Discord.enabled to true and paste a valid webhook URL into MS.Discord.webhook in backend/config/sv_config.lua. Also check that the specific event (created/accepted/closed/deleted) is enabled in MS.Discord.events, and watch the console — MS.Debug logs a warning if the webhook returns a non-200/204 status.

Confirm MS.Settings.phone in cl_config.lua matches the phone resource you actually run ("lb-phone" or "roadphone"), and that it's started. MS.CallPhoneNumber silently returns false if the dispatch has no known reporter phone number, or if the target resource's export throws — check the console with MS.Settings.dev_mode enabled. For any other phone system, add your own integration in the "-- integrate your custom phone here" section of sv_config.lua.

Set MS.Locale in cl_config.lua to "de" or "en" — it must match a key present in MS.Locales. Raw keys (e.g. "reporter_created" shown literally) mean GetLang couldn't find that key in either the active locale or the "en" fallback; check backend/locale/*.lua loaded correctly and the key is spelled exactly as used in the script. Add new languages by creating another backend/locale/xx.lua following the same structure as de.lua/en.lua.

Last updated