🚀 v1.3.2 - Multi-Server Support & Performance Update

Massive update bringing full multi-server support, database backends, Redis integration, and performance optimizations!

This release combines v1.3.0, v1.3.1, and v1.3.2 - skipped on Modrinth until multi-server support was complete.

🌐 Multi-Server Support (v1.3.0 - v1.3.2)

Database Backends (v1.3.0)

• MySQL/PostgreSQL support - Share economy data across multiple servers
• SQLite support - Better performance for single servers
• JSON (default) - Simple file-based storage for easy setup
• Automatic migration - Seamlessly upgrade from older versions

Transaction Safety (v1.3.1)

• Optimistic locking - Prevents race conditions when multiple servers modify balances
• Centralized logging - Transaction history stored in database for network-wide tracking
• Connection pooling - Configurable HikariCP settings for high-traffic networks
• Enhanced retry logic - Improved handling of concurrent transactions

Redis Pub/Sub (v1.3.2)

• Real-time synchronization - Balance updates propagate instantly across servers
• Cross-server notifications - Players receive transaction messages from other servers
• Optional integration - Works perfectly with or without Redis
• Debug logging - Configurable verbose logging for troubleshooting

⚡ Performance Improvements (v1.3.2)

• Caffeine caching - Lightning-fast balance lookups with minimal database queries
• Smart cache invalidation - Automatic updates on balance changes
• Tab completion caching - Instant offline player name autocompletion
• Reduced database load - Significant performance gains on busy servers

🛠️ New Features

Developer Tools (v1.3.2)

• /ecodebug verify - Test database connection and transaction safety
• /ecodebug cleanup - Remove test accounts

Transaction Logging (v1.3.1)

• Database-backed logs for network-wide visibility
• Pagination support for large result sets

📋 Configuration

New configuration options for multi-server setups:

Database Settings:

• Choose between JSON, SQLite, MySQL, or PostgreSQL
• Configurable connection pooling (poolSize, timeouts)

Redis Settings (Optional):

• Enable real-time cross-server sync
• Configurable host, port, password, and channel
• Debug logging option

🔄 Multi-Server Setup Guide

For Velocity/BungeeCord networks:

1. Use MySQL or PostgreSQL (shared database)
2. Install Redis and enable it in config (recommended for best experience)
3. Configure identical settings on all servers

With Redis enabled:

• ✅ Instant balance synchronization
• ✅ Cross-server transaction notifications
• ✅ Automatic cache invalidation

Without Redis:

• ✅ Transaction safety (optimistic locking)
• ✅ Accurate balances (database is source of truth)
• ⚠️ Slightly higher database load

🐛 Bug Fixes

• Fixed SQLite HikariCP configuration conflict
• Improved transaction return values for better error handling
• Enhanced sell command validation
• Fixed TestUser persistence in tab completion

📦 New Dependencies

• lettuce-core - Redis client
• reactor-core - Reactive streams support
• reactive-streams - Reactive streams API
• caffeine - High-performance caching
• HikariCP - Connection pooling (already included)

📖 Documentation

See the README for complete setup instructions and configuration examples.

---

Compatibility: Minecraft 1.21.10 (Fabric)
Server-Side Only: No client installation required

Upgrading from v1.2.0: Your existing JSON data will be automatically migrated. No manual intervention needed!