Keep the essential engine working
Preserve the existing runtime approach, renderer/native components, libraries, version metadata and working compatibility code while building original VoidCraft screens and features around it.
Preservation principleOne place to work toward a more personal Minecraft Java experience on Android: launcher controls, instances, versions, optional features, customization and community tools.
This page describes the project and its roadmap. It does not claim every planned function is already implemented or tested.
Original VoidCraft interface concept · illustrative preview, not proof of completed features
VoidCraft is being developed around the existing launcher foundation instead of replacing its essential runtime internals without a technical reason.
Preserve the existing runtime approach, renderer/native components, libraries, version metadata and working compatibility code while building original VoidCraft screens and features around it.
Preservation principlePrioritize responsive layouts, readable controls, touch-friendly navigation and clear device compatibility information. Actual support depends on the device, Android environment and build.
Design directionSeparate working functions, prototypes and planned work. A preview or settings screen alone will not be treated as proof that a feature launches successfully in-game.
Project quality goalThe following describes target functionality. Availability must be verified in the actual launcher build before it is called complete.
Work toward choosing compatible Minecraft Java versions, checking required files, reporting downloads clearly, and surfacing launch errors with useful diagnostics.
In development / validation requiredTarget separate game profiles with version, loader and per-instance preferences, plus safe clone, import, export and organization options without overwriting a user's worlds.
Planned / verify per buildTarget supported loader and modpack workflows with version compatibility checks, clear install results and recovery paths. Support will vary by Minecraft version and device.
Planned / compatibility dependentTarget touch layouts that are easier to adapt to different screens, with a touch-control designer and practical in-game usability checks.
PlannedTarget world-safe management, backup and restore guidance, configurable memory and launch settings where supported, and safeguards against accidental data loss.
PlannedTarget compatibility-aware performance guidance, reversible settings and useful diagnostics. FPS and stability claims require repeatable testing on real supported devices; no universal FPS guarantee is made.
Planned / testing requiredVoidCraft's store concept is for optional, reviewable extensions. Essential launch, runtime, rendering and file-management components must remain part of the core where required.
Potential device snapshot, compatibility notes, reversible presets and explanations of trade-offs.
Concept previewPotential saved-server list, online/offline result, MOTD, icon, player count and edit/remove/refresh actions through a real status service.
Concept previewPotential profiles, friend requests and private messaging with account safeguards, reporting, blocking and moderation designed first.
Concept previewPotential backup verification, restore preview and safeguards before replacing or deleting world files.
Concept previewPotential custom colors, backgrounds, density and layout options so the launcher can feel personal without changing the game runtime.
Concept previewLong-term goal: individually managed optional features, each with a dedicated page, source/licence details, permissions, compatibility notes and review status.
Uploads and installation not connectedVoidCraft is building its own visual identity: a dark interface, violet/cyan accents, responsive cards and motion effects. The Cosmetic Store page contains theme ideas and original illustrations; purchases and cosmetic unlocks are not active.
Explore cosmetic concepts →Project pages outline server tracking, community support, safe feature submissions and documentation. Live server pings, community sign-up links and upload workflows must be connected before they can be used as real services.
Registration asks for a username, email and password together. The username is saved to the website profile; use the same username when signing in.
It provides registration, sign-in, a session and a basic profile. A visible website role such as Owner is part of this website account.
It is not Microsoft, Xbox or Minecraft authentication, does not prove game ownership, and does not currently sign into the Android launcher.
Passwords are stored as salted chained PBKDF2-HMAC-SHA-256 hashes, not plain text. Session cookies are Secure, HttpOnly and SameSite. Email verification and password reset still need implementation.
Follow releases and source changes, review the project documentation, and check each feature's status before relying on it.