Database
Storage location for important player information
You can use environment variables in the database fields, for example ${VALUE}
Setting
Pathconfig.yml → database
database:
use_playtime_tracking: true
type: "H2"
name: "flectonepulse"
host: "127.0.0.1"
port: "3306"
user: "root"
password: "1234"
parameters: "?autoReconnect=true&useSSL=false&useUnicode=true&characterEncoding=UTF-8"
prefix: ""
pool_settings:
max_size: 10
min_idle: 10
max_lifetime: 1800000
keepalive_time: 0
connection_timeout: 5000use_playtime_tracking
Whether to store the player's playtime in the database. If disabled, the /online and /toponline commands will not work, the newbie module will not be able to detect a newcomer, and join will not know that the player has already been on the server
type
The type of database used; currently supported types are:
| Type | Explanation |
|---|---|
SQLite | Local, stored as a file |
MySQL | Server-based, requires connection |
MariaDB | Server-based, requires connection |
H2 | Local, stored as a file |
PostgreSQL | Server-based, requires connection |
name
Database name
host
Address of the server where the database is located
port
Connection port for the database on the server
user
Username to be used for connecting to the database
password
Password for connecting to the database
parameters
Database connection parameters
prefix
If you change the prefix, the tables will be new and previous player data will not be used.
Prefix for database tables; if empty, the fp_ prefix will be used.
pool_settings
Database connection pool settings
max_size
Maximum number of connections in the pool
min_idle
Minimum number of idle connections that the pool tries to maintain
max_lifetime
Maximum lifetime of a single connection in milliseconds, after which it is closed and replaced with a new one
keepalive_time
Interval for checking idle connections in milliseconds. If 0, the check is disabled
connection_timeout
Maximum time to wait for a connection from the pool in milliseconds before an error is thrown