Skip to main content

Troubleshooting

Use these checks if HSC ChaosMod does not start, the HUD is missing, or events do not fire.

Resource does not start​

  1. Confirm the folder is called ChaosMod (if you used ensure ChaosMod).
  2. Make sure fxmanifest.lua is directly inside the folder, not inside an extra nested ChaosMod/ directory.
  3. Check the server console for Lua errors or resource start failures.
  4. Confirm that client/, server/, shared/, and web/ files were extracted intact.
  5. Run ensure ChaosMod in the server console.

Countdown HUD is missing​

  • Confirm Config.UI.Enabled = true.
  • Confirm the resource starts and the player has finished joining.
  • Check F8 for NUI JavaScript or Lua errors.
  • Check that web/index.html, web/style.css, and web/app.js exist and are listed in fxmanifest.lua.
  • The HUD may be intentionally hidden with Config.UI.ShowWhenPaused = false while chaos is paused or disabled.
  • The overlay normally appears near the top center; check Config.UI.TopPx and Config.UI.WidthPx.
  • Restart the resource after changing configuration or web assets.

Timer is not triggering effects​

  • Verify Config.Enabled = true, or run /chaos on as an authorized admin.
  • Check /chaos status to see whether the timer is paused or disabled.
  • With Config.SkipWhenEmpty = true, automatic events do not run while nobody is online.
  • Look at Config.IntervalMs and any chaosmod_eventtimer convar override in server.cfg.
  • If filters leave no eligible effect IDs, nothing can be selected. Run /chaos list to inspect the pool.
  • If Config.LiveSafeMode = true, only the allowed IDs in Config.LiveSafeEffects can play.
  • The automatic interval is measured between effect starts. Some effects have shorter or longer durations.

Command says permission denied​

Default required ACE:

add_ace group.admin chaosmod.admin allow

Ensure your user belongs to the configured admin group and Config.AdminAce matches the ACE entry. Test chaos status in the server console, which bypasses player ACE checks.

An effect cannot be forced​

  • Run /chaos list to find allowed IDs.
  • Use an exact ID such as /chaos force miscFireworks (not the friendly display name).
  • Review the live-safe allowlist, destructive filter, weather filter, and disabled ID table.
  • playerSwap needs at least two connected players.

Weather looks wrong or keeps changing​

Leave Config.WeatherEffects = false if another resource controls weather. Weather-category effects use GTA/FiveM client weather override natives and can conflict with other synchronization resources.

Spawned vehicles, props, or other effects persist​

Cleanup is best-effort. A spawned vehicle may remain if occupied or if it cannot be deleted. Instant effects such as teleports or tyre damage are not automatically reversed. Consider excluding those effects for persistent roleplay environments.

Anticheat or script conflicts​

Some effects intentionally create entities, teleport players, modify weapons, apply explosions, or change vehicle properties. Anticheat, inventory, weather, spawn, camera, and persistence resources may react to these operations. Temporarily switch to the restricted preset and test individual effects in a staging environment.

Debug logging​

In config.lua:

Config.Debug = true

Or in server.cfg:

set chaosmod_debug true

Capture relevant server console and client F8 output. Avoid sharing passwords, API tokens, license keys, or private player data with public support channels.

Version label mismatch in the supplied archive​

The supplied fxmanifest.lua declares version '1.0.0', but server/main.lua prints a Modern v2.1.1 live edition startup message. This guide follows the manifest version. Align the version strings before release if the console log should show the same version.

Support information to include​

Provide the resource folder name, relevant configs (with secrets removed), the exact command/effect ID used, server/client errors, server artifact version, and steps needed to reproduce the problem.