No results
42
Update Instructions
anonoe edited this page 2025-04-28 15:01:51 +02:00
Updating MMS-client from 1.2 to 3.0
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.
- 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 - 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.
- Close PrismLauncher to avoid problems.
- Now you are going to copy some files from your 1.2 instance into your 3.0 instance. Instead of copy, you can move as well (if it's a lot of data) or delete the 1.2 instance once you have verified, that your 3.0 installation works.
- copy
instance.cfg - At your 1.2 instance folder go into
.minecraft, at your 3.0 instance folder go intominecraft - copy everything except
modsandDistant_Horizons_server_data. You will be asked what to do with files of the same name: Merge folders and Skip files! - When all file operations have completed, open PrismLauncher.
- The new 3.0 instance should now appear with the same name and icon as your 1.2 instance. Change name & icon as you please, but be sure to get the right one, as they both appear exactly the same. The new MMS logo should be available in the icon picker.
- Launch your 3.0 instance. Join the server to see whether everything works alright. Now there are just a few things missing.
- 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. - There is now a official Testing server. Go to 'Multiplayer -> Add Server' and enter
nanody.de:25566in the Address field. If you are whitelisted on the main official server, you should be whitelisted there as well. - If you configured Distant Horizons or some of the performance mods, you will have to re-configure them. (see note below)
- If you edited the Vanilla Tweaks resourcepacks before, you will have to re-add your changes. (see note below)
- If you added mods, you will have to re-add them. (see note below)
- Please take note: Some data cannot be migrated. This makes steps 13/14/15 necessary. Still better than losing all data by installing a new, separate instance.
Not migrated data:- configurations/settings of Distant Horizons and some performance mods. See the
minecraft > configfolder 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. Mod configurations (settings) are all properly migrated.
- configurations/settings of Distant Horizons and some performance mods. See the
Alternative: Do not update, install 3.0 to a new, separate instance
- Pros: You can install it without hassle and start playing with 3.0 in no time.
- Cons: You might miss some things, like your configurations/settings, DistantHorizons LODs, logs, your Xaero world map
and if you added any of the following: mods, resourcepacks, singleplayer worlds, servers...
This is because no data is transferred from your 1.2 installation. You start with a fresh new 3.0 installation.
Just follow the standard installation instructions and a new, separate instance will be created.