BedWars

A full-featured BedWars minigame plugin for Hytale. Defend your bed, raid enemy islands, and be the last team standing. Built from the ground up on the Hytale platform with multi-team arenas, map voting, a configurable shop, AI bots, persistent player stats, and rich integrations.

Features

Core Gameplay

• Classic BedWars rules — destroy enemy beds to prevent their respawn, eliminate the rest of their team, last team standing wins.
• Configurable team sizes — solos, duos, trios, squads, or any custom size up to your arena cap.
• Map voting — players vote on a shuffled subset of eligible maps before each match. Tie-breakers and time-outs fall back to a random pick.
• Manual or automatic team selection — players can pick a team during the team-select phase, with automatic balancing for anyone who hasn't chosen.
• Fast start — when an arena fills above a configurable threshold, the start countdown shortens automatically.
• Spectator mode — eliminated players become spectators; latecomers can also spectate ongoing matches when enabled.
• Per-team resource generators — bronze, iron, gold (or any custom drops) spawn at configurable positions and intervals.
• Per-arena lobby — each arena has its own waiting lobby with vote, team-select, and leave items.
• Block protection — only player-placed blocks can be broken; map terrain is preserved automatically.
• Friendly-fire protection — teammates cannot damage each other.
• Void death handling — falling out of the world counts as a normal death.
• Per-arena world instancing — each arena loads its own world template copy so multiple games can run in parallel without interference.

Shop System

• Hierarchical category shop — top-level tabs (blocks, weapons, armor, utilities, etc.) with per-category item lists.
• Multi-currency offers — define purchases that cost any combination of in-game items (e.g. 4 bronze + 1 iron).
• Quick-buy with Shift — Shift-click any offer to fill a full stack or as much as the player can afford.
• Custom display names and icons — every offer and category supports a custom label and icon item.
• Per-arena shop selection — point each arena at a named shop configuration.
• Cancellable purchase events — third-party plugins can intercept or modify purchases via ArenaShopPurchaseEvent.

AI Bots (Experimental)

The plugin includes an experimental bot system that can fill empty team slots or play alongside real players. Bots can gather resources, build, fight, and target beds, with selectable difficulty profiles (EASY, MEDIUM, HARD).

Bots are built on top of Hytale's core entity and NPC mechanisms, which are themselves in an early stage and still contain bugs. Any limitations or glitches in those underlying systems will surface in bot behavior as well. Both the bot system and its foundation will continue to improve in future updates.

Optional movement patch (Mixins). Hytale's NPC steering has a deadlock where a stationary bot can fail to bootstrap its own velocity and gets stuck in place. An optional companion mod — BedWars-Mixins — applies a runtime Sponge Mixin patch (loaded by the Hyxin mixin framework) that fixes it, so bots navigate far more reliably. It is not required — bots run without it — but installing it (alongside the Hyxin loader) noticeably improves bot movement.

Persistent Player Stats

• Stats tracked: kills, deaths, wins, losses, beds destroyed, blocks placed, blocks broken, hits, games played.
• Players can view their stats with /bw stats.
• Stats are exposed to other plugins via PlaceholderAPI.
• Optional MySQL storage with HikariCP connection pooling and async writes.

Economy & Rewards

• Optional stat-based reward payouts — earn currency for kills, wins, bed breaks, and more. Each reward value is independently configurable.
• Built-in support for Ecotale as an economy backend.
• Pluggable economy provider API for custom backends.

Internationalization

• Bundled languages: English (en-US) and Czech (cs-CZ).
• Messages use Hytale's native .lang asset system — add a new language by dropping in a translated file.

Requirements

• Hytale Server with the Kytale framework.

Required Dependencies

Optional Dependencies

Installation

1. Drop the BedWars plugin file into your server's mods directory.
2. Install the required dependencies listed above into the same mods directory.
3. (Optional) Install BedWarsConfigurator for the in-game setup UI.
4. (Optional) Install Ecotale if you want economy-based rewards.
5. Start the server. Default config.json, economy.json, game.json, and bot.json files are generated automatically on first run.

