Server Identity Layer
Every backend gets a stable machine ID, friendly display name and server type shared across VoidedCore, private Discord integration and website status surfaces.
Roadmap 6 builds the real cross-server layer: stable backend identities, network player presence, shared tab and scoreboard displays, a Velocity bridge, switch events, placeholders, staff visibility and network navigation.
Updates 51–60 are shipped: stable server identities, network presence, cross-server tab and scoreboard surfaces, the Velocity bridge, server-switch events, placeholders, per-server display controls, vanish-aware staff visibility and player navigation are now one connected layer.
Every backend gets a stable machine ID, friendly display name and server type shared across VoidedCore, private Discord integration and website status surfaces.
Track network_user_id, UUID, current backend, join time, last switch and online state across the network.
Show players from the full network grouped by backend with friendly server labels.
Configurable network totals, current backend, server populations, staff counts and other shared lines.
A dedicated Velocity bridge sends authoritative proxy and server-switch data to VoidedCore instead of guessing from Bukkit.
Emit player.server_changed and related network events into the Roadmap 5 event bus.
Expose current server, display name, network online counts and per-backend counts through Voided placeholders.
Aliases, colors, icons, ordering and visibility settings for network display surfaces.
Optional vanish-aware staff presence showing where network staff are currently online.
Server selector commands, GUI navigation and Velocity transfer hooks using the shared identity layer.
Updates 41–50 are shipped: unified identity and profiles, role synchronization, moderation cases, cross-platform notifications and progression, staff operations, Network API v2/event bus, CI/CD and staged deployments.
One internal network identity linking Discord, Minecraft, website and opted-in external creator identities.
One configurable profile surface for Minecraft, Discord, community progression, creator links, badges and privacy controls.
Rules-based Minecraft rank, Discord role and website permission synchronization with loop protection and guild scoping.
Global case IDs and shared Minecraft, Discord and website moderation history, management and appeals.
One notification service delivering to website, Discord and Minecraft with user-controlled preferences.
Cross-platform achievements and quests that can combine Minecraft and community activity with shared rewards.
A central WebStaff operations console for servers, bot instances, moderation, alerts, claims, tickets and platform health.
Versioned authenticated API and shared event bus connecting VoidedCore, private network services and the website without brittle direct coupling.
Private source repositories, automated validation/builds, tagged releases, checksums and deployment tracking across all three projects.
Safe staged updates with release notes, backups, checksums, health checks and rollback across the complete VoidedNetwork stack.
Roadmap 4 delivered the complete creator and streaming platform: integrations, live alerts, creator profiles, scheduling, clips/VODs, viewer rewards, memberships, collaborations, creator safety, sponsors and operations analytics.
Roadmap 3 delivered the shared MySQL platform, unified identity, progression/economy, quests and seasons, Events 2.0, support tooling, advanced staff management, notifications and multi-instance high availability.
Roadmap 2 delivered self roles, scheduled community tools, analytics, appeals/reports, applications, cross-platform rewards, branding, subscriptions, config rollback and the Developer API.
Every guild stays isolated, website permissions remain guild-scoped, the bot remains globally installable, secrets remain private, and Minecraft integration continues through authenticated VoidedCore APIs. Each completed roadmap remains here as release history. Future work will be published as a new roadmap rather than changing the shipped status of Roadmap 5.