ChromaHunt documentation

Paint the disguise.
Play the hunt.

Everything you need to install, configure and run a player-made camouflage hide-and-seek minigame on your Minecraft server.

Bukkit · Spigot · PaperMinecraft 1.20—26.2No hard dependencies
A painted ChromaHunt hider camouflaged against a tree
Core loopPaint · Hide · HuntEvery disguise starts with the player.
01

Creative camouflage

Players paint their own pixel avatar instead of choosing from a preset disguise list.

02

Two game modes

Classic rewards survival. Infection grows the seeker team as hiders are found.

03

Server-ready flow

Arena tools, live HUD, local statistics and an included resource pack ship together.

01

Product overview

A complete camouflage minigame

ChromaHunt gives both roles an active job: hiders create and manage a disguise, while seekers read color, shape and movement under time pressure.

P

Player-made identities

Paint with a brush, eyedropper and connected fill, then choose a pose that fits the arena.

H

Readable match pressure

Timers, role HUD, exposure feedback and final reveals keep the match easy to follow.

S

Self-contained tools

Create arenas, configure rules and deliver the bundled pack without another required plugin.

Version scope

The same JAR is compiled against Bukkit-compatible APIs for 1.20.1, 26.1.2 and 26.2, and was live-start tested on matching Paper builds.

02

Getting started

Install in five steps

A default installation hosts its own resource pack. External hosting is optional and useful for networks or servers behind NAT.

1

Stop the server

Always install or replace the JAR while the server is fully stopped.

2

Install the plugin

Place ChromaHunt.jar inside the server's plugins directory.

3

Generate files

Start once. ChromaHunt creates plugins/ChromaHunt/ with configuration, messages and data folders.

4

Make the pack reachable

Allow players to reach TCP port 8128, or configure a direct public HTTP(S) URL.

5

Create an arena

Set bounds and role spawns, check the arena with /chroma admin info, then enable it.

Server softwareBukkit · Spigot · Paper
Minecraft Java1.20.x through 26.2
Plugin bytecodeJava 17
DependenciesNone required

Run the Java runtime required by the Minecraft server build you choose. Newer server versions may require a newer runtime even though the plugin bytecode targets Java 17.

03

Administrator guide

Build your first arena

Select one cuboid and provide four functional points. The arena can only be enabled when every required value is present.

  1. 01

    Create

    Use a short lowercase ID that will remain stable in commands and files.

  2. 02

    Select

    Stand at opposite arena corners and record pos1 and pos2.

  3. 03

    Place spawns

    Set lobby, hider, seeker and spectator.

  4. 04

    Validate

    Run info, fix any missing value, then enable the arena.

Quick setup
/chroma admin create forest
/chroma admin pos1
/chroma admin pos2
/chroma admin bounds forest
/chroma admin set forest lobby
/chroma admin set forest hider
/chroma admin set forest seeker
/chroma admin set forest spectator
/chroma admin info forest
/chroma admin enable forest
A configured forest arena surrounded by ChromaHunt border markers
Custom arena frameVisible only to participants and occluded by terrain.
04

Player guide

One hunt, two ways to play

Both modes share the paint, hide, seek and reveal loop. The difference is what happens when a hider is found.

Classic

Survive the clock

Seekers have configured ammunition. Hiders win by staying undiscovered until seeking time expires.

  • Limited seeker ammo
  • Exposure and missed-spot pressure
  • Survivors revealed at the end
Infection

Turn the whole arena

Found hiders become seekers. The searching team grows until everyone is discovered or time runs out.

  • Infinite seeker ammo by default
  • Escalating team pressure
  • Last-hider tension
A hider camouflaged in a forest
A seeker scanning a forest with the Chroma Blaster

Chroma Blaster

Seekers commit area-effect shots against suspicious locations instead of clicking every block.

Exposure

Missed-spot scoring records how convincingly a hider occupied the seeker's view.

Freecam

Hiders can watch the search inside a configured radius and return to their body.

Wall climbing

Enable the climbing tool, face a solid wall and hold Shift. Release to drop; reaching a ledge mantles over it.

05

Original paint workflow

Create the disguise in front of you

The preview is placed directly in front of the player. Walk around it, rotate it or recenter it whenever another side is easier to reach.

A ChromaHunt player painting a brown and red avatar in front of them

Brush

Paint the pixel under your crosshair with the selected color.

Eyedropper

Sample a color. Sneak while sampling to use the exact block texture.

Connected fill

Replace a connected region without repainting each pixel.

Pose

Right-click for the next pose; sneak-right-click for the previous one.

Rotate / recenter

Rotate by 45° or sneak-right-click to place the preview in front again.

Save & exit

Store the current design and leave the paint session safely.

The ChromaHunt color palette inventory
Eight palette pages

Broad color choice, familiar inventory controls.

Practice mode lets players learn the painter before joining a match.

06

Reference

Commands

The main command is /chromahunt. /chroma, /chunt and /ch are included as aliases.

Player commands
CommandWhat it does
/chromaOpen the ChromaHunt game browser.
/chroma join [arena]Join a named arena or use quick join.
/chroma leaveLeave safely and restore the inventory you had before joining.
/chroma practiceOpen the painter outside a live match.
/chroma stats [player]View your own or another player's local statistics.
/chroma resourcepackRequest the configured resource pack again.
/chroma helpShow the command list in game.
Administrator commands
CommandWhat it does
/chroma admin create <id>Create a new arena configuration.
/chroma admin delete <id>Delete an arena configuration.
/chroma admin pos1Set selection corner one to your current location.
/chroma admin pos2Set selection corner two to your current location.
/chroma admin bounds <id>Apply the selected cuboid to an arena.
/chroma admin set <id> <point>Set lobby, hider, seeker or spectator spawn.
/chroma admin enable <id>Enable a complete arena.
/chroma admin disable <id>Stop automatic use of an arena.
/chroma admin start <id>Force-start an eligible arena.
/chroma admin stop <id>Stop the current match and reset its players.
/chroma admin listList configured arenas and their status.
/chroma admin info <id>Show configuration and missing requirements.
/chroma admin reloadReload configuration and messages.
07

