Log in Discuss Your Project

ModernHDV Installation

This page explains the technical installation process for ModernHDV and what happens when the plugin starts for the first time.

Compatibility

Component Compatibility / Status
Paper 1.14 → 26.1.2
Spigot 1.14 → 26.1.2
Java 8+ recommended
Vault Required
Economy plugin Required

Note

Vault acts as an economy abstraction layer. This allows ModernHDV to integrate with different compatible economy plugins without depending on a single implementation.

Dependencies Explained

Vault

ModernHDV uses Vault to communicate with compatible economy plugins. This keeps compatibility broad and avoids direct coupling with one specific plugin.

Economy Plugin

ModernHDV does not manage money directly. Balances, debits, and credits are handled by your economy plugin through Vault. Without an active economy plugin, auction house transactions cannot work.

First Startup Process

  1. Creation of the plugin folder and base file structure.
  2. Generation of default YAML files (configuration, GUI, categories, language).
  3. Loading of the active language and configuration values.
  4. Detection of Vault and the available economy provider.
  5. Initialization of the storage backend (SQLite by default).

Tip

ModernHDV works immediately after installation thanks to an optimized default configuration (single-server mode + SQLite).

Context

The First Setup page covers the quick start. This page focuses on the technical details and installation modes.

Generated File Structure

plugins/
└── ModernHDV/
    ├── config.yml
    ├── items-gui.yml
    ├── items-categories.yml
    ├── lang/
    └── modernhdv.db

config.yml

Main plugin configuration (language, storage, system options).

items-gui.yml

Interface (GUI) configuration: items and custom-model-data. In YAML for the Free version, via Admin GUI for the Pro version.

items-categories.yml

Item assignment and auction house category configuration in YAML for the Free version, via Admin GUI for the Pro version.

lang/

Language files and user/console messages.

modernhdv.db

Local SQLite database created by default on first startup (single-server mode).

Storage Modes

SQLite

  • Local storage on the server
  • Recommended for a single server
  • No additional configuration required to get started

Recommended use: quick start, testing, single-server production.

MySQLPro required

  • Auction synchronization between servers
  • Shared auction house data across a network
  • Recommended for multi-server infrastructures

Recommended use: networks / proxies / linked servers.

Note

In multi-server mode, a shared / synchronized economy is required to guarantee transaction consistency. See the Multi-Server Mode section.

Multi-Server Mode Pro required

ModernHDV can run across multiple Minecraft servers by sharing the same auctions and player data through a common database. This mode is designed for network infrastructures that want to provide a consistent global auction house across multiple instances.

  • Multi-server networks
  • Hub + survival architecture
  • Shared economy
  • Global auction house accessible from multiple servers

How It Works

Servers use a shared MySQL database, which allows automatic synchronization of auctions between instances.

Players see the same auction house regardless of which server they access ModernHDV from.

Detailed technical configuration (structure, settings, network best practices) is documented on the dedicated Multi-Server page.

Warning

ModernHDV uses Vault as its economy interface and does not synchronize player balances by itself.

In a multi-server environment, an economy synchronization solution is required to guarantee transaction consistency between servers.

ModernHDV intentionally remains compatible with any Vault-compatible economy solution.

Examples of Possible Solutions

  • EssentialsX with MySQL synchronization
  • EcoBridge, MySQL Economy Bridge...
  • Custom network economy systems
  • Any Vault-compatible economy with shared data

Why This Step Matters

Without economy synchronization between servers:

  • balances may differ between servers;
  • purchases may become inconsistent;
  • economic losses may occur.

Tip

Complete configuration is available on the dedicated Multi-Server page.

Console Verification

✅ Correct startup

[ModernHDV] Vault hook detected
[ModernHDV] Storage backend: SQLite
[ModernHDV] ModernHDV is ready

❌ Dependency error example

[ModernHDV] Vault not found
Disabling plugin...

Installation Best Practices

  • Avoid /reload (prefer a full server restart)
  • Fully restart the server after adding dependencies
  • Check the logs on first startup
  • Create a backup before migrating SQLite → MySQL

IMPORTANT — Premium Features

Some advanced options described in the documentation (multi-server, MySQL storage, advanced in-game configuration) require ModernHDV Pro.

Next Steps

Configuration Commands Customization Multi-Server (Pro)

ModernHDV — Installation (technical documentation)