Resolución de problemas
Troubleshooting
Problemas comunes y cómo solucionarlos.
Two chat boxes / duplicate chat
Cause: the default chat resource is still running alongside BUPA Chat. Because BUPA Chat provide 'chat', both register as chat.
Fix: stop or remove the stock chat resource. Do not ensure chat anywhere in your config — only ensure bupa-chat.
Resource won't start / UI is blank
Cause: a missing dependency. BUPA Chat depends on ox_lib, qb-core and declares dependency '/assetpacks'.
Fix: ensure all three start before BUPA Chat:
ensure ox_lib
ensure qb-core
ensure assetpacks
ensure bupa-chatIf assetpacks is missing, the packaged UI assets fail to load and the chat never appears.
No messages showing
- Make sure other resources send messages via the standard API —
chat:addMessage(event) orexports.chat:addMessage(...). See Developer API. - For category messages, confirm the player actually has access:
permissions(ACE),jobsorgangson the category must match. A player without access never sees or uses that tab. - Check
maxLengthon the category — overly long messages are truncated, not dropped, but a mismatchedtypein a custom integration will be ignored.
Suggestions not appearing
- Command suggestions are built from registered commands the player is ACE-allowed to use (
command.<name>). If a command isn't ACE-permitted for that player, it won't be suggested. - Suggestions refresh on player load and when resources start/stop. If a newly registered command doesn't appear, restart the providing resource or re-open chat.
- For custom help text/params, push them explicitly with
chat:addSuggestion/chat:addSuggestions.
Everything is in English (or the wrong language)
Cause: the locale convar isn't set, so BUPA Chat falls back to en.
Fix: set the language in server.cfg:
setr ox:locale "tr"
# or force only chat:
setr bupa-chat:locale "tr"Remember bupa-chat:locale overrides ox:locale. For a live change use the bupa:changeLanguage client event. See Localization.
Missing translations show the key name
t() returns the key (e.g. CATEGORY_ADMIN_LABEL) when a translation is missing from the active language file. Add the missing key to that locales/<code>.json, or copy it from en.json.
qb-core / framework not detected
Cause: the framework core started after (or isn't running when) BUPA Chat boots.
Fix: ensure qb-core (or qbx_core / es_extended) starts before BUPA Chat. The framework bridge auto-detects Qbox, QB-Core and ESX; you can also pin or disable it with the bupa-chat:framework convar (default qb-core; set to false to run frameworkless).
Discord logging / bridge not working
- Webhook logs not arriving: confirm the URLs in
server/webhook.luaare real Discord webhook URLs and not the placeholder values. - Discord → chat bridge silent: in
shared/config/discord.lua, setactive = true, fill inchannelId, and provide a bot token + guild ID (inconfig.discordor reused fromconfig.adminChatName.discord). Bot-authored messages are intentionally ignored.