Modpack update process
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. 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 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. 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).
...
Remove obsolete mods
...
Add new mods
...
Testing locally
...
Consolidating of new configurations
...
Testing on test server
...
Update modpack
...
Update modpack info
...
Update modpack packages
...
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