Installation

Install

1. Drop the ac_chat folder into your resources (for example [communication]/ac_chat).
2. Add ensure ac_chat to your server.cfg.
3. Stop any other chat resource (the default chat, or another paid chat). Two resources that provide 'chat' will fight over the UI.
4. Restart. It auto detects your framework, nothing else to set up.

Grant the staff permission (read this)

Staff commands (/announce, /clearchat, /mutechat, and so on) and the Staff channel are gated by an ACE permission. By default that is qbcore.mod, and nobody has it until you grant it. That is why even you, the owner, see "You do not have permission" at first. This is correct: these are staff tools, not open to everyone.

Grant it, pick one:

# 1) One person, by license (find your license in txAdmin, Players)
add_ace identifier.license:YOURLICENSE "qbcore.mod" allow
 
# 2) A whole group you already use (then your txAdmin admins qualify)
add_ace group.admin "qbcore.mod" allow

Or change Config.Admin.perm to an ACE your server already gives staff (for example group.admin). Any ACE string works. The same applies to the per channel perm in Config.Channels.

Out of the box, AC Chat already accepts a range of common staff ACEs (command, group.admin, qbcore.mod, mod, admin, god) via Config.StaffAces, so most txAdmin and QBCore setups work without extra steps. Trim that list to tighten access.

Framework support

Everything works on every framework: channels, RP commands, moderation, autocomplete, settings, Discord. The only framework specific parts are:

• Character names. On QBCore, QBox, and ESX you get the RP character name. On standalone it uses the player's platform name.
• Job channel. Needs a framework that has jobs. On standalone the Job channel is simply not used. Remove it from Config.Channels if you do not want it.

No database

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