After first start, either drop in the ready-made demo setup (below) or configure your own arenas, maps, and shops (see Setup), then join with /bw join.

Try It Now — Demo Setup

Want a working game without configuring anything by hand? Download the demo setup — a complete, ready-to-run package that bundles everything: all required mods, a pre-configured arena, map, and shop, and the game worlds. No separate dependency installs, no JSON editing.

The pack ships two top-level directories that mirror your Hytale server layout:

mods/      All required mods (BedWars, Kytale, PlaceholderAPI, UiManager, …) plus the demo
           BedWars configs — arena, map, and shop — under mods/CreeperFace_BedWars/
worlds/    The demo game world(s)

1. Download the demo pack from the project's resources / downloads page.
2. Extract it into your Hytale server directory, merging the bundled mods/ and worlds/ folders into your server.
3. Start the server.
4. Join with /bw join and play.

Because the pack includes every required mod, you can skip the Installation and Setup steps below for a quick trial. It also doubles as a working reference when building your own arenas, maps, and shops.

Setup Workflow

The recommended workflow is to use the BedWarsConfigurator companion plugin, which provides an in-game UI for everything below. If you prefer to edit JSON by hand, all the same files are in the plugin data directory.

Plugin Data Layout

BedWars' data folder lives at mods/CreeperFace_BedWars/ (Hytale derives the folder name from the plugin's group and name in manifest.json):

mods/CreeperFace_BedWars/
├── config.json              Global plugin settings
├── economy.json             Economy provider and reward values
├── game.json                Chat formats and game mechanics
├── bot.json                 Bot system settings
├── arenas/
│   └── <ArenaName>.json     Arena definitions
├── maps/
│   └── <MapName>/
│       ├── config.json      Map (teams, beds, spawns, generators)
│       ├── preview.png      Map preview shown in voting UI
│       └── world/           World template copied per game
└── shops/
    └── <ShopName>.json      Shop window/category/offer definitions

Building Your First Arena

