MyWorlds/MultiverseImporting - Revision history

RyanDo at 09:41, 12 October 2025

2025-10-12T09:41:45Z

← Older revision		Revision as of 09:41, 12 October 2025
Line 1:		Line 1:
	~~[[MyWorlds\|« Go back]]~~

	There used to be some mechanism for importing but aside from basic stuff, there isn't, really. You will have to set up the following things using myworlds again for existing multiverse worlds:		There used to be some mechanism for importing but aside from basic stuff, there isn't, really. You will have to set up the following things using myworlds again for existing multiverse worlds:

Bergerkiller at 22:47, 4 June 2023

2023-06-04T22:47:14Z

← Older revision		Revision as of 22:47, 4 June 2023
Line 1:		Line 1:
	[[MyWorlds\|« Go back]]		[[MyWorlds\|« Go back]]

	~~==How~~ to ~~import Multiverse's configuration into MyWorlds==~~		There used to be some mechanism for importing but aside from basic stuff, there isn't, really. You will have to set up the following things using myworlds again for existing multiverse worlds:
	~~A common question~~, ~~so as of 1.65~~ there ~~is automatic importing logic in MyWorlds. Whenever you load new worlds while Multiverse is running, and Multiverse has a configuration available~~, ~~MyWorlds will use that configuration by default~~. You ~~can disable this behaviour in~~ the ~~config.yml.~~

	~~To manually import these~~ worlds ~~(after they were already imported before by~~ MyWorlds ~~by loading them), follow these steps:~~		== Loading worlds ==
			Make sure to load the worlds again using MyWorlds. You can also opt to load both MyWorlds and Multiverse plugins at the same time. Then MyWorlds will pick up when Multiverse loads up new worlds and take over configuration options like the chunk generator plugin used.

	==~~Step 1: Install both MyWorlds 1.65+ and Multiverse==~~		== Stuff you probably have to change after ==
	~~That is all~~ you ~~need~~ to ~~do, no configuration changes are needed.~~		These things you will likely have to configure after:
			* Time. E.g. /mw time always 12:00 for always day
	~~==Step 2: Start the server~~==		* Weather. E.g. /mw weather always clear to disable rain
	~~And check up on the server log to see that all is well.~~

	~~==Step 3: Reset the configuration for worlds~~ you ~~wish~~ to ~~take over==~~
	~~Use the following command to reset specific world configurations~~:

	~~<code>/world config reset [worldname1] [worldname2] [etc~~.]</~~code>~~
	~~If you want to take over ALL worlds, use~~:

	~~<code>/world config reset</code>~~
	~~Please note that any settings you had set for worlds yourself will get lost, with the exception of a minor few~~.

	~~==Step 4: Restart the server==~~
	~~Between stopping and starting the server again, you could remove Multiverse or only remove the world configuration of Multiverse if you wish to keep using it~~. ~~This way there won't be any conflicts between Multiverse and MyWorlds when trying~~ to ~~load worlds.~~

RyanDo: 1 revision imported

2020-11-17T21:36:10Z

1 revision imported

← Older revision

Revision as of 21:36, 17 November 2020

Bergerhealer Wiki>RyanDo: Created page with "« Go back ==How to import Multiverse's configuration into MyWorlds== A common question, so as of 1.65 there is automatic importing logic in MyWorlds. Whenever y..."

2020-09-13T18:49:59Z

Created page with "« Go back ==How to import Multiverse's configuration into MyWorlds== A common question, so as of 1.65 there is automatic importing logic in MyWorlds. Whenever y..."

New page

[[MyWorlds|« Go back]]

==How to import Multiverse's configuration into MyWorlds==
A common question, so as of 1.65 there is automatic importing logic in MyWorlds. Whenever you load new worlds while Multiverse is running, and Multiverse has a configuration available, MyWorlds will use that configuration by default. You can disable this behaviour in the config.yml.

To manually import these worlds (after they were already imported before by MyWorlds by loading them), follow these steps:

==Step 1: Install both MyWorlds 1.65+ and Multiverse==
That is all you need to do, no configuration changes are needed.

==Step 2: Start the server==
And check up on the server log to see that all is well.

==Step 3: Reset the configuration for worlds you wish to take over==
Use the following command to reset specific world configurations:

<code>/world config reset [worldname1] [worldname2] [etc.]</code>
If you want to take over ALL worlds, use:

<code>/world config reset</code>
Please note that any settings you had set for worlds yourself will get lost, with the exception of a minor few.

==Step 4: Restart the server==
Between stopping and starting the server again, you could remove Multiverse or only remove the world configuration of Multiverse if you wish to keep using it. This way there won't be any conflicts between Multiverse and MyWorlds when trying to load worlds.