LITW-Refined/modpack
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Modpack update process aktualisieren

Pascal
2024-08-16 15:58:02 +00:00
parent ae6f56e98a
commit 073b76664f
1 changed files with 15 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
Modpack-update-process.md

@@ -4,16 +4,13 @@ This page navigates you throw the update process of the LITW modpack.
## Collecting mods
The first step is collecting all the new mods, mod updates and what mods need to be removed. In parallel update the [modlist](https://cloud.pilzinsel64.de/s/Er3YsCENRmaNtwg). You should update all existing mods, add potential new mods and remove obsolete mods. In what order you do that steps is yours, but it's recommended to start with updating existing mods. Like this you may regonize any obsolete mods. After all, add the new mods.
The first step is collecting all the new mods, mod updates and what mods need to be removed. In parallel update the [modlist](https://cloud.pilzinsel64.de/s/Er3YsCENRmaNtwg). In what order you do that steps is yours, but it's recommended to start with updating existing mods. Like this you may regonize any obsolete mods. After all, add the potential new mods.
But before you start, you should create a fresh local client and server modpack installation. Use this as base for your changes.
> **Mod files naming strategy**
> Ensure you remove version numbers from mod names to make update process easier in the future.
### Mod updates
Go throw the modlist and collect all mods and check it's like for a new version. Ensure you take the latest official version, not a pre version, likely tagges with `-pre`.
Go throw the modlist and collect all mods and check it's like for a new version. Ensure you take the latest official version, not a pre version, likely tagges with `-pre`. In advanced, collect the new download link _(on GitHub: right-click -\> copy link; on CurseForge: copy the download link from the download entry within your browser)_.
...
@@ -51,4 +48,16 @@ Go throw the modlist and collect all mods and check it's like for a new version.
### Update production server
...
...
## FAQ
### File naming strategy
Ensure you remove version numbers from mod names to make update process easier in the future. The only exception is `CodeChickenLib` wich requies it's version number for technical reasons.
### How to get download links
On GitHub: right-click -\> copy link
On CurseForge: copy the download link from the download entry within your browser