Neue Seite
Migration from v1-legacy to v2
GWorld v2 features intelligent migration systems that make the transition from older versions or the change between storage media (files to database) as easy as possible.
Are you looking for a way to switch from YAML to MySQL? Then please follow this link: Switch from YAML (File) to MySQL (DB)
Migration from GWorld v1 to v2
When you upgrade from the first version of GWorld to v2, the plugin will automatically detect this during the first start.
How it works
- Detection: The plugin looks for an existing
worlds.ymlwhere...- the
ConfigVersionfield is missing - the
LoadWorldslist exists - the
Worldslist exists
- the
- Automatic Backup: Before changes are made to the datasets, GWorld renames the old file to
worlds_legacy_backup.yml. - Data Conversion: The
LegacyMigratorreads all old world definitions and transfers them into the new, structured v2 format. Missing new fields are filled with default values. - Seed Repair: Since seeds were not saved in v1, GWorld v2 automatically detects missing seeds when the world is first loaded, reads the correct seed from the world files, and corrects the entry.
Note: During the migration, the console will inform you about the progress. Once the worlds.yml file contains a ConfigVersion: 1, the process is complete. This will also be output in the console.
After a successful migration, GWorld v2 starts normally and all worlds are loaded.
Security Measures & Prerequisites
To ensure a smooth migration, please note the following points:
Prerequisites (see Introduction)
- Java Version: GWorld v2 strictly requires at least Java 21, as modern language features are used.
Checklist
- Create a manual backup of your entire plugin folder before upgrading.
- After the migration, check with the command
/gworldswhether all worlds are listed correctly. - Check the server console for error messages during the first start.
Example worlds.yml Configurations
This documentation refers to GWorld version 2.0.0.