At this time, *Heck* is only available as a [PolyMC] / [MultiMC] instance that is set up to auto-update using [packwiz].
This page describes how to install *Heck* as a [PolyMC] / [MultiMC] instance using [packwiz]. You may also get this modpack [on Modrinth](https://modrinth.com/modpack/heck/version/2.1.0) - their [installation instructions](https://docs.modrinth.com/docs/modpacks/playing_modpacks/) differ slightly. However, using instructions found on this page you can set your instance to **automatically update** when new versions of the modpack are out, or even be on the cutting edge of changes! Manually updating is also more straight-forward.
## Prerequisites
## Prerequisites
@ -22,21 +22,37 @@ If you want to download Java, I recommend [Temurin], an OpenJDK build by the Ecl
## Modpack Installation
## Modpack Installation
Go to the [releases page](../releases) and copy the URL of the latest `Heck_vX.X.X.zip` file. Finally, to get the *Heck* modpack added to your launcher, press "Add Instance", select "Import from zip", paste the URL you copied into the textbox and click "OK".
When launching, you will be asked which optional mods you want to use. I suggest to look up the mods online if you're unsure if you want to use them, or ask the community if anything is unclear. If you want to change your mind later, you can always do so when you start up the instance again.
When launching, you will be asked which optional mods you want to use. I suggest to look the mods up online if you're unsure if you want to use them, or ask the community if anything is unclear. If you want to change your mind later, you can always do so when you start up the instance again.
On first launch, [packwiz] will download all mods, configs and other associated files. And whenever you start the game, it will check for updates and apply them as well. That way you're always on the latest version of the modpack without having to worry about updating it manually.
On first launch, [packwiz] will download all mods, configs and other associated files. And whenever you start the game, it will check for updates and apply them as well. That way you're always on the latest version of the modpack without having to worry about updating it manually. Unless you chose a specific release version, which will only update when you change the version manually - see below.
## Updates
## Updates
When updating the modpack, not all changes might be applied, because some settings are stored per world, which won't be overridden by the update process. If you're just playing multiplayer, this won't matter to you. If you're playing singleplayer however, you might want to copy the contents of the `defaultconfigs` folder into your world's `serverconfig` folder after an update.
When updating the modpack, not all changes might be applied, because some settings are stored per world, which won't be overridden by the update process. If you're just playing multiplayer, this won't matter to you. If you're playing singleplayer however, you might want to copy the contents of the `defaultconfigs` folder into your world's `serverconfig` folder after an update.
If you want to manually update a [packwiz] based instance, you can go click "Edit Instance", select "Settings" and "Custom commands". You can simply edit the "Pre-launch command" to point to a different version (or auto-updating branch). For example, change it to:
- `.../heck/dev/pack.toml` to switch to the unstable development branch.
- `.../heck/main/pack.toml` to switch to the stable release branch.
- `.../heck/v2.1.0/pack.toml` to switch to the `v2.1.0` release version.
