anonoe/MMS
SHA256
1
0
Fork 0
Code Issues Pull requests Projects Releases 3 Packages 4 Wiki Activity Actions

Update Update Instructions

anonoe 2025-04-28 14:45:03 +02:00
parent 42d4eb8a32
commit d3235707b0
1 changed files with 10 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

17
Update-Instructions.md

@ -1,6 +1,6 @@
## Updating MMS-client from 1.2 to 3.0 ## Updating MMS-client from 1.2 to 3.0
af
Updating MMS-client from 1.2.x to 3.0 requires migrating your data from your 1.2 instance into a 3.0 instance. Updating MMS-client from 1.2.x to 3.0 requires migrating your data from your 1.2 instance into a 3.0 instance. Follow the instructions in strict fashion, otherwise you will end up with a misconfigured MMS-client instance! Only deviate if you know _exactly_ what you're doing.
1. In PrismLauncher click 'Add Instance -> Import', paste the following link and hit 'OK' `https://git.nanody.de/api/packages/anonoe/generic/MMS-client/3.0/MMS-client_3.0-up.zip` 1. In PrismLauncher click 'Add Instance -> Import', paste the following link and hit 'OK' `https://git.nanody.de/api/packages/anonoe/generic/MMS-client/3.0/MMS-client_3.0-up.zip`
2. Open the folders for both your 1.2 instance and your new 3.0 instance: Select each instance and then click 'Folder' on the right side. 2. Open the folders for both your 1.2 instance and your new 3.0 instance: Select each instance and then click 'Folder' on the right side.
@ -15,12 +15,15 @@ Updating MMS-client from 1.2.x to 3.0 requires migrating your data from your 1.2
11. Go to the 'Options... -> Controls... -> Key Binds...' and hit 'Show Conflicts' in the bottom right corner. 11. Go to the 'Options... -> Controls... -> Key Binds...' and hit 'Show Conflicts' in the bottom right corner.
Most conflicts are no problem. Fix the 'X' conflict by setting 'Load Hotbar Activator' to 'Not Bound': Click on the Button and hit the Escape key on your keyboard. Most conflicts are no problem. Fix the 'X' conflict by setting 'Load Hotbar Activator' to 'Not Bound': Click on the Button and hit the Escape key on your keyboard.
12. There is now a official Testing server. Go to 'Multiplayer -> Add Server' and enter `nanody.de:25566` in the Address field. If you are whitelisted on the main official server, you should be whitelisted there as well. 12. There is now a official Testing server. Go to 'Multiplayer -> Add Server' and enter `nanody.de:25566` in the Address field. If you are whitelisted on the main official server, you should be whitelisted there as well.
13. If you configured Distant Horizons or some of the performance mods, you will have to re-configure them. 13. If you configured Distant Horizons or some of the performance mods, you will have to re-configure them. (see note below)
14. If you edited the Vanilla Tweaks resourcepacks before, you will have to re-add your changes. 14. If you edited the Vanilla Tweaks resourcepacks before, you will have to re-add your changes. (see note below)
15. If you added mods, you will have to re-add them. 15. If you added mods, you will have to re-add them. (see note below)
- Please take note: You might miss some configurations/settings and if you added any: mods or resourcepacks if you edited 'fancy', '3D' or 'utility' via VTDownloader - Please take note: Not all your data will be migrated. Due to the nature of the update process. Not migrated data:
But still better than losing all data by installing a new, separate instance - configurations/settings of Distant Horizons and some performance mods. See the `minecraft/config` folder inside the new 3.0 instance before step 7.
- resourcepacks if you edited 'fancy', '3D' or 'utility' via VTDownloader. Resourcepacks which are separate from these three packs are properly migrated.
- Every Mod you added by yourself.
Still better than losing all data by installing a new, separate instance
### Alternative: Do not update, install 3.0 to a new, separate instance ### Alternative: Do not update, install 3.0 to a new, separate instance