Troubleshoot Raid System

The resource or contacts do not appear#

• Check version 1.2.0 in fxmanifest.lua and that the resource folder contains the complete matching archive.
• Check ox_lib, ox_target, ox_inventory, and the QB core export are available before XSC_Raids starts.
• Read the first server/client console error. Error reading file or Failed to load configuration messages point to a missing path or invalid Lua table.
• Match each config path in the manifest and the server loader, including letter case on Linux.
• Check startingPed/endingPed models and coordinates against the installed map. For Weapon Raid, verify Cayo and access to the island.

For a Cfx entitlement error, verify the account associated with the server licence owns the purchased asset and reinstall the complete entitled download. Preserve the delivery's Cfx files.

Starting or searching does not work#

• Start through the contact's ox_target action. This version does not register a /raid crew command.
• You cannot afford this refers to the initiating character's bank balance. Check startCost and the framework's money integration.
• You cannot do this yet indicates the raid cooldown. The cooldown begins on start in version 1.2.0.
• For missing Search Guard actions, wait for the guard-clear notification and stand within the body's target range. Read the client console for failed model/spawn or targeting errors.
• Finding nothing on one guard can be expected: the objective is assigned to one of the spawned guards.

The objective or rewards are missing#

• Confirm objective.item and every loot name are registered and match your inventory's exact identifiers.
• Test the framework's AddItem and RemoveItem integration with ox_inventory. Missing methods or Failed to add item messages need a working inventory bridge, not a different contact location.
• Keep inventory capacity available for both the objective and the rolled reward quantities.
• Use the same character that started the raid and follow its delivery route. No active raid for player means the server has no current operation for that player.
• No loot received this time may mean no configured reward passed its roll. Check server payout errors before assuming the roll was the only cause.

Give support a reproducible example#

Include your manifest version and edition, framework/inventory versions, the raidId, relevant item names, the first server and client error, and the stage that failed. Send a small configuration excerpt rather than credentials or an entire server backup.