Skip to content

Latest commit

 

History

History
119 lines (86 loc) · 7.84 KB

multimc-auto-update.md

File metadata and controls

119 lines (86 loc) · 7.84 KB
Raw

MultiMC auto-update

Here's a quick FAQ about the auto-updating MultiMC pack.

What is it?

It is a normal MultiMC modpack that simply launches packwiz, a mod handling tool on every start. That means it will add and update any mods according to what I specify in the pack.toml file.

How to install it?

The same way you would install any other MultiMC modpack - download the zip and drag to MultiMC window.

How does it update?

It asks the server if the modpack has any updates every time you launch it. This means you do need internet or you'll get an error (though you can skip the error).

If there are any, they will be downloaded and launched, otherwise the current game will launch.

It does not auto-update the individual mods outside of what is set in the the modpack. This is a common misconception and it could cause problems anyway.

Why are you not distributing it in CurseForge?

  • To keep it visible in files list, I'd have to reupload it every time I update the pack, which is often unnecessary.
  • It may not actually support the mod developers via downloads so I'd prefer if only a limited amount of technical users use it.
  • It is still somewhat experimental and may have unexpected issues or variances from the normal packs I distribute (CurseForge and MultiMC)

So why did you make this at all?

  • Because MultiMC doesn't have this yet, see their issues #2640 and #3037
  • Because the developer is planning to make an installer using the same system for the vanilla launcher as well, which I definitely want for FO
  • Because it was suggested for this pack previously, where an user wanted to upgrade without needing to have a separate profile

What happens if a new version of Minecraft is released?

You'll have to download a new version of the pack that is specific to that Minecraft version.

Can I ignore some of the mods?

There is no official procedure for this yet, but RaptaG and Ultrasonic1209 have made tutorials and scripts for an improved version of the Remty5's workaround. The user now only has to replace the instance parameters and list the mods that will be disabled.

If you have any problems, you can ask for support in our Discord server.

Windows

Tutorial and scripts by Ultrasonic1209.

  1. Download the mod disabling scripts:
    1. Open MultiMC, right click your instance and click "Instance Folder"
    2. Inside the folder, shift-right click and select Open in Terminal (or equivalent PowerShell prompt)
    3. Within the terminal, run the following commands to download the files.
(Invoke-WebRequest -Uri "https://raw.githubusercontent.com/Fabulously-Optimized/fabulously-optimized/main/Packwiz/pre-launch.ps1" -OutFile "pre-launch.ps1")
(Invoke-WebRequest -Uri "https://raw.githubusercontent.com/Fabulously-Optimized/fabulously-optimized/main/Packwiz/post-exit.ps1" -OutFile "post-exit.ps1")

If you wish to install them somewhere else, run cd path\to\folder (where path\to\folder is the path to your folder's location) before running the command above.

  1. Select the mods to disable.

    1. Copy the name of the mod(s) you want to disable.
    2. Open pre-launch.ps1 with any text editor
    3. On line 4, double click mod1 and paste the name of the mod you previously copied. You can do this on line 5 too! If you want to disable more mods, copy all of line 5, press the Enter key at the end of line 5 and hit paste. (Make sure to change the name to match the new mod, though!)
      • Mod names may change with modpack updates so you'll need to update them here again.

  2. Setup the scripts to run on your MultiMC (auto-update) instance

    1. Open MultiMC
    2. Click on your instance "Edit Instance"
    3. Go to "Settings" and then to "Custom Commands"
    4. Remove the pre-launch command and replace it with powershell -ExecutionPolicy Bypass -File ..\pre-launch.ps1
      • If you've installed it elsewhere, use path\to\folder\pre-launch.ps1 (where path\to\folder is the path to the folder)
    5. Do the same thing for the post-exit command but with powershell -ExecutionPolicy Bypass -File ..\post-exit.ps1 this time.
      • Or path\to\folder\post-exit.ps1 (where path\to\folder is the path to the folder)

  3. That's it! Now, the mods you disabled will not run with the instance nor appear inside Mod Menu!

Linux, macOS

Tutorial and scripts by RaptaG. Not fully tested on macOS.

  1. Open a terminal and run the command below:
    • Debian-Ubuntu Linux: sudo apt-get install jq
    • Fedora Linux: sudo dnf install jq
    • openSUSE Linux: sudo zypper install jq
    • Arch Linux: sudo pacman -S jq --needed
    • Other distros/macOS: follow this tutorial

This will install a program called jq, needed for automatically adapting this script to any Minecraft version you use.

  1. Download the mod disabling scripts:
    1. Open MultiMC, right click your instance and click "Instance Folder"
    2. Inside the folder right click and select "Open Terminal here"
    3. Within the terminal, run the following command - this will install the files and make them executable:
curl -Os https://raw.githubusercontent.com/Fabulously-Optimized/fabulously-optimized/main/Packwiz/pre-launch.sh | curl -Os https://raw.githubusercontent.com/Fabulously-Optimized/fabulously-optimized/main/Packwiz/post-exit.sh && chmod +x pre-launch.sh post-exit.sh

If you want to install them somewhere else, run cd /path/to/folder (where /path/to/folder is the path to your folder's location) before running the command above.

  1. Select the mods to disable

    1. Copy the name of the mod(s) you want to disable
    2. Open pre-launch.sh with any text editor
    3. Find the line saying "Select the mods you wish to disable:" and below it mod0=, mod1=, mod2=,mod3=, mod4= and mod5=. After = place the name of the mods you previously copied, one by one.
      • No matter how many mods you disable, never remove mod0= and $mod0.jar.
      • Mod names may change with modpack updates so you'll need to update them here again.

  2. Setup the scripts to run on your MultiMC (auto-update) instance

    1. Open MultiMC
    2. Click on your instance "Edit Instance"
    3. Go to "Settings" and then to "Custom Commands"
    4. Remove the pre-launch command and replace it with ../pre-launch.sh
      • If you've installed it elsewhere, use /path/to/folder/pre-launch.sh (where /path/to/folder is the path to the folder)
    5. Do the same thing for the post-exit command but with ../post-exit.sh this time.
      • Or path/to/folder/post-exit.sh (where /path/to/folder is the path to the folder)

  3. That's it! Now, the mods you disabled will not run with the instance nor appear inside Mod Menu!

FAQ:

What if I want to disable more or less than 6 mods?

  • Removing: Just remove the extra rows from the start and end of pre-launch.sh, eg. from lines 10 & 11 mod4=, mod5= and $mod4.jar\, $mod5.jar\ from lines 35 & 36, if you want to have 4 mods disabled.
  • Adding: Press Enter in the end of line 11 and type mod6= for example. Then, in the end of line 36, press again Enter and type $mod6.jar\. Repeat the same for more mods by just changing the number (mod6= to mod7= and $mod6.jar\ to $mod7.jar\ etc.).