Skip to content

Commit d215959

Browse files
its-miromaits-miroma
committed
rewrite(how-to/update): initial commit
1 parent 1f90db3 commit d215959

File tree

7 files changed

+165
-0
lines changed

7 files changed

+165
-0
lines changed

‎how-to/README.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
---
2+
hidden: true
3+
icon: arrow-progress
4+
---
5+
6+
# How to...

‎how-to/update/README.md‎

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
---
2+
hidden: true
3+
icon: arrows-rotate
4+
---
5+
6+
# Update
7+
8+
<table data-view="cards"><thead><tr><th align="center"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><strong>Modrinth App</strong></td><td><a href="modrinth-app.md">modrinth-app.md</a></td></tr><tr><td align="center"><strong>CurseForge App</strong></td><td><a href="curseforge-app.md">curseforge-app.md</a></td></tr><tr><td align="center"><strong>Prism Launcher</strong></td><td><a href="prism-launcher.md">prism-launcher.md</a></td></tr><tr><td align="center"><strong>Minecraft Launcher</strong></td><td><a href="vanilla.md">vanilla.md</a></td></tr><tr><td align="center"><strong>MultiMC</strong></td><td><a href="multimc.md">multimc.md</a></td></tr></tbody></table>
9+
10+
{% hint style="danger" %}
11+
**You should ALWAYS** [**make backups**](../backup/) **before updating**.
12+
13+
As with any other piece of software, updates may go wrong for many reasons, including but not limited to: the launcher, the hardware, your custom configuration, the mods you added... and, rarely, FO as well.
14+
{% endhint %}
15+
16+
{% hint style="warning" %}
17+
**FO only supports updates to stable versions**.
18+
19+
We do NOT support updating from a stable to an unstable version, nor do we support downgrading. In those cases, consider creating a separate installation/instance.
20+
21+
Of course, if you've [added custom mods to FO](../add-mods/), you are responsible for updating those, but you should not update [mods bundled in FO](../../info/mods/) manually.
22+
{% endhint %}
23+
24+
{% hint style="info" %}
25+
If you want the recommended FO configuration after an update, you may [reset your custom settings](../../info/options/reset/).
26+
{% endhint %}
27+
28+
{% hint style="info" %}
29+
If a server you're playing on is out-of-date, you may want to [add](../add-mods/) the [ViaFabricPlus mod](https://modrinth.com/mod/viafabricplus).
30+
{% endhint %}

‎how-to/update/curseforge-app.md‎

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
---
2+
hidden: true
3+
---
4+
5+
# How to Update: CurseForge App
6+
7+
{% hint style="danger" %}
8+
**You should ALWAYS [make backups](../backup/curseforge-app.md) before updating**.
9+
10+
As with any other piece of software, updates may go wrong for many reasons, including but not limited to: the launcher, the hardware, your custom configuration, the mods you added... and, rarely, FO as well.
11+
{% endhint %}
12+
13+
1. Open the **CurseForge App**
14+
2. Select **Minecraft** from the grid or from the sidebar
15+
3. In **My Modpacks**, right-click on **Fabulously Optimized**
16+
4. Click on the **Change Version** button
17+
5. If you cannot find the **Change Version** button, it means you've added custom mods:
18+
1. Click on the three dots button
19+
2. Click on **Profile Options**
20+
3. Uncheck the **Allow content management for this profile** checkbox
21+
4. Click on **Continue**
22+
6. If you do not want the latest version, select the version you want from the dropdown
23+
7. Click on **Continue**. FO should now get updated
24+
8. If you've followed _step 5_, remember to check the **Allow content management for this profile** checkbox again
25+
9. Once updated, launch the instance. Minecraft should open up
26+
10. If you can see the newly installed version in the bottom-right corner, you're done!

‎how-to/update/modrinth-app.md‎

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
---
2+
hidden: true
3+
---
4+
5+
# How to Update: Modrinth App
6+
7+
{% hint style="danger" %}
8+
**You should ALWAYS [make backups](../backup/modrinth-app.md) before updating**.
9+
10+
As with any other piece of software, updates may go wrong for many reasons, including but not limited to: the launcher, the hardware, your custom configuration, the mods you added... and, rarely, FO as well.
11+
{% endhint %}
12+
13+
1. Open the **Modrinth App**
14+
2. Click on the **Library** section
15+
3. Select the existing FO instance
16+
4. Click on the **Update modpack** button on the top-right
17+
5. If you do not want the latest version, select the version you want from the dropdown
18+
6. Click on the **two-arrows** button. FO should get updated
19+
7. Once updated, launch the instance. Minecraft should open up
20+
8. If you can see the newly installed version in the bottom-right corner, you're done!
21+
22+
<!-- TODO: clear cache? -->