1. Build (or import) a map world and place it under maps/<MapName>/world/.
2. Add an optional preview.png (shown in the voting UI).
3. Create maps/<MapName>/config.json defining each team's spawn, bed location, shop NPC position, and resource generators.
4. Create arenas/<ArenaName>.json with the lobby position, player counts, time limits, and a map_filter controlling which maps are eligible.
5. Optionally create a shops/<ShopName>.json and reference it from the arena.
6. Restart the server (or use the configurator's reload action).

Setup with the Configurator

The BedWarsConfigurator plugin provides a visual setup tool that handles all the JSON file editing for you — arena creation, map registration with team placement, shop building, and live preview. Highly recommended for production setups.

Configuration Reference

config.json — Global Settings

{
  "general": {
    "auto_join": false
  },
  "data": {
    "enable": false,
    "data_provider": "none",
    "store_configs": false,
    "mysql": {
      "host": "127.0.0.1",
      "port": 3306,
      "user": "root",
      "password": "mysql",
      "database": "default"
    }
  }
}

economy.json — Economy & Rewards

{
  "economy_provider": "none",
  "rewards": {
    "enabled": false,
    "values": {
      "kills": 10.0,
      "deaths": 0.0,
      "wins": 100.0,
      "losses": 0.0,
      "beds": 50.0,
      "place": 0.0,
      "break": 0.0,
      "hits": 0.0,
      "games": 5.0
    }
  }
}

Arena Configuration (arenas/<Name>.json)

Map Configuration (maps/<Name>/config.json)

Shop Configuration (shops/<Name>.json)

A shop is a list of windows (category tabs). Each window contains children — the individual offers. Every offer has a purchase_item (what the player receives) and a cost array (any combination of items required).

{
  "windows": [
    {
      "type": "menu",
      "name": "Blocks",
      "icon": {
        "item_id": "Cloth_Roof_Green_Flap"
      },
      "children": [
        {
          "type": "offer",
          "name": "Green Wool",
          "purchase_item": {
            "item_id": "Cloth_Roof_Green_Flap",
            "item_count": 16
          },
          "cost": [
            {
              "item_id": "Bronze_Coin",
              "item_count": 4,
              "item_name": "Bronze"
            }
          ]
        }
      ]
    }
  ]
}

Bot Configuration (bot.json)

Game Mechanics & Chat (game.json)

game.json is split into a general section and a chat section:

{
  "general": {
    "allow_spectators": true
  },
  "chat": {
    "enable_all_chat": true,
    "all_prefix": "!",
    "lobby_format": "...",
    "team_format": "...",
    "all_format": "...",
    "spectator_format": "..."
  }
}

The *_format strings use PlaceholderAPI placeholders (see the table below) — e.g. %player_display_name%, %message%, %team_color%.

Commands

All commands live under the /bw root.

Placeholders

The plugin ships with full PlaceholderAPI support. All BedWars placeholders are prefixed with bw_.

Arena Placeholders (global, parameterized by arena name)

Used as %bw_arena_<property><ArenaName>%:

Team Placeholders (scoped to a team context)

Arena Placeholders (scoped to an arena context)

Color Placeholders

Color is applied via PlaceholderAPI's built-in helpers — there's no extra registration step:

• %color<name,shade>% — Tailwind palette, e.g. %color<zinc,400>%, %color<cyan,500>%. Default shade is 500.
• %color_rgb<r,g,b>% — explicit RGB, e.g. %color_rgb<255,255,255>%.
• %color_hex<rrggbb>% — explicit hex, e.g. %color_hex<ff5555>%.
• %team_color% — the active team's color, resolves to an empty string when no team is in scope.

Plugin API

BedWars exposes a public BedWarsAPI interface other plugins can use:

• Look up arenas, get a player's current arena, join a random arena.
• Register custom data providers (storage backends) via registerDataProvider.
• Register custom economy providers via registerEconomyProvider.
• Listen to arena lifecycle events:
  • ArenaPlayerJoinEvent, ArenaPlayerLeaveEvent
  • ArenaStartEvent, ArenaStopEvent, ArenaStateChangeEvent
  • ArenaPlayerEliminateEvent, ArenaPlayerRespawnEvent, ArenaTeamEliminateEvent
  • ArenaKillEvent, ArenaBedDestroyEvent (cancellable)
  • ArenaShopPurchaseEvent, ArenaResourceDropEvent (both cancellable)
• Extend arena/map/shop configurations with custom sections via the ConfigExtensionRegistry.

Add the BedWars API module as a compile-time dependency to use it. Full API documentation — usage, events, and customization examples — lives in the public API repository: Creeperface01/BedWars-API (vendored here as the api/ git submodule).

Game Flow

Waiting  →  Voting  →  Team Select  →  Game  →  (reset to Waiting)

1. Waiting — players are in the arena lobby. When startPlayers is reached, the arena advances.
2. Voting — players vote on a shuffled subset of eligible maps. The winning map (or a random fallback) is loaded.
3. Team Select — players pick teams via the UI. Anyone who doesn't pick gets auto-balanced when the countdown ends.
4. Game — match runs until only one team is left alive, time runs out, or an admin stops the game. Players who die with their bed intact respawn; players who die with their bed destroyed become permanent spectators.
5. Reset — the world copy is cleared, players return to the lobby, and the arena waits for the next match.

Languages

Bundled translations:

• English (en-US)
• Czech (cs-CZ)

To add a language, drop a translated .lang file under the appropriate Server/Languages/<locale>/ asset path.

Credits

• Author: CreeperFace

Support

Report issues and feature requests on the BedWars-API issue tracker. Contributions and translations are welcome.