This page distinguishes ARVEE Hub features implemented in the source from features verified in production. A passing build or isolated test does not establish that a configured Discord module works in a real server.
Available in the source code
- Discord sign-in and accounts: OAuth, protected sessions, account preferences, logout and permission checks have automated tests.
- Discord RPG profiles: browser profiles use the RPG bot's authoritative player records rather than separate game saves.
- Bot Administration: authorized bot administrators can preview changes to supported game settings, manage maintenance, and use player support controls.
- Website tools: news, status, support, staff audit and website analytics have implemented routes and tests.
- Visual Item Manager: item creation, duplication and editing use native catalog validation and an audited review/commit flow. The RPG expansion branch adds a live preview and a stat-change comparison before review.
Needs real-server verification
- Welcome messages: join handlers and settings exist, but server managers reported failed delivery. A follow-up release adds bot-channel permission validation, membership-screening handling and a manual Send test welcome action. A real new member joining is still required to verify automatic delivery after deployment.
- Moderation, announcements, private tickets, event logs and automatic join roles: the handlers and isolated tests exist. Their actual behavior depends on granted Discord permissions, enabled gateway intents and individual guild configuration. Test each feature before relying on it.
- Browser RPG gameplay: combat, gathering, social actions and cooperative raids have separate feature switches. Their presence in the code does not mean they are enabled on this installation.
In development / not yet deployed
- RPG inventory quality of life (expansion branch): searching, rarity filters, stable sorting by name/quantity/enhancements, inventory totals and quest progress bars are being tested. These are browser-only views of existing data, not changes to rewards or player saves. Item deletion remains unavailable until existing inventories and content references can be safely handled.
- Discord community reach: an overview counter uses the bot's cached guild counts. Combined member counts are estimates and include the same person more than once across servers.
- Minecraft player statistics: proxy status and heartbeats do not provide Prison ranks, pets, skills or other Paper plugin data. Dedicated supported adapters are needed.
- Major RPG expansions: full dungeons, automated matchmaking and a complete economy rebuild are not finished.
How to check live availability
- Check Network status to confirm that the services are online. Online status alone does not confirm feature readiness.
- Open the Server Dashboard, choose a guild that you manage and save the module configuration.
- For welcome messages, enable them, choose a writable channel, save and use Send test welcome. Then test with a real member joining or completing Discord membership screening.
- If a feature fails, share the displayed error and the relevant bot event log, with credentials and private user information removed.
Status descriptions are updated from source and available test evidence. No feature should be presented as verified live merely because its code exists.