Getting Started

Welcome to Warden Party. This plugin lets you run configurable Warden boss encounters with custom health logic, scheduled spawns, reward commands, Phantom support, and PlaceholderAPI integration.

Prerequisites

Before installing Warden Party, make sure your server meets these requirements:

Java Version: Java 21 for Minecraft 1.21.11. Java 25 is required for Minecraft 26.x.
Server Software: Paper or a Paper-compatible fork is required.
Minecraft Version: 1.21.11 - 26.3. Paper 26.3 is recommended and was checked with Warden Party 1.8.9.
PlaceholderAPI Optional : Required only if you plan to use the built-in placeholders.
Permissions Plugin Optional : A plugin such as LuckPerms helps manage admin access cleanly.
MythicMobs Optional : MythicMobs 5.x for spawning a custom mob base. Use a release compatible with your server version.
ModelEngine Optional : ModelEngine 4.x for custom models, with its generated resource pack installed on clients.

Installation

Setting up Warden Party is straightforward. Follow these steps to get started:

Download the latest Warden Party build from Hub, SpigotMC or BuiltByBit.
Place the warden-party-x.x.x.jar file into your server’s plugins/ directory.
Restart the server to generate the default configuration files.
Join the server and run /wp to verify that the plugin loaded correctly.

First-Run Configuration

On first startup, the plugin generates a dedicated folder containing two main files:

config.yml: Boss definitions, schedulers, natural spawn rules, reward commands, and combat settings.
messages.yml: Command feedback, permission warnings, cooldown messages, and placeholder fallback text.

When upgrading from 1.8.8, replace the plugin JAR while the server is stopped and keep your configuration files. Bosses without an appearance section retain the normal Warden behavior. To use the new integrations, merge an example from the MythicMobs or ModelEngine guide into an existing profile; do not replace the entire profile with a partial snippet.

First Test Flow

For a clean first test, use this order:

Leave the default Warden definition in place.
Join a non-peaceful world.
Run /wp summon to spawn the default Warden at your location.
Hit the boss a few times to confirm cooldowns, sounds, and health tracking behave as expected.
If Phantom mode is enabled, continue until the configured threshold is reached and verify the fight phase changes correctly.

Next Steps

Gameplay Overview: Understand how boss fights, vulnerability, and damage tracking work.
Admin Commands: Review the full command and permission surface.
config.yml: Start customizing boss variants, spawn logic, and reward commands.
Schedulers: Automate recurring Warden events.
MythicMobs: Spawn a custom mob with optional model skills.
ModelEngine: Apply an imported model directly to a Warden.