‎how-to/update/multimc.md‎

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
hidden: true
3+
---
4+
5+
# How to Update: MultiMC
6+
7+
{% hint style="danger" %}
8+
**You should ALWAYS [make backups](../backup/multimc.md) before updating**.
9+
10+
As with any other piece of software, updates may go wrong for many reasons, including but not limited to: the launcher, the hardware, your custom configuration, the mods you added... and, rarely, FO as well.
11+
{% endhint %}
12+
13+
{% hint style="success" %}
14+
If you had installed [FO on MultiMC **with** automatic updates](../install/multimc.md#automatic-updates), and you're not updating to a newer version of Minecraft, you just need to open the existing versions.
15+
16+
If you get a popup saying **This modpack uses new versions of the following...**, click on the **Update** button.
17+
{% endhint %}
18+
19+
If you had installed [FO on MultiMC **without** automatic updates](../install/multimc.md#easier-installation), or if you're updating to a new version of Minecraft:
20+
21+
1. Follow the [FO installation instructions for MultiMC](../install/multimc.md) again. This will create a new instance
22+
2. In **MultiMC**, click on the previous version
23+
3. Click on **Minecraft Folder**
24+
4. Click on the new version as well
25+
5. Click on **Minecraft Folder**
26+
6. Copy the following files from the folder you opened in _step 3_ to the folder you opened in _step 5_:
27+
* `saves`: Your local worlds
28+
* `resourcepacks`: Your resource packs, if any. If you're asked to replace files, do not!
29+
* `shaders`: Your shaders, if any
30+
* `screenshots`: Your screenshots, if any
31+
* `server.dat`: Your multiplayer servers, if any
32+
* `options.txt`: Your custom options and keybinds, if any. If you want the [recommended FO settings](../info/options.md), do not copy it
33+
7. Once you've moved them, launch the new instance. Minecraft should open up
34+
8. If you can see the newly installed version in the bottom-right corner, you can delete the previous version from _step 2_

‎how-to/update/prism-launcher.md‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
---
2+
hidden: true
3+
---
4+
5+
# How to Update: Prism Launcher
6+
7+
{% hint style="danger" %}
8+
**You should ALWAYS [make backups](../backup/prism-launcher.md) before updating**.
9+
10+
As with any other piece of software, updates may go wrong for many reasons, including but not limited to: the launcher, the hardware, your custom configuration, the mods you added... and, rarely, FO as well.
11+
{% endhint %}
12+
13+
1. Open the **Prism Launcher**
14+
2. Select the existing FO instance
15+
3. Click on **Edit** in the sidebar
16+
4. Select **Modrinth** in the tab list
17+
5. If you do not want the latest version, select the version you want from the dropdown
18+
6. Click on the **Update pack** button. A prompt should pop up
19+
7. Click on **Yes**. FO should get updated <!-- TODO: Are you sure? -->
20+
8. Once updated, launch the instance. Minecraft should open up
21+
9. If you can see the newly installed version in the bottom-right corner, you're done!

‎how-to/update/vanilla.md‎

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
---
2+
hidden: true
3+
---
4+
5+
# How to Update: Minecraft Launcher
6+
7+
{% hint style="danger" %}
8+
**You should ALWAYS [make backups](../backup/vanilla.md) before updating**.
9+
10+
As with any other piece of software, updates may go wrong for many reasons, including but not limited to: the launcher, the hardware, your custom configuration, the mods you added... and, rarely, FO as well.
11+
{% endhint %}
12+
13+
{% tabs %}
14+
{% tab title="Installer" %}
15+
16+
Follow the [installation instructions](../install/vanilla.md) again.
17+
18+
You may find a `paigaldaja_meta.json` file in the same folder as the installer. Don't worry: this is just a configuration file for smoother future updates.
19+
{% endtab %}
20+
21+
{% tab title="Manual" %}
22+
If you've installed FO manually, you must reinstall it for every update.
23+
24+
Follow the [installation instructions](../install/vanilla.md) again. You may skip _step 1_ because Java is already installed.
25+
{% endtab %}
26+
{% endtabs %}

0 commit comments

Comments
 (0)