Database Setup

XDiscordUltimate persists linked accounts, tickets, stats, and moderation records in a relational database via HikariCP connection pooling. SQLite needs zero configuration - it is the default and works out of the box. Use MySQL or PostgreSQL for networks, multiple servers sharing one dataset, or higher write throughput.

Choose a Backend

Tab Title
Tab Title
Tab Title

SQLite is the default and stores everything in a single file. No server to run, no credentials to manage.

database:
  type: sqlite
  sqlite:
    file: data.db

The database file is created at plugins/XDiscordUltimate/data.db.

SQLite is ideal for single-server setups up to a few hundred players. Back up data.db by copying the file while the server is stopped.

For multi-server networks or higher concurrency, point XDiscordUltimate at a MySQL (or MariaDB) server:

database:
  type: mysql
  mysql:
    host: localhost
    port: 3306
    database: xdiscord
    username: xdiscord
    password: "your_password"
    ssl: false

host - the database host (use localhost for same-machine)
port - MySQL default is 3306
database - the schema name; create it beforehand (CREATE DATABASE xdiscord;)
username / password - the database user; needs SELECT, INSERT, UPDATE, DELETE, CREATE, ALTER, INDEX, DROP on the schema
ssl - set true to require TLS

PostgreSQL is recommended for larger networks with heavy write loads:

database:
  type: postgresql
  postgresql:
    host: localhost
    port: 5432
    database: xdiscord
    username: xdiscord
    password: "your_password"

host - the database host
port - PostgreSQL default is 5432
database - the database name; create it beforehand (createdb xdiscord)
username / password - the role credentials

Connection Pooling

All backends run through HikariCP. Default pool settings:

Setting	Value	Notes
`maxPoolSize`	10	Sufficient for most servers; raise for large networks
Leak detection	Enabled	Warns in logs if a connection is held too long

The schema is created automatically on first run. A schema_versions table tracks migrations, so future plugin upgrades apply any pending schema changes on startup.

Database Setup

Database Setup

Choose a Backend

Connection Pooling

Next Steps

First Run

Database API

​Database Setup

​Choose a Backend

​Connection Pooling

​Next Steps

First Run

Database API

Database Setup

Choose a Backend

Connection Pooling

Next Steps