Homes!

🗄️ Multiple Storage Backends

New: YAML / SQLite / MySQL storage

Select your storage backend in config.yml under storage.type:

Backend	Description
yaml	Default. Per-player .yml files in playerdata/. Zero setup required.
sqlite	Single embedded database file (homes.db). No external dependencies. Recommended for mid-size servers.
mysql	External MySQL or MariaDB server with full HikariCP connection pooling. For large networks.

All three backends are bundled inside the JAR so no extra JARs to install.

Auto-migration (storage.auto-migrate: true)

Switch backends without losing data. On the next server start, Homes automatically reads all existing YAML player files and imports them into the new backend, then marks the source files as migrated.

SQLite specifics

• Uses WAL journal mode for better concurrent read performance
• Pool size locked to 1 (SQLite supports only one writer at a time)
• No external server or credentials required

MySQL/MariaDB specifics

• Full HikariCP connection pool (configurable size, timeouts, idle settings)
• ON DUPLICATE KEY UPDATE for safe upserts
• Configurable table prefix (safe to share a database with other plugins)
• Tables created automatically on first start

New config section

storage:
  type: yaml           # yaml | sqlite | mysql
  auto-migrate: true
  sqlite:
    file: homes.db
  mysql:
    host: localhost
    port: 3306
    database: homes
    username: root
    password: ""
    table-prefix: homes_
    pool:
      maximum-pool-size: 10
      minimum-idle: 2
      connection-timeout: 30000
      idle-timeout: 600000
      max-lifetime: 1800000

---

🌍 Broad Server Compatibility (1.13 → Latest)

Spigot, Paper, and Bukkit support

• Compiled against Spigot API 1.13.2 — runs on Spigot, Paper, and any fork

Java requirement

• Minimum: Java 17

---