Microsoft sign-in
Authentication has multiple stages: Microsoft OAuth, Xbox Live, XSTS, Minecraft Services, entitlement verification, profile retrieval and secure session storage. A failure at Microsoft OAuth is different from a Minecraft Services AppID rejection, and both are different from a secure credential-store failure after sign-in.
On Android or Quest, check basic connectivity, automatic date/time and whether VPN/Private DNS software is interfering before changing account configuration. On Windows, a secure-session save failure points to the operating-system credential backend, not necessarily to Minecraft ownership.
Downloads
The normal Downloads screen groups each install or modpack into one job. If a job stalls, open Details and look for the current stage, host, retry count or checksum result. A completed byte count does not always mean installation is complete; Java, loader processors or final validation can still remain.
Install and repair
Install progresses through required components in dependency order. Final validation should not run before a required runtime component is available. If validation finds missing or corrupt managed files, use Repair. Repair should not delete worlds, screenshots, mods, resource packs, options or unrelated configuration.
Loader problems
If a loader does not apply after selection, verify that the instance draft changed, a compatible loader version resolved and the Review → Apply step completed. If the loader is unavailable for that Minecraft version, choose a genuine supported combination instead of forcing an artifact from another version.
Modpack import errors
For Modrinth packs, giant lists of Fabric API module “duplicates” can indicate that nested JAR dependencies were scanned as top-level mods. A real duplicate is two conflicting top-level files. The importer should rely on the pack manifest, understand nested dependencies, avoid adding a dependency the pack already provides and show concise user-facing conflicts.
Local Hosting
Check the Minecraft server state and the public SPUDZWARE address separately. If the server is running locally but the public address fails, retry the connection rather than restarting a healthy server. If sign-in is required for the relay, authenticate first. Port conflicts and server startup failures should be handled as local process issues.
Quest VR
Quest problems can happen at APK installation, secure sign-in, Android Java startup, Minecraft startup, renderer initialization, OpenXR initialization, controller input or gameplay. A statically valid APK is not proof that all later stages work. Record the last successful stage before changing the runtime.
What to include in a support report
- Platform and launcher version.
- Instance name, Minecraft version and loader.
- The exact stage shown as failed.
- The short sanitized error message.
- Whether Retry or Repair changed the result.
- Relevant logs with tokens, passwords and private keys removed.
Support never needs your Microsoft password, refresh token, Xbox/XSTS token, Minecraft bearer token, API keys or private signing material.