Documentation / Discord roles

Discord roles

Temporary VIP, in-game VIP exports, Discord staff roles, bot and tickets.

This section covers Discord roles managed from the panel: expiring VIP (readable in-game via Adictos_WebLogs exports), who counts as staff in ticket threads, roles required on ticket panel buttons, and ticket blacklist by role. Not the same as the panel’s Steam permissions (see the Panel permissions section).

Connecting the bot

  1. 1Panel Settings → WebLogs → configure the global bot (recommended) or use your own token.
  2. 2My servers → DiscordBot tab → Invite bot → Connect and detect.
  3. 3After detection, the role and channel drop-downs fill in automatically.
In the Developer Portal enable Server Members Intent. The bot’s role on Discord must be above the VIP roles it is going to assign.

Temporary VIP (Discord VIP)

Assign Discord roles (VIP, VIP+, PRO, etc.) with an expiry date from the panel:

  1. 1My servers → DiscordBot → VIP roles table: choose the roles from your Discord (the role name is the in-game rank).
  2. 2Optional per role: ACE group and ESX job (to use it in-game from your scripts).
  3. 3Configure the staff channel, advance-notice days and automatic messages (DM + channel).
  4. 4Staff with the Discord VIP permission manage assignments in the panel’s Discord VIP menu (also /vip on Discord and giveaway prizes).
  5. 5Expired roles are removed automatically; advance notices are sent according to the days you configure.
Panel permissionCapability
View Discord VIPView VIP assignments
Manage Discord VIPAssign, extend and remove VIP
Discord giveaways (Enter button, VIP/item prizes) are documented in the Giveaways section.

Using VIP in-game (exports)

Adictos_WebLogs caches the panel’s active VIPs on startup and updates them on assign/remove/expiry. From your scripts you can read the player’s rank with these exports (server):

ExportWhat it returns
GetPlayerRank(src)Rank name ("VIP", "VIP+", "PRO"…) or false
GetPlayerRankInfo(src)Details: role_name, esx_job, end_date_ms, …
EnsurePlayerRank(src)Ensures the rank is cached for that player (useful on connect)
HasPlayerRank(src)true if they have any active rank
-- Ejemplo en tu script (servidor)
local src = source
local rank = exports['Adictos_WebLogs']:GetPlayerRank(src)

if rank == 'VIP++' then
    -- ventaja máximo rango
elseif rank == 'VIP+' then
    -- …
elseif rank then
    -- cualquier otro nombre configurado en DiscordBot (VIP, PRO, …)
else
    -- sin VIP
end

local info = exports['Adictos_WebLogs']:GetPlayerRankInfo(src)
-- info.role_name, info.esx_job, info.end_date_ms
-- Al conectar / personaje listo
AddEventHandler('esx:playerLoaded', function(playerId)
    local src = tonumber(playerId) or source
    exports['Adictos_WebLogs']:EnsurePlayerRank(src)
end)

-- Cambio en caliente (panel asignó o caducó VIP)
AddEventHandler('adictos_weblogs:playerVipUpdated', function(src, info)
    print(('VIP src=%s rank=%s'):format(src, tostring(info.role_name)))
end)
The rank is the exact role name from DiscordBot (VIP, PRO, Pro+, …). Compare against that string in your scripts.

Staff roles on Discord

Under My servers → DiscordBot → Staff roles choose the administrator and/or moderator role of your Discord.

  • In ticket threads, anyone with those roles writes as staff (not as a player).
  • They can claim, close and reopen and, inside the ticket, use /add, /remove and the /ticketadd alias with a user or a role.
  • They can use the /vip command in the configured staff channel.

Required role on ticket buttons

Under Ticket settings → Discord panel you can post a message with buttons. Each button can require a specific role (donations, whitelist, community…). Only members with that role can open a ticket from that button.

Ticket blacklist by role

Ticket settings → Blacklist → type Discord role. Prevents anyone with that role from opening tickets (entirely or only in selected categories). Useful to isolate sanction roles or restricted accounts.

Discord ticket bot

A separate worker that syncs threads with the panel. After connecting DiscordBot and configuring channels under Ticket settings → Discord sync, start the bot from Panel Settings → WebLogs.

  • Players: panel buttons, /ticket or the category command (e.g. /new).
  • Staff: in that command, optional objetivo (user or role). The user becomes the owner and is mentioned once; the role joins as with /add, without a mass mention. Inside the ticket, /add and /remove (user or role). /ticketadd is an alias of /add. A role can’t be added to a private thread: its members join instead, up to a limit.
  • Thread messages ↔ web panel and in-game (if the player is linked in players).