1. Start with an instance
An instance is a self-contained Minecraft setup. Give it a useful name such as “SMP 26.3”, “Quest VR”, or the name of a modpack. The selected instance should remember its Minecraft version, loader, loader version, installed mods and runtime state. Keeping those choices together is what prevents a change made for one world from unexpectedly breaking another.
2. Choose the Minecraft version first
The Minecraft version controls almost every compatibility decision that follows. Loaders, mods, Java requirements, native libraries and VR components are all version-sensitive. If you change the version on an existing instance, read the review screen before applying the change; a loader or mod that worked on the previous version may not have an equivalent release.
3. Choose a loader deliberately
Vanilla is for the base game. Fabric and Quilt focus on lightweight mod-loader ecosystems. Forge and NeoForge use their own libraries, metadata and processors. SPUDZWARE should show only genuine choices for the selected version. A loader card being visible does not mean it is compatible until the resolver has checked that version.
| Choice | Use it when | Watch for |
|---|---|---|
| Vanilla | You want the base game or a clean compatibility baseline. | No loader-specific mods. |
| Fabric | The pack/mods require Fabric or you prefer its ecosystem. | Exact Minecraft and Fabric Loader versions. |
| Quilt | The project specifically supports Quilt. | Do not assume every Fabric combination is automatically Quilt-compatible. |
| Forge | The modpack/mod explicitly targets Forge. | Forge version and processor output must match the Minecraft version. |
| NeoForge | The project explicitly targets NeoForge. | NeoForge is not just a renamed Forge selection. |
4. Review before applying
SPUDZWARE separates choosing from installing. The expected flow is Choose → Next → Review → Apply. The review should show the Minecraft version, loader and loader version, Java generation, VR/runtime choice where applicable and the effect on the existing instance. Applying changes updates the instance configuration; it should not silently begin a large download without the user seeing the plan.
5. Install as one job
Once the configuration is correct, Install prepares the runtime. The Downloads view groups the thousands of underlying files into a single operation for that instance. You should see overall progress and a current stage such as Downloading Minecraft, Installing loader, Installing Java or Verifying files. Technical file names, retries and source hosts remain available in Details for troubleshooting.
Use Resume when the launcher knows which managed components were completed. Starting over should clear only staged managed installation data, not worlds, screenshots, mods or user configuration.
6. Validation decides whether Play is safe
Play should not be enabled just because every download finished. Validation checks that required managed files are present and match expected hashes or runtime contracts. If validation fails, the correct state is Repair Required. Repair should replace only the damaged managed pieces and then validate again.
7. Add mods or import a modpack after the runtime is clear
Individual mods need the right Minecraft version and loader. Modrinth packs describe their own Minecraft and loader requirements and should normally become dedicated instances. A pack import should respect the pack manifest, verify downloads, apply overrides and understand nested Fabric dependencies instead of treating every embedded module as a duplicate top-level mod.
8. If something fails
Start with the stage that actually failed. A Microsoft sign-in error is not a loader error. A checksum failure is not a Java error. A public Local Hosting address failure does not necessarily mean the local Minecraft server crashed. SPUDZWARE keeps these systems separate so troubleshooting can stay specific.
- Use Retry for a transient network/download failure.
- Use Repair when managed files fail validation.
- Use View Details when support needs the exact component or sanitized system error.
- Keep personal worlds and configuration backed up before large version or modpack changes.