Minecraft Multi-Server Auction House Setup (ModernHDV Pro)

Introduction

Multi-server mode allows several servers in your network to share the same auctions and the same auction house data. The goal is to provide players with a consistent experience regardless of which server they open the menu from.

This page explains the overall behavior, network prerequisites, and key points to watch. The detailed option setup remains documented on the Configuration page.

How It Works

Shared MySQL Database

All ModernHDV servers in the network use one shared MySQL database. This database centralizes auction data and allows every instance to work from the same data source.

Auction Synchronization

Auctions created, viewed, and processed on one server become visible on the other servers connected to the same storage. Players therefore see one global auction house across the network.

Payment Routing

ModernHDV handles delayed sale and purchase payouts through its secure payout system to preserve auction transaction consistency across the entire network.

Simplified Architecture

Players
   │
   ├── Hub (ModernHDV Pro)
   ├── Survival-1 (ModernHDV Pro)
   └── Survival-2 (ModernHDV Pro)
          │
          └── Shared MySQL database (auctions / auction house data)

Economy: must be shared or synchronized separately (through Vault + your network solution)

Prerequisites

ModernHDV Pro on every relevant server
MySQL database accessible from the network servers
storage.type=MYSQL configuration
multiserver.enabled=true
Unique multiserver.server-name on each server
Vault installed on each server
Shared or synchronized economy solution between servers

Warning

ModernHDV does not synchronize economy balances by itself. On a network, you must use a shared or synchronized economy solution between servers to guarantee transaction consistency.

Minimum Configuration

Minimum configuration example to enable multi-server mode (full option details remain documented on the Configuration page).

multiserver:
  enabled: true
  server-name: "survival-1"

storage:
  type: "MYSQL"

Server Identifier

Each server must use a different server-name value (e.g. hub, survival-1, survival-2).

Delayed Payouts

ModernHDV includes a secure payout system to handle sale-related payments reliably in environments where players are not always connected to the same server.

The goal is to make auction house transaction handling more reliable across the network while keeping compatibility with your economy through Vault.

Common Issues

Auction house not shared between servers: verify that all servers use the same MySQL database and that multiserver.enabled=true.
Inconsistent data between servers: check the server-name values (they must be unique).
Inconsistent transactions: verify your network economy solution (shared/synchronized balances).
Database connection failed: validate the MySQL settings and network access between the servers and the database.

Network Best Practices

Clearly name each server through multiserver.server-name (e.g. roles / instances).
Use a dedicated MySQL database for ModernHDV to simplify maintenance and diagnostics.
Test the buy/sell flow on a staging environment before network deployment.
Monitor the logs during the first startup of each server in the cluster.
Validate network economy consistency before opening it to players.

Next Steps

Configuration FAQ Upgrade to Pro