Configuration
Configure command permissions and the optional buckets menu via data/cfg.lua.
All configuration lives in data/cfg.lua. Edit the values there and restart the resource — no other files need to change.
return {
useDataTables = true,
commandCooldown = 2000,
ace = {
menu = "god",
killb = "god",
showb = "support",
getpb = "support",
listb = "support",
resetpb = "support",
setpb = "manager",
}
}useDataTables
boolean
Enables the buckets in-game menu, which lists active buckets and lets you inspect or kill them without typing commands. The menu itself is rendered by a separate datatable resource — ip_datatable on FiveM, rw_datatable on RedM — which must be installed and running.
Set this to false if you don't have that resource installed. The buckets command will still exist, it just won't do anything.
commandCooldown is present in this file but is not currently read anywhere in the resource — changing it has no effect on any command.
ace
table<string, string>
Maps each restricted command to the ACE permission a player must hold to run it. Each value is passed straight through as the restricted option of an lib.addCommand registration, so it can be either a bare ace name (as shipped) or a full group.xxx principal string.
| Key | Default | Gates |
|---|---|---|
setpb | manager | Assigning a player's bucket |
resetpb | support | Clearing a player's bucket |
listb | support | Listing active buckets |
getpb | support | Looking up a player's bucket |
showb | support | Showing a bucket's contents |
killb | god | Wiping a bucket |
menu | god | Opening the buckets menu |
See Commands for what each of these actually does.
Because these are raw ace names rather than group.* strings, grant them directly to a principal in server.cfg:
# server.cfg
add_principal identifier.discord:123456789012345678 group.admin
add_ace group.admin god allow
add_ace group.admin support allow
add_ace group.admin manager allowIf you'd rather reuse an existing permission group instead of these bare names, change the values in cfg.ace to that group's principal string (e.g. 'group.admin') — lib.addCommand's restricted option accepts either form.
The buckets menu's Kill and Reset Player row actions are gated by a separate, hardcoded command.rw_buckets ACE — it is not read from cfg.ace and won't change if you edit menu. Grant it alongside menu if players need to use those actions:
add_ace group.admin command.rw_buckets allowResetting an entity row from the menu, and the read-only calls used to populate the menu, currently perform no permission check beyond the player having a valid connection — in practice, menu access is the real gate on who can open the menu at all.