Access control

Permissions

Player permissions are enabled by default. Administrative and bypass permissions should stay restricted.

Permission nodes
NodePurposeDefault
chromahunt.usePlayer commands and the main menuEveryone
chromahunt.playJoin and play configured arenasEveryone
chromahunt.statsView player statisticsEveryone
chromahunt.adminArena setup and match administrationOperators
chromahunt.bypass.resourcepackBypass enforced resource-pack acceptanceNobody
chromahunt.bungee.bypassBypass dedicated-server join and leave locksOperators
08

Visual delivery

Resource pack

The pack supplies custom tools, menu icons, HUD elements and pixel-avatar visuals. The JAR contains the same pack supplied as a separate ZIP.

01

Embedded host

Enabled by default on port 8128. Set public-url when the automatic address cannot be reached by players.

02

External host

Upload ChromaHunt-ResourcePack.zip to a direct public HTTP(S) URL and place it under resource-pack.url.

03

Request again

Both the Resource Pack icon in the Chroma GUI and /chroma resourcepack send a fresh cache-busted request.

Public means public

The client downloads the pack itself. A private LAN address, authenticated file page or non-direct sharing link will not work for remote players.

09

Operator reference

Configuration map

Defaults are usable immediately. Tune one system at a time, reload, and verify the change in a test arena before using it in production.

resource-pack

Pack delivery

Automatic sending, enforcement, URL, retries and embedded host.

bungeecord-mode

Network behavior

Automatic arena join, leave locking and fallback handling.

mode-rules

Mode ammunition

Classic and Infection seeker ammo values.

defaults

Match rules

Players, timers, movement, painter, weapon, taunts and results.

hud

Runtime display

Update interval, progress and player-head appearance.

custom-border

Arena frame

Materials, spacing, dimensions, view range and close-range culling.

waiting-role-chances

Lobby board

Live fair-selection probabilities before the round starts.

storage

Local data

Statistics file, skin folder and save intervals.

Reliable border
custom-border:
  enabled: true
  disable-culling: true
  marker-spacing: 4.0
  view-range: 96.0
Wall climbing
defaults:
  movement:
    wall-climbing: true
    climb-speed: 0.22
    climb-facing-dot: 0.35
10

Proxy networks

Dedicated-server mode

Use this mode when a backend exists only for ChromaHunt matches. Regular players are automatically placed into an available arena.

01ProxyPlayer connects to the ChromaHunt backend.
02BackendThe plugin finds an available enabled arena.
03MatchJoin and leave rules stay controlled by the server.

Enable it deliberately

Set bungeecord-mode.enabled: true only on dedicated backends. A general survival or lobby server should keep it disabled.

Choose the no-arena action

KICK denies entry. CONNECT asks a BungeeCord-compatible proxy to return the player to the configured fallback server.

Keep a bypass

Operators receive chromahunt.bungee.bypass through the admin permission, which is useful for setup and testing.

Host the pack publicly

For multiple backends, an external direct URL is normally more predictable than exposing a separate embedded port for each one.

11

Help center

Troubleshooting

Start with the exact symptom below. Most setup problems come from an incomplete arena or a resource-pack URL the Minecraft client cannot reach.

The resource pack is accepted but custom items still look vanilla.

Run /chroma resourcepack or click the Resource Pack icon, wait for the successful-load message, then reopen the menu. Confirm the ZIP is a direct download and that the player did not disable server packs in the multiplayer entry.

The embedded resource pack does not download.

Expose TCP port 8128 to players and set resource-pack.embedded-host.public-url when the server's detected address is private, proxied or behind NAT. Alternatively use an external public URL.

An arena cannot be enabled.

Run /chroma admin info <id>. It lists missing bounds or spawn points. The world, cuboid, lobby, hider, seeker and spectator points must all be valid.

Border columns disappear when a player gets close.

Keep custom-border.disable-culling: true. Version 1.0.3 applies the close-range display fix by default; reload or restart after changing this value.

Wall climbing does not activate.

Confirm defaults.movement.wall-climbing is enabled, activate the climbing item, face a solid wall at close range and hold Shift. Adjust attach distance or facing tolerance only after testing the default behavior.

Players on a proxy are not joining automatically.

Verify dedicated-server mode is enabled on the backend, at least one arena is enabled and playable, and the proxy forwards BungeeCord-compatible plugin messages.

ChromaHunt final reveal showing a seeker victory

Expected finish

Clear result, clean reset.

When diagnosing a match, check the server console around the phase where the flow stopped and include that section when requesting support.

12

Ownership & privacy

Local data. Clear license.

ChromaHunt is proprietary commercial software, delivered without telemetry, advertising, remote activation or a hidden update checker.

No telemetry

The plugin does not report player, server or usage information to the seller.

No DRM

There is no license server, IP whitelist or hardware-bound activation.

Local storage

Arenas, statistics and painted skins remain in plugins/ChromaHunt/.

Commercial EULA

One purchase licenses one server network.

Customers may configure the plugin and supplied resource pack for that network. Redistribution, resale, public sharing and claiming authorship are not allowed. The complete legal terms are in LICENSE.txt.

PluginResource packREADMELicense