Database
Setting up database backends for plot data storage.
Database Backends
minePlots supports four database backends. Choose one based on your deployment needs.
YAML / Flat File (Default)
Local file-based storage that requires no external setup.
database:
database-type: FLAT
Best for: single-server setups, testing, and small communities.
H2
An embedded SQL database stored in a single file. Better performance than YAML for larger datasets.
database:
database-type: H2
Best for: single-server setups with moderate plot counts.
MySQL
A full relational database for production deployments.
database:
database-type: MYSQL
hostname: "localhost"
base: "mineplots"
port: 3306
username: "root"
password: "securepass"
| Option | Type | Description |
|---|---|---|
hostname | String | MySQL server address |
base | String | Database name (must exist) |
port | Integer | MySQL server port |
username | String | Database user |
password | String | Database password |
Best for: large communities, production environments.
MongoDB
A document-based database for distributed deployments.
database:
database-type: MONGODB
mongo-db-connection-string: "mongodb://localhost:27017"
| Option | Type | Description |
|---|---|---|
mongo-db-connection-string | String | Full MongoDB connection URI |
Best for: distributed systems, existing MongoDB infrastructure.
Stored Data
The database stores the following information for each plot:
| Data | Description |
|---|---|
| Plot metadata | ID, name, owner, creation date, visibility |
| Location data | Center coordinates, region boundaries, world |
| Members | Member UUIDs, permissions, join dates |
| Flags | All flag states |
| Warps | Warp names and locations |
| Bans | Banned player UUIDs |
| Expiration | Expiration timestamp |
| Biome | Current plot biome |
| Ranking | Block-based ranking points |
| Ratings | Player ratings (1-5 stars) |