Troubleshooting

Find the relevant symptom

Start with Common Issues, which separates configuration mistakes, release-specific fixes and cases still needing diagnosis. Use Installation to check dependency order and the files expected by your release.

Short diagnostic session

In shared/config.lua, leave Config.DevMode = false and temporarily enable Config.Debug only while reproducing the issue. Restore the previous debug value afterwards. For a performance report, capture the affected craft or station in a profiler and include the configuration size. Lowering Config.SaveInterval increases database save frequency; it is not a general speed fix.

Send a reproducible report

Include the resource version from fxmanifest.lua, framework and inventory versions, exact steps, expected result, actual result, and the first client F8 and server-console error. If another resource is involved, identify its purpose and the integration used. Use a test character where practical.

Preserve data while investigating. Do not delete player records, invent a character identifier, replace a failed callback with a dummy success, or raise everyone's permissions to make an error disappear. Remove credentials and unrelated player information from logs or screenshots before sending them to support.