Our Discord Bots

In-server item shop, support tickets, and cross-server chat bridge.

PX Shop lets server members buy in-game items and kits with credits, and claim them directly to their ARK: Survival Ascended character via RCON. It also runs the server's support-ticket category and an optional cross-server chat bridge that relays messages between linked Discord servers.

Why it needs Server Members Intent

To resolve a server's configured admin list and ticket-category permissions against real guild members, and to check role membership when gating shop features or ticket-category access.

Why it needs Message Content Intent

Two features read message content: (1) the cross-server chat bridge, which reads a message posted in a designated bridge channel so it can repost it (via webhook) into the linked server's own bridge channel; and (2) per-season activity tracking, which counts admin messages inside ticket channels toward season stats shown on the leaderboard. Message content outside these specific channels is not read or stored.

ARK stat tracking, alpha-tribe scoring, rewards, raffles, and role automation.

PX Leaderboard parses a server's ARK log files to build kill/death/playtime/structure stats per player and tribe, and turns them into a live leaderboard, an "alpha tribe" score, and a battle-pass style season-rewards system. It also runs raffles, public player reviews, invite-tier and name-keyword ("ambassador") role automation, dupe detection, and admin tools like global bans and grantable season roles.

Why it needs Server Members Intent

Nearly every automation feature works by comparing the current member/role list against a target set and adding or removing roles: leaderboard-rank roles, loot-tier roles, invite-count tier roles, and "ambassador" roles based on a configurable name keyword. This requires enumerating `guild.members` / `role.members` — it cannot be done from slash-command interactions alone.

Message Content / Presence

PX Leaderboard does not request Message Content Intent or Presence Intent. It has no prefix commands that read message text, and no feature reads a member's online status or activity — "presence" in this bot only ever refers to whether a player is currently online in the ARK server, which is determined entirely from the ARK server's own logs, not from Discord.

AI-assisted support ticket intake and conversation.

PX Utils runs inside support-ticket channels once a member opens a ticket. It asks a short structured intake questionnaire, then hands the conversation to an AI agent that can answer common questions and triage the request, escalating to human staff when needed. It also maintains a ticket dashboard showing who claimed and closed each ticket.

Why it needs Server Members Intent

The ticket dashboard resolves the Discord user IDs stored against a ticket's "claimed by" / "closed by" fields into member display names via `guild.get_member()`, so staff see readable names instead of raw IDs.

Why it needs Message Content Intent

The bot only reads message content inside a member's own open ticket channel — never server-wide. Content there is used to: (1) capture the member's answers during ticket intake, and (2) send the conversation to our AI provider's chat-completion API to generate the agent's replies. Message content is not read in any regular server channel.

AI / machine learning

Ticket message content is sent to a third-party AI provider's API purely to generate a live response — it is not used to train, fine-tune, or improve any AI model, ours or the provider's.