October 13, 2026 — launcher workflow cleanup
The launcher workflow was reorganized around persistent instances. Version and loader changes now follow a choose, review and apply flow instead of behaving like disconnected buttons. Installation progress is being grouped into one user-facing job, while technical file-level details remain available for troubleshooting. Local Hosting is also being simplified so the Minecraft server state and the public SPUDZWARE address are presented as separate health layers.
Windows, Android and Quest continue to share the core instance/runtime model while keeping platform-specific controls and secure-storage behavior. Physical device testing remains a separate acceptance step.
October 13, 2026 — live updater integration
A SPUDZWARE-controlled update design is being integrated so Windows, Android and Quest can check for a release at startup. Releases are independent by platform and can use stable, beta or development channels. Update metadata and packages are intended to be verified before installation. Android and Quest continue to use the operating system's installation approval rather than silently bypassing platform security.
October 12, 2026 — Quest runtime matrix
Quest runtime work expanded across the current target Minecraft versions and loader families. The project now distinguishes runtime generation, host installation/repair validation, Android ARM64 process startup, Minecraft startup, OpenXR initialization, VR menu access and physical VR gameplay as separate milestones. That prevents a metadata pass from being reported as hardware-verified VR.
The current target set is 26.3, 26.2, 26.1.2, 1.21.11, 1.21.10, 1.21.9, 1.21.8, 1.21.1, 1.20.1 and 1.19.2. Compatibility is evaluated per loader and version instead of using one blanket status.
October 2026 — public documentation expansion
The public knowledge base now covers the launcher, Quest VR architecture, Local Hosting, version/loader compatibility, Modrinth pack imports and launcher troubleshooting in addition to the existing server setup, performance, backups, security and maintenance guides. This is intended to make the public site useful even before a visitor signs in or creates a server.
Development notes describe the state of the project, not a guarantee that every experimental combination works on every device. SPUDZWARE will continue to label unverified runtime stages honestly and publish user-facing fixes as they are validated.