Troubleshooting
Check common installation, access, display and persistence problems.
| Symptom | Check |
|---|---|
| Resource will not start | OneSync and FS-Lib must be available. Keep the correct resource name and start the selected target dependency first. |
| No interaction prompt | Confirm the configured backend is running, you are close to the correct cabinet, and you have entry permission. Signs operate in the base world, routing bucket 0. |
| Signadmin denied | Check the configured admin ACE and your actual principal membership. LUX DOT access does not grant administration. |
| Repair or link controls missing | Check action-specific permissions. Linking also needs operate permission; repair needs cabinet entry. LUX require/replace mode adds its own approval requirement. |
| LUX access denied | Check the private server key, player Discord identifier, exactly one active service, matching service code and that type's road_status module. Unknown/missing/stale data denies LUX approval. |
| Cabinet in use | Another operator may own it. Leaving, death, disconnect or heartbeat expiry releases the session. |
| Text edit rejected | Stay near the cabinet with the active session. Check length limits and reload after a stale revision conflict. |
| Linked message changes other signs | Expected: SHARED MESSAGE means the current target shares content. Unlink before making independent text changes. |
| Directional symbols differ | Expected: linking and forward/reverse sync share text, not symbols. Set arrows per face. |
| Sign stays dark | Check common power, face power, FS-Blackout state and section damage. Changing messages does not repair damage. |
| Map imagery unavailable | Use the searchable list. Confirm the packaged NUI map sheets were installed. |
| Missing or duplicated models | Install the complete current stream folder; do not run the old fs_us_signs alongside it. |
| Saves disabled | Inspect server errors and restore valid writable data/signs.json. Do not replace live data with blank defaults. |
| Placements disappeared after a source build | The current build copies source config and source placement JSON over packaged versions. Restore the live backup and carry it into source before rebuilding. |
| Old UI after an update | Check the installed resource path and compare the actual deployed nui and stream files with your package. Do not assume caching is the cause. |
Before requesting help
Record the resource version, interaction backend, sign ID/type, exact action, error text and whether other signs are affected. Include relevant non-secret configuration and server/client error lines. Never include API keys or player authentication data.
Recovery and safe editing
Back up the live config and entire data folder first. Stop the resource before manually editing placement JSON, then load your repaired copy when ready. A previous-version signs.json.bak may help, but is not a replacement for independent backups.
Saved messages, faults and links persist; cabinet sessions and door state reset on restart. Only the nearest 12 signs within the current 500 m streaming distance are streamed. Those limits are internal constants, not owner config options.
These guides were checked against local source and the documentation build. They do not claim live gameplay, permission-provider or deployment verification.