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.
Steady Adventures release — awaiting deployment and verification
- Automatic welcome deduplication shares a cross-process portal database claim across member joins and screening completion, avoiding repeated greeting messages for ten minutes.
- Owner-only Bot Admin/Tester grants and revocations use native review, audit and current-owner permission checks.
- The Guild tab includes headquarters facilities, treasury, shared projects, missions, milestones, achievements and rankings. Reviewed browser actions and
/guild headquartersshare the same saved guild and permissions. - These are implemented in source and tested in isolation; a passing test is not proof of production availability.
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.
Starter journey and DM support release — deployed 13 November 2026
- Browser starter journey: Journey supports challenging the Trail Warden and completing the shared first-adventure reward path. Existing combat and character-action switches still control availability. The release adds keyboard navigation between character sections, guided links to the required reward, mobile action wrapping and account-scoped loading. Desktop and mobile browser checks passed with isolated test characters; live account gameplay was not used for testing.
- DM support: a repair for failed ticket lookup is deployed. New tickets retain their consent prompt, and follow-up messages reuse an accessible open ticket. Automated delivery checks passed; actual delivery still depends on Discord permissions and requires a consenting user's operational check.
In development / not yet deployed
- Browser RPG expansion: inventory search/sorting, native browser crafting, equipment comparisons and existing recipe/enchantment/loot editors are available in the code, subject to runtime configuration. Guild headquarters and the native quest cards are released; access still depends on your character, permissions and enabled capabilities.
- Account sanctions: reviewed account-wide ban/unban applies to both live and tester sandbox saves in the Steady Adventures source. It remains pending deployment and real-admin QA.
- Original project completion: the public completion roadmap summarizes the requirements; the internal full five-phase audit is tracked in
hub/docs/ORIGINAL-REQUIREMENTS-AUDIT.md. 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.
- Next RPG expansions: full seasonal progression and Creator Studio remain unfinished. Existing server competitions are separate from the planned seasonal reward tracks.
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.
Cooperative expeditions — deployed 13 November 2026
Parties of one to four can find teammates, choose roles, confirm ready and explore
three dungeons across Explorer, Veteran and Mythic difficulties. Discord
/expedition and the browser party/RPG pages share saved progress, room choices,
combat and final rewards. See Cooperative Expeditions
for preparation and commands.
The release passed complete fixture journeys on desktop and mobile, native PostgreSQL recovery tests, and live service/permission-boundary checks. Real player gameplay was not used as a release test.