ARVEE is a Discord RPG with optional server-management tools. This section explains how to use the features connected to Server Members Intent and Message Content Intent. It is intended for server administrators, community members, and reviewers evaluating the app.
The ARVEE server dashboard lets people with appropriate Discord server permissions configure modules. The RPG itself primarily uses Discord slash commands and interactive buttons. Individual text-command and server-management features are opt-in.
Choose a feature guide
- Member events, welcome messages and roles — configure automatic welcomes and goodbyes, ordinary join roles, verification, onboarding workflows, and anti-raid alerts.
- Text commands, moderation and message features — configure optional text commands, message filters, community chat XP, message-triggered automations, and starboard.
Which privileged intents does ARVEE use?
| Intent | Why ARVEE requests it | Examples |
|---|---|---|
| Server Members | Receive joins, departures, and membership updates for configured community features | Welcome messages, join roles, screening completion, anti-raid |
| Message Content | Recognize opted-in text commands and inspect messages for enabled server features | Text commands, moderation, chat leveling, workflow triggers, starboard |
| Presence | Not requested by the current bot client | ARVEE can set its own bot activity without reading member presence |
A server administrator must enable and configure optional server modules. Some features require channel and role permissions in addition to an enabled intent.
Quick setup
- Invite ARVEE through its bot listing.
- Sign in at ARVEE Hub with Discord.
- Open the server dashboard, then choose a server where you have Manage Server permission.
- Select a module such as Welcome & goodbye, Roles, Moderation, or RPG & commands.
- Configure channels, roles, and any relevant permissions; select Save changes.
- Test the configured feature with a separate ordinary member account in a Discord test server. A saved setting is not proof that a live Discord event was delivered successfully.
Features labeled Premium have additional entitlement requirements; ordinary free features do not require a purchase.
Evidence for Discord's application review
These pages explain the implemented feature behavior and show administrators how to reproduce it. They do not replace Discord's request for a publicly accessible screenshot or video showing each requested intent working within a Discord server. Record actual outcomes in a test server, remove unnecessary personal information, and provide those real media links separately in the application form.
The member-events guide and message-content guide each include a suggested demonstration checklist.
Privacy, support, and data requests
ARVEE processes Discord account identifiers, server settings, and activity information needed for the enabled features. Some account-linked RPG progress and community leveling records persist beyond 30 days. Optional support-ticket intake, notes and transcripts may store message text under separate controls; ordinary moderation does not automatically create a permanent archive of every server message. Retention depends on the type of record.
Server administrators can disable optional features, but this is not a guarantee of an individual per-user opt-out from every server-level message-processing feature.
- Privacy Policy
- Support and privacy requests
- Privacy email: privacy@arvee.world
- Discord command reference
Availability note: Documentation describes implemented behavior in the ARVEE source. Deployment status, enabled server settings, granted permissions and Discord connectivity determine what is available in a particular server.