Create a MySQL Database for Your Game Server

Many plugins and mods want a MySQL or MariaDB database rather than flat files: permissions systems like LuckPerms, logging tools like CoreProtect, economy and stats plugins, and cross-server setups. The game panel can create one for you in a few clicks from the Databases tab, complete with credentials. Reach the panel as described in Access Your Game Server Panel.

Create a database#

1. Open the Databases tab on your server and click New Database.
2. Name it. Something short and descriptive: luckperms, stats. The panel prefixes the real database name with your server's identifier (you will see something like s12_luckperms), which keeps databases from different servers apart.
3. Set where connections may come from. The default % allows any host, which is what most plugins running on the same panel need. Restrict it to an IP or subnet if only a specific outside application will connect.
4. Create. The panel generates the database, a user, and a strong password.

Each plan allows a set number of databases. If the button is unavailable, delete one you no longer use or ask us about your limit.

Find the connection details#

Each database in the list shows the Endpoint (host and port), the Username, the Password (revealed on click), and a ready-made JDBC connection string for Java plugins. Copy the pieces into your plugin's config; a typical layout looks like:

storage-method: MySQL
data:
  address: db.example.net:3306
  database: s12_luckperms
  username: u12_aB3kL9mQ
  password: paste-from-the-panel

Restart the server after editing the config so the plugin reconnects.

Rotate the password#

If a password leaked or a former helper had it, use Rotate Password on the database. The old password stops working immediately and the new one is shown once, so update the plugin config first, rotate, paste the new value, and restart, in that order, to avoid downtime.

Delete a database#

Good habits#

• One database per plugin where sensible; it makes rotation and cleanup painless.
• Keep the connection host tight for anything reachable from the wider internet; % is convenient, a specific IP is safer.
• Include the database in your backup plan. Panel file backups do not include database contents; dump it on a schedule with the plugin's export or a mysqldump from a machine allowed to connect, and store the dump alongside your file backups.

Related#

• Startup Variables and Docker Images
• Console, File Manager, and SFTP