FAQ & Troubleshooting

Staff commands say "You do not have permission"

This is the number one question, and it is working as intended. Staff commands and the Staff channel are gated by an ACE permission, and nobody has it until you grant it, not even the owner. Grant it (see Installation):

add_ace group.admin "qbcore.mod" allow

Or point Config.Admin.perm at an ACE your staff already hold.

Two chats are showing, or the UI is glitchy

You still have another chat resource running. Stop the default chat or any other paid chat. Two resources that provide 'chat' fight over the UI. Keep only AC Chat.

Names show as platform names, not character names

Character names come from your framework. On QBCore, QBox, and ESX you get the RP name. On standalone there is no character system, so it uses the platform name. Set Config.NameFormat if you want to force platform names everywhere.

The Job channel is empty or unused

The Job channel needs a framework that has jobs. On standalone it is simply not used, and players are told they have no job channel. Remove it from Config.Channels if you do not want it.

Existing scripts that print to chat still work?

Yes. The legacy chat:addMessage, chat:addSuggestion, chat:clear, and chat:removeSuggestion events are supported automatically, so other resources keep printing to chat with no changes.

Where are player settings stored?

Per player settings save locally in the player's game KVP storage. There is no database and no server load. Clearing the FiveM cache resets a player to the server defaults.

What is the version checker?

Nothing you need to touch. It is an optional console notice that can flag a newer release. It is silent by default and fails quietly, so leave it as is. You never host or configure anything, update availability reaches you through Tebex and Cfx asset escrow.

Still stuck? Reach us at scripts.aczone.xyz.