Troubleshooting

Resource does not start

Verify that the folder name in server.cfg matches the actual directory. Check that fxmanifest.lua exists directly inside the resource folder and inspect the server console for missing dependencies or syntax errors. Install the missing declared dependencies and restart in the correct order.

UI does not appear

Confirm the resource started, then review the FiveM client F8 console. Ensure the package contains its ui/ or html/ assets and that another resource is not taking conflicting input focus or showing an interface on the same key.

Command not found

Check that you are using the command listed for the installed build, not a command from another version or older product name. Also check whether the command is disabled or renamed in the resource's configuration.

Player cannot use a feature

Check whether the feature is enabled, any effective ACE or role checks, whether the player is close enough to the relevant object/player, and whether the correct player or vehicle state is present. For Scene Dynamics, remember that the reviewed open-access build does not impose general department access gates.

Two resources behave incorrectly together

Temporarily test each resource separately in a controlled staging server to identify which integration overlaps. Focus first on duplicated key mappings, UI focus, fuel ownership, vehicle damage controllers, and voice proximity overrides. Preserve logs and test results rather than disabling unrelated resources at random.

Client and server show different states

Test with at least two connected players and check the server's OneSync configuration. Distinguish a client-only visual effect from a server-managed gameplay state. Some effects intentionally remain local, while others are synchronized by the product.

Data does not persist after restart

Do not assume every product or configuration saves state. Review its persistence settings and the actual storage files/permissions. For example, the reviewed Impact Dynamics README describes plate-based damage persistence as off by default.