Skip to content

Commit

Permalink
docs: v3 instead of v2 in MPDB migrator page
Browse files Browse the repository at this point in the history
  • Loading branch information
WiIIiam278 authored Dec 2, 2023
1 parent 5d1bd7c commit 693209f
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions docs/MPDB-Migration.md
Original file line number Diff line number Diff line change
@@ -1,18 +1,18 @@
This guide will walk you through how to migrate from MySQLPlayerDataBridge (MPDB) to HuskSync v2.x.
This guide will walk you through how to migrate from MySQLPlayerDataBridge (MPDB) to HuskSync v3.x.

> **Warning:** Please note that due to MPDB changes, HuskSync only supports migrating from MySQLPlayerDataBridge `<= v4.9.2`. Support for newer versions will be added in the future.
## Requirements
- Spigot servers with MySQLPlayerDataBridge *still installed*

## Migration Instructions
### 1. Install HuskSync v2.x on all Spigot servers
### 1. Install HuskSync v3.x on all Spigot servers
- Download, then install HuskSync on all your servers. Don't uninstall MySQLPlayerDataBridge yet.
- Follow the setup instructions [here](Setup).
- Follow the setup instructions [here](setup).
- Start your servers again when done.

### 2. Configure the migrator
- With your servers back on and correctly configured to run HuskSync v2.x, ensure nobody is online.
- With your servers back on and correctly configured to run HuskSync v3.x, ensure nobody is online.
- Use the console on one of your Spigot servers to enter: `husksync migrate mpdb`. If the MPDB migrator is not available, ensure MySQLPlayerDataBridge is still installed.
- Adjust the migration setting as needed using the following command: `husksync migrate mpdb set <setting> <value>`.
- Note that migration will be carried out *from* the database you specify with the settings in console *to* the database configured in `config.yml`.
Expand All @@ -27,4 +27,4 @@ This guide will walk you through how to migrate from MySQLPlayerDataBridge (MPDB

### 5. Ensure the migration was successful
- Verify that the migration was successful by logging in and using the `/userdata list <username>` command to see if the data was imported with the `mpdb_migration` saveCause.
- You can delete the old tables in the database if you want. Be careful to make sure you delete the correct ones.
- You can delete the old tables in the database if you want. Be careful to make sure you delete the correct ones.

0 comments on commit 693209f

Please sign in to comment.