Best Practices
Recommended settings and habits for running SigmaOrders, by server size.
Sizing Guide
| Setting | Small (<50 players) | Medium (50-200) | Large (200+) |
|---|---|---|---|
max-orders-per-player | 5 | 10 | 15 |
max-items-per-order | 32 | 54 | 64 |
order-life | 10080 (7 days) | 10080 (7 days) | 1440 (1 day) if high activity |
| Database | SQLite | SQLite | MySQL |
cache-size | 100 (default) | 200-300 | 500+ |
Adjust order-life to economy activity rather than just server size: 1440 (1 day) for active economies, 10080 (7 days) normal, 43200 (30 days) for slow economies. Set min-price-per-item/max-price-per-item to fit your economy - tighter for economy-focused servers, wider for permissive ones.
Database
SQLite suits single-server, low-volume setups; MySQL suits large or multi-server setups needing external tooling. Back up database.db regularly for SQLite; use standard backup tools and monitor connection pool usage for MySQL. See Database Configuration.
Permissions
Follow least privilege: new players get sigmaorders.use + sigmaorders.fulfill, trusted/regular players get full sigmaorders.*, admins get all permissions plus sigmaorders.admin. See Permissions Overview and LuckPerms Examples for ready-to-use commands.
Economy
Keep the default ESCROW payment method - it holds funds until delivery is confirmed and guarantees payment for deliverers. Set refund.deduction-percentage to 0.0 for player-friendly servers or a small fee (e.g. 0.05) to discourage order spam on economy-focused servers.
Security
Enable the item blacklist (blacklist.enabled: true) for griefing/exploit items like BEDROCK, BARRIER, COMMAND_BLOCK. Enable transaction logging (transaction-logging.enabled: true, format: DETAILED) for an audit trail. Full detail in Security Guide.
Player Experience
Write clear, actionable messages in messages.yml - explain what happened, what to do next, and keep formatting consistent. Configure error messages to explain the failure reason and suggest a fix.
Maintenance
Back up the database file, config files, and transaction logs on a regular schedule. Before updating: test on a dev server, back up, read the changelog for breaking changes, and update during low-traffic periods.
Monitor order creation rate, delivery completion rate, average order value, and player participation to catch problems early.