Database Setup
AutoPickup stores one thing per player: whether their auto-pickup toggle is on. It keeps that in a database so it survives restarts, and loads every saved toggle into memory on startup. Saves happen in the background the moment a player toggles. A player with no saved row is looked up once, then cached.
SQLite (default)
database:
type: "sqlite"
Nothing else to set. The file is mods/BusyBee_AutoPickup/database.db. This is the right choice
for a single server.
The bundled SQLite driver supports Linux x86_64, Windows x86_64 and macOS. On other platforms, use MySQL or MariaDB. See Requirements.
MySQL / MariaDB
database:
type: "mysql" # or "mariadb"
host: "localhost"
port: 3306
name: "autopickup"
user: "autopickup"
password: "change-me"
pool-size: 10
mysql and mariadb behave the same: both connect through the bundled MySQL driver with
useSSL=false. Create the database first; AutoPickup creates its table itself.
Use MySQL or MariaDB when several servers should share the same player toggles.
Pool settings
| Setting | Value |
|---|---|
| Maximum connections | pool-size (default 10) |
| Minimum idle connections | half of pool-size |
| Connection timeout | 5 seconds |
AutoPickup only reads and writes one small row per player, so the default pool is more than
enough. Lower pool-size on a busy shared database if you need to.
Table
AutoPickup creates autopickup_players if it doesn't exist:
| Column | Holds |
|---|---|
uuid |
The player's UUID (primary key) |
autopickup_enabled |
Their toggle |
last_known_name |
Currently also stores the UUID |
Players with no row use default-enabled from config.yml.
Changing database settings
Database settings are only read at startup. Restart the server after changing them;
/autopickup reload won't switch databases.
Switching from SQLite to MySQL doesn't copy existing toggles across. Players start from
default-enabled again on the new database.
Migrating from data.yml
Older versions saved toggles in data.yml. If that file is still in the data folder, it's
imported automatically. See Migration Guide.