The server core is implemented in Rust, with performance, reliability, and clear module boundaries as priorities.
Designed around Minecraft Java Edition server workloads without unrelated runtimes.
Services, configuration, and networking keep focused responsibilities for gradual extension and maintenance.
Rust's type system and explicit error handling reduce runtime uncertainty.
Feature status is calibrated against qexed/Qexed@f57af391ad79823aac42b78399cefdc381ed31fc, covering major changes across the commit range since c5b8c2d86c1fc33bed49e70088bef16b32e303d8. Solid cards are closed in source; dashed cards are incomplete or partial.
Current server performance for lobby scenarios is still not ideal, and optimization is not finished yet.
Native i18n support is available.
Auto-injects configuration annotations with multi-language support.
Supports economy APIs backed by local storage and databases.
NPC functionality is integrated natively.
Common baseline sidebar/scoreboard capability.
LuckPerms-like permission management model.
Common chest-menu functionality.
Players should not be able to damage lobby worlds.
Lobby servers usually do not need persistent player inventory/achievement data.
In typical lobby setups, most block interactions are unnecessary and can hurt performance or create security risks.
Lobby servers usually run in a grouped/proxy architecture.
Vanilla Minecraft capability.
Server-top BossBar is commonly used for announcement display.
For lobby servers, lighting should prioritize CPU savings when possible.
Even if lobbies do not heavily depend on terrain, a basic void/superflat world path is still needed.
External deployment should support official authentication per Minecraft operational requirements.
A new server project needs strong docs; otherwise onboarding is significantly harder than mainstream server ecosystems.
The Qexed official site focuses on documentation and project information. Content is written as local MDX in the repository and statically generated for doc.qexed.com.
