Changelog

Every release of HCFCore, newest first. Versions follow Semantic Versioning, and each is on the releases page with its jar.

A release gathers several changes: they collect under Unreleased as they reach main, and are published together. HCFCore is in pre-release (0.x) until 1.0.0: a minor version may still change a setting's name or meaning — the notes say so, and what to do, since your configuration files are never rewritten.

Unreleased

Added

• The Theme Builder rewords any message: every text of lang/en.yml — about 1,300 — searchable by key or word, filtered by part of the plugin, rendered as it is typed, written into theme.yml's messages. It also sets the /leaderboard window's items (ui.yml, leaderboard-menu) and each kind of event's colour in /schedule, and previews both windows.
• theme.yml carries the /schedule colours (schedule-colors, by kind or event id), in place of events.yml's weekly-schedule.menu.colors — one theme file holds the whole look.

Changed

• A kit or [Refill] sign's first line is a message (kit.sign.header, &1[%word%] as shipped), where its dark blue was fixed: a theme recolours it. Its text must stay [%word%] for the sign to be recognised.

0.10.0 - 2026-09-29

A combat logger leaves a villager behind, a raid pays the raiders, and DTR stays negative for as long as a team is raidable — no more freeze. Mountains and capture zones are claimed land; Kill the King is held in the warzone by a wall, and a King who logs out is banned. [Refill] signs, /kit fromchest, /leaderboard in a window, /alleffect, /db and /ct, clickable invitations, your own Lunar nametag, more for Discord. And the classic 1.7.10 combat is gone: it will come back as a plugin of its own after 1.0.

Tried in game on Paper 26.2 with two players, the combat logger first. Several settings changed or went away: the notes under each change say what to do — your configuration files are never rewritten, and a missing key takes its default.

Added

• /alleffect (/alleffects, /effects): Speed II, Fire Resistance, Invisibility, Haste II and Night Vision in one command, typed again to take them off. Any effect command may now give several effects at once (effects: in effect-commands.yml). Existing servers: copy the alleffect entry from the jar's effect-commands.yml, and the effect-commands.given-several line of lang/en.yml.
• /deathban (/db): how long dying now would ban you — /pvp, and now /ct (/combattag), stay your combat tag. For staff, /db <player> checks someone, and /db lift, /db ban work as under /pvp; Tab offers the deathbanned. Copy the pvp.deathban.own lines of lang/en.yml from the jar.
• /schedule colours each kind of event — KOTH gold, Citadel purple, Kill the King red… — in the window and the chat alike (weekly-schedule.menu.colors, by kind or by event id).
• A refill sign asks before it wipes your inventory: with clear-before-giving, a player holding anything clicks the sign a second time within 5 seconds (refill-signs.confirm-seconds, 0 never asks). Add confirm-seconds under refill-signs in kits.yml to change it.
• Pause or continue while contested (events.yml, when-contested, for a KOTH, a Citadel and each Conquest zone): pause, as before, freezes the countdown; continue lets the holder keep counting down while it is still in the zone.
• A raid pays: what a team loses at becoming raidable goes to the team whose kill made it so (teams.yml, points.raidable-steal) — never to an ally, to nobody when no team caused the death. TeamRaidableEvent#getRaider() names that team.
• Making subclaims is a permission like the others (claims.yml, subclaims.create-role, every member as shipped), which each team may raise in /team settings (create-subclaims).
• A won event leaves a sign, as a kill does: the event, who won it and the date, to the King's winner or every online member of the winning team (events.yml, capture-signs; lines in events.capture-sign). Existing servers: copy the capture-signs section and the events.capture-sign lines from the jar.
• EventWonEvent in the API: fired when any event is won, with its kind, the winning team and, for Kill the King, the player.
• /leaderboard opens a window with every board: kills, deaths, K/D, killstreak, playtime, and two new ones — the teams' kills and points — each item listing its top 10 (ui.yml, leaderboard-menu). /leaderboard <board> still lists one in the chat. Existing servers: copy the leaderboard-menu section of ui.yml and the stats.top lines of lang/en.yml from the jar.
• Discord hears more (discord.yml, sensors): teams founded and disbanded, alliances, the server up and stopping — on as shipped — and kills, joins and leaves — off, being busy — each with its own message (discord.*), routed like any announcement. Embeds (style: embed), a colour per rule, and a role or member pinged by a rule (mention) — nothing else ever pings. Existing servers: copy style and sensors from the jar's discord.yml, and the new discord.* lines of lang/en.yml; without sensors, only the raid news is heard, as before.
• A combat logger leaves a stand-in (pvp.yml, combat-tag.logout: npc): a villager where they stood (logger.entity), at full health — ten hearts (logger.health) —, knocked back by blows but never walking (logger.knockback), which only a player can hurt, by the rules of a blow at them. Killed, their items fall and the death counts as any other — deathban, DTR, team points, statistics, kill reward, bounty, death sign —, and they come back to spawn with nothing; alive when the tag runs out, it goes and they keep everything; back first, they take its place, with the health they left with less the damage it took. Each hit starts both tags over. CombatLoggerDeathEvent in the API. kill-on-logout: true now means the stand-in; set logout: kill for death on the spot as before. Copy the pvp.combat-logger lines of lang/en.yml from the jar.
• A Mountain is claimed land (resourcenodes.yml, claim, y-min, y-max): the land of a server team, drawn with the claiming wand — /resourcenode claim <id> makes the team, a combat zone, and hands the wand — and shown on /team map and at its border. Between its heights it is mined by its own rules; the region follows the land as it changes. Two corners still work. The shipped Mountains now name server teams (Glowstone, OreMountain); a server's own resourcenodes.yml with corners is read as before.
• A capture zone is part of its event's claim: drawn with /events setzone past the edge of the event's territory, the territory grows to hold it, claim-margin blocks around (events.yml, setup.zone-claims-land), where it used to only warn. Add zone-claims-land: false under setup to keep the warning alone.
• /buildmode and /editmode for /staffbuild: staff build through protection — spawn, roads, events — until they type it again.
• /kit fromchest <id>: a kit from a chest — the one looked at, or at coordinates from the console — its armour put on, the rest in the chest's order. Copy the kit.admin.created-from-chest and no-chest lines of lang/en.yml from the jar.
• [Refill] signs (kits.yml, refill-signs.refill-line): a kit's items in a self-service window — potions, pearls, golden swords for a player back at spawn — taken freely, never used up, nothing cleared; nothing can be put in or thrown out. The window is a double chest (refill-rows), and /kit fromchest on a double chest keeps its 54 slots as laid out. Copy refill-line and refill-rows from the jar's kits.yml and the kit.sign.refill-title line of lang/en.yml.
• Your own Lunar nametag (apollo.yml, nametags.show-self): your team and its DTR above your own head, in third person — Lunar draws it with its "show own nametag" setting on.
• Server teams may have longer names: staff name server land up to 32 characters (GlowstoneMountain); a player's team stays within max-length, 16 as shipped.
• The Bard's invisibility is an ink sac, as on most HCF servers, where it was gunpowder (classes.yml). A server's own classes.yml keeps its item: rename GUNPOWDER to INK_SAC under the Bard's held-effects to follow.
• An invitation is clickable: a click on it joins the team. /team leader for /team transfer, and /team forceleader (forcetransfer) for staff, who make anybody the leader of their team. Copy the team.invite and team.transfer.leader-forced lines of lang/en.yml from the jar.
• Overlapping starts (weekly-schedule.overlap): an event still running when a planned one starts is stopped for it (replace, as shipped), keeps running while the planned one is skipped (skip), or runs alongside it (both).

Changed

• The wall around spawn is a ball around the player: the safe zone's border within 15 blocks of a player in combat, all round (safe-zones.wall.radius-blocks), instead of 15 blocks each way up to layer 128 — far fewer blocks read and sent. width-blocks, top-y and minimum-height are no longer read.
• No pause in DTR regeneration after a death: a team is raidable while its DTR is below zero — back at 0.00 it is protected — and regenerates from the moment of the death, +0.1 every 90 seconds (regeneration.interval-seconds): the raid lasts the climb back to zero, 15 minutes from -1. /team setregen is the one way left to pause it. regeneration.freeze-seconds is no longer read; take interval-seconds: 90 from the jar to have the new pace.
• The Purge opens enemy blocks, not raiding: anybody may use the doors, chests and buttons of other teams' claims, but nobody builds or breaks there unless its DTR makes it raidable (phases.yml, purge.use-enemy-blocks).
• EOTW opens server land too: roads, event territories and mountains are open to building and breaking like every claim, the safe zones — spawn — aside (eotw.open-server-land, keep-safe-zones, protected-teams).
• Kill the King is started by staff only: a time in its schedule, daily or weekly, is shown in /schedule and announced, never acted on.
• The King cannot leave the warzone: walking, a pearl, a teleport out are refused, and they see its edge as a wall within 15 blocks, as spawn's is shown in combat (reign.wall). The Wither for a King outside is off (outside-penalty.enabled: false). To keep the Wither on an existing server, add enabled: true under outside-penalty.
• A King who logs out is banned for 2 hours (reign.quit-ban-seconds), the event ending with no winner as before.
• Only active players are drawn as King: idle for 5 minutes — no move, look, chat, command or click — and a player is left out (reign.afk-seconds).

Removed

• Classic combat (1.7.10) is gone: the server plays the game's own combat. A plugin of its own, for 1.7.10 and 1.8 combat, will follow 1.0. What it left behind is taken back as it is seen — a sword that blocks, a weapon at its 1.7 damage, when a player joins, picks the item or opens a chest; a player's held-off regeneration when they join. combat in config.yml and legacy-combat in pvp.yml are no longer read and can be deleted; the console says so.

Fixed

• /pvp help did not exist, though every mistake pointed to it, and a staff command typed short answered "Unknown command": help now lists what you may use under the name you typed (/db help, /ct help), and a short command shows its usage. /db help no longer looks for a player named "help". ban takes an optional length: with none, as long as a death would ban that player. Copy the pvp.help lines of lang/en.yml from the jar.
• The Fake Pearl stayed greyed out after /cooldown reset: the game's own cooldown on it was left running. A reset of the abilities, or of the Fake Pearl, now ends it too.
• /pvp lift completed the online players, who are never the ones banned: Tab now offers the deathbanned, as /revive does — a ban until the map ends included, which staff can lift. /pvp check offers both.
• A death sign placed by a player who is not an operator was blank, and opened the sign editor: the game copies a block's data from its item for operators only. The plugin now writes the sign and waxes it when placed, for everybody, and refuses the editor and any rewriting.

0.9.0 - 2026-09-27

Teams set up without a single command: /team settings holds the team's profile — its description and Discord invitation —, who may join (closed, on invitation, open), each rank's permissions, its members and invitations, the claim lock and the HQ. A new rank, the officer. Shortcuts: /hq, /fc, /f i. deposit all and withdraw all for the team bank.

Tried in game on Paper 26.2 with two players: everything below. Several settings came with it: the notes under each change say what to copy from the jar — your configuration files are never rewritten, and a missing key takes its default.

Added

• Officers: a rank between member and co-leader (teams.yml, max-officers, no limit as shipped). /team promote now goes member → officer → co-leader, and nobody promotes somebody to their own rank.
• /team settings (alias options): a window where a team sets itself up with no command to type, for every member — each button checks its own rank and says under it who may use it. Its profile: name, description and Discord invitation, typed in the game's own dialogs and shown in /team info (the link clickable). Who may join: closed, on invitation (as shipped) or open. Permissions: the lowest rank for each (every key of required-roles, and open-subclaims); whoever changes one must hold it and cannot set it above their own rank, and the server locks some for every team (team-settings.locked: disband and transfer-leadership as shipped). Members (promote, demote, kick), invitations (invite a player by typing a name, take one back), the claim lock and set HQ. Kept in the new table hcf_team_settings. Existing servers: copy the team-settings and shortcuts sections, max-officers and required-roles.settings from the jar's teams.yml, and the new team.settings, team.join-mode, team.join.closed, team.info (description, discord, join-mode, officers), team.role.officer, team.promote.officer-limit, claim.menu and ui.tab.role-officer lines of lang/en.yml — without them, the defaults apply.
• Shortcuts (teams.yml, shortcuts): /hq, /base, /stuck and /fc as commands of their own, and /team i, h, home, sh, d, w, m, k, s for info, hq, sethq, deposit, withdraw, map, kick, settings. Both lists are the server's; a name another plugin already has is left to it.
• Who may join a team: closed (nobody; staff still can), on invitation (as shipped) or open (/team join without an invitation) — each team's choice in /team settings, among team-settings.join-modes, from default-join-mode.
• The shop's back button is configurable (economy.yml, shop.menu.back-icon).
• /team deposit all and /team withdraw all: everything in your wallet into the bank, or the whole bank out — as much as your balance can still hold under the ceiling.

Changed

• Invite, revoke an invite, focus and rally need an officer as shipped (required-roles), not a co-leader. A server's own teams.yml keeps its values.
• shop.enabled: false leaves /shop to another plugin: the shop switched off gives the name /shop to another shop plugin's /shop, where there was a clash.

Fixed

• Tab in the chat offered the HCF grid's cells (!tab00...) instead of the players' names: the cells are no longer completed, and the players you can see are.

0.8.1 - 2026-09-24

Kill the King fixed after its first try in game: the King keeps the kit's armour on, and their death is the event's — no kit to loot, no DTR lost, no deathban. /revive completes the names of the deathbanned. And the license is now plain MIT.

Tried in game on Paper 26.2: Kill the King in team mode, before these fixes. The fixes themselves and the solo mode are not yet tried in game.

Added

• The King cannot take off their armour (events.yml, kill-the-king.<id>.reign.lock-armour, on as shipped): no click, drag or key swap on an armour slot, no right-click swap with another piece.
• /revive completes names: Tab offers the players deathbanned now (never a ban until the map ends, which a life cannot lift).

Changed

• The license is plain MIT: the additional attribution requirement is gone. Keeping the copyright and permission notice with the software, as MIT asks, is all that remains.
• The King's death is the event's, not a real one (reign): the kit vanishes with the reign instead of dropping as loot (drop-kit: false), the King's team loses no DTR (death-costs-dtr: false) and the King is not deathbanned (deathban: false) — they respawn and get their own items back. A King who logs out in combat is not spared. To keep the 0.8.0 behaviour, set all three to true in a reign section; without the section, the new values apply.

0.8.0 - 2026-09-23

Claims drawn block by block with the claiming wand, and every event set up in game with the same commands — three new ones (DTC, Last Break, Slide), the Totem and Mini Totem, a weekly schedule. Territory shown in the world, safe zones that close to anybody in combat, and an economy for the fights: money for a kill, a shop, bounties. Kill the King in teams or alone, Discord announcements, mining alerts, death signs, subclaims.

Tried in game on Paper 26.2 with two players: the claiming wand and block-precise claims, the event setup commands, DTC, Last Break, the Totem, the weekly schedule, the map pillars and the lock wall, safe zones, mining alerts, death signs, points and money for a kill, the shop and bounties. Not yet tried in game: the Slide, both Kill the King modes, subclaims and the Discord webhook. Several settings changed: the Changed section says what to do.

Added

• The claiming wand — claims are drawn block by block, the traditional HCF way. /team claim hands over the wand (a golden hoe): left-click a block for the first corner, right-click one for the second, sneak + left-click to claim the rectangle between them, full height; drop it to give up. The corners show as glass columns only its holder sees, and the chat gives the size, the price and anything that would refuse the claim before it is confirmed. Staff draw server land with it (/team createsystem, /team forceclaim <team>: free, no size or placement rule), event territories (/events claim <id>) and event zones (/events setzone <id>, setup.zone-height in events.yml). Configured in claims.yml (wand).
• Claims are paid from the team bank: price.per-block (0.25), 75 % of what was paid back on /team unclaim (price.refund-percent). Money is the limit; sizes keeps each claim sensible — at least 5 × 5, at most 128 a side, optional caps on claims and surface. /team here shows the claim's size and corners; /team map is drawn in 8-block cells (map.cell-blocks).
• /team createsystem hands over the claiming wand at once, to draw the new safe or combat zone.
• An event's territory is a claim like any other: the land of a server team, named in the event's claim key (as a Citadel's always was), drawn with the claiming wand. /events create and /events claim make the team — a combat zone named after the event — and write the key. An existing event without a claim key keeps working; /events info finds a server team named after it, and /events claim writes the key.
• One way to set up every event — KOTH, Citadel, Kill the King, Conquest, DTC, Last Break, Slide, Totem, Mini Totem — with the same commands (hcfcore.events.admin): /events create <type> <id> makes a new event where you stand, copied from the shipped example of its kind, its territory claimed; /events info <id> shows what it has and lacks, with the command for each; /events claim <id> and unclaim <id> [all] draw and release its territory with the claiming wand; /events setzone <id> [zone] draws its zone (a Conquest's named zone — a new name adds one) and delzone <id> <zone> removes one; /events setblock <id> places a DTC's core or a Totem's column; /events delete <id> removes any event and releases its territory. /events setcore, settotem and setzone <id> <1|2> are gone: setblock and the wand replace them. In events.yml, setup.default-zone-radius and setcore-distance are no longer read — take auto-claim, claim-margin and target-distance from the jar.
• Three new capture events, events.yml:
  • DTC (Destroy The Core): a permanent block core inside a zone — end stone while the event runs, bedrock between runs, like a Totem's column (core.material, core.idle-material) — broken by teams — a per-team cooldown (break-cooldown-seconds), counter: SHARED (common health, most breaks of its own wins a tie by whoever reached that count first) or PER_TEAM (first to its own target wins at once).
  • Last Break: the same engine, always common health — whoever lands the break that empties it wins, even with fewer breaks of its own.
  • Slide: every team member standing in a zone scores for their team every interval-seconds, cumulative; a death anywhere costs the team death-penalty points; first to points-to-win wins, with a live top 3 on the scoreboard.
  • Creative, spectator and teamless players never break a core or score in a Slide.
  • Staff set them up in game, like every other event (see above) — the only commands in the plugin that ever rewrite a configuration file, and only the one section they name. The console warns when a core is not on server land.
  • New scoreboard placeholders %dtc_line%, %dtc_team_line%, %last_break_line%, %slide_line%, %slide_top_1..3%; a hologram above every core and Slide zone; Lunar Client waypoints on a running core and Slide zone.
  • New team points: teams.yml's points.per-dtc-win, per-last-break-win, per-slide-win (the scale is under Changed). Configuration files are never rewritten: copy the dtc:, last-break: and slide: sections (and the setup: section) from the jar's events.yml, the three new points.per-*-win lines of teams.yml, and the new dtc_line/last_break_line/slide_line/slide_top_* lines of ui.yml into your own files.
• Totem and Mini Totem (events.yml, totem:): a column of 5 blocks (3 for the Mini Totem), bedrock between runs and quartz during one. Teams mine it with a sword, block by block (instant-break: true makes one hit enough); every block a team breaks turns to bedrock, and the first team to break the whole column wins — but a block broken by any other team starts it over, every block quartz again (rival-break, RESET or RESET_AND_START). Set up with /events create totem|minitotem <id> and /events setblock <id>; %totem_line% on the scoreboard, a hologram, a Lunar waypoint and points.per-totem-win in teams.yml. Existing servers: copy the totem: section of events.yml, per-totem-win of teams.yml and the %totem_line% rows of ui.yml from the jar.
• A weekly schedule (events.yml, weekly-schedule): which event starts at what time on which day of the week, started by the plugin itself exactly as /events start would; /schedule add <day> <HH:mm> <event> and /schedule remove <day> <HH:mm> [event] edit it in game. Every start — weekly or an event's daily schedule — is announced ahead (announce-before-minutes, 15, 5 and 1 minute). Existing servers: copy the weekly-schedule section of events.yml and the events.planning messages of lang/en.yml from the jar — without the section, the weekly schedule is empty but on.
• /schedule (/planning): every event start of the next seven days, day by day, for everybody.
• /schedule opens as a window (events.yml, weekly-schedule.menu): one item per day of the week ahead, holding that day's events hour by hour. /schedule chat still prints the list, and the console always gets it.
• Kill the King has two modes (events.yml, mode): team, as before — the King's team defends them and the winner's team scores — or solo — everybody against the King, teammates included, and the prize is the winner's own reward commands (crate keys, money), no team points.
• Nobody helps the King, in either mode: no Bard buff, no partner item, no potion thrown by somebody else (healing included), no beacon — the kit and what they drink or eat themselves.
• No abilities on an event's land (abilities.yml, disabled-in.event-territory): partner items are refused on the territory of an event — its server team's claims, not only the zone held or stood in — during-event (as shipped: until it ends), always (at any time, as on a safe zone) or never. An event decides for its own land with disable-abilities: never|during-event|always in events.yml. Existing servers: add event-territory: during-event under disabled-in — without it, that default applies.
• /team map is drawn in the world (claims.yml, map.style, pillars as shipped): a column on each corner of every player team's claim within four chunks (server land is left out, include-system-claims), from the ground to layer 128, one ore or block of ore per team — drawn at random each time, named in the chat under the map — shown to you alone and gone after 20 seconds, or at the next /team map - the command is the switch. The chat says which block marks which team. /team map chat still draws the old grid, whose size is now configurable too (map.chat.radius-x, radius-z). Existing servers: map.cell-blocks moved to map.chat.cell-blocks; take the new map section from the jar.
• A locked claim shows a wall (claims.yml, lock.wall): red glass around its border, from the ground to layer 128, appearing as they come within five blocks of it, to the players the lock refuses and to nobody else, sent like the wand's columns and never placed. Members see nothing. It is redrawn as a player walks rather than on a timer, each claim's wall being read from the world once and kept.
• The claiming wand's columns are seen through a clear-glass pack: one block in every six is glowstone (wand.pillar-marker-material, pillar-marker-every).
• Subclaims (claims.yml, subclaims): a [Subclaim] sign on a chest of your team's land, with the players allowed below, keeps your other members out of it — no opening, breaking, rewriting its sign or hopper under it. Co-leaders and the leader open them all.
• Safe zones take no damage at all (pvp.yml, safe-zones.no-damage) and fill health and hunger back up (heal, keep-fed), all on as shipped: on spawn, a fall, fire, drowning, suffocation, a mob or a cactus does nothing.
• Spawn is closed while you are in combat (safe-zones.block-combat-tagged, on as shipped): a combat tag refuses the step into a safe zone — walking, a pearl, any jump — until it runs out, and the border is shown as a wall of red glass 15 blocks each way in front of the player, to layer 128 (safe-zones.wall). Existing servers: take the whole safe-zones section from the jar — without the new keys, their defaults (all on) apply.
• Death signs (pvp.yml, death-signs): a kill by a player leaves a sign — the dead player, "slain by", the killer, the date — that keeps its text when placed and cannot be rewritten. It falls with the loot, or goes to the killer (to-killer).
• Money for a kill (economy.yml, kill-reward): 10 to the killer — the unit the shop and bounties are priced on, plus, if you set steal-percent, a share of the dead player's balance. Nothing for an ally, and nothing again for the same victim within 5 minutes.
• A shop (economy.yml, shop): [Buy] and [Sell] signs placed by staff, the /shop menu, or both (mode). The menu opens on shelves — ores, combat, the Archer's leather and every dye, potions, food, building, utility, farming — about a hundred items priced on a 10-a-kill economy; ores are sold, the rest bought, and the shop never buys back what it sells. Only plain items are ever taken.
• Bounties (economy.yml, bounties): /bounty <player> <amount> puts money on a head, taken from your balance at once; whoever kills the target collects it all — never a teammate or an ally. /bounty lists the largest. Saved in a new table, hcf_bounties, created by itself.
• /lff [note] (teams.yml, lff): a player with no team tells everybody they want one, with a few words of their own — once every 5 minutes.
• Mining alerts (staff.yml, mining-alerts): staff are told when a player breaks into a vein of diamond, ancient debris or emerald — once per vein, with its size and position. Player-placed ores are never reported; audience: everyone shows everybody the classic "[FD]" line, without the position.
• Announcements on Discord (discord.yml, off as shipped): through a webhook, the server posts event starts and results, SOTW and EOTW, bounties, and teams going raidable to a Discord channel — routed by rules on the language keys, chatty lines left out, nobody ever pinged.

Changed

• A team made raidable loses half its points (teams.yml, points.raidable-loss-percent, 50), or a fixed number with the share at 0 (per-raidable). A file with its own per-raidable and no share keeps meaning what it said.
• Team points have a scale out of the box (teams.yml), where everything shipped at 0: a kill +1, a death −2, and an event worth far more than the kills fought for it — a KOTH capture 100, a Citadel 300, a Conquest 250, a DTC and a Slide 200, Kill the King, a Last Break and a Totem 150, a Mini Totem 80 — so the event, not the farm, decides the ranking. A Citadel and a Mini Totem now have values of their own (points.per-citadel-capture, per-mini-totem-win) instead of a KOTH's and a Totem's. Existing files keep their own numbers; take the points section from the jar for the new scale.
• Territory is block-precise: a claim is a rectangle, not a set of chunks; the buffer between teams is in blocks (placement.buffer-blocks, 8), a new claim must share an edge with the team's land, and the warzone's radius is exact instead of rounded to chunks. Existing chunk claims are converted automatically on the first start — same land, paid nothing, so refunding nothing; the console says how many. In claims.yml, limits (base, per-member, maximum, max-per-command) and placement.minimum-distance-to-others are no longer read: take the new wand, price, sizes, placement and map sections from the jar. /team claim [radius] and /team forceclaim <team> [radius] take no radius any more.
• Blocks per claim (limiters.yml, claim-blocks) are counted per team as well as per chunk, since two teams can now share a chunk. The counts are rebuilt as claimed chunks load; until a chunk has loaded once, its blocks are not counted.

0.7.0 - 2026-09-19

A look for the whole plugin — one theme, gradients, and the Theme Builder to design it — and the tab list of an HCF server: the grid, with heads, or the classic list with LuckPerms ranks, and nothing to install. Strikes by offence, elevator signs.

Tried in game on Paper 26.2 with two players: the theme, both tab lists, strikes, elevators and the staff mode. A setting or two changed: the Changed section says what to do.

Added

• Elevator signs (elevators.yml): a sign written [Elevator] over Up or Down takes whoever right-clicks it up or down its column — straight to the next elevator sign in that column, whatever lies between, or, for a sign alone in its column, to the next floor. Refused on an enemy's land unless it is raidable; optionally kept to one's own land or refused in combat.
• A theme for the whole plugin (theme.yml): eight colours by role, a message prefix, a list symbol, small-capital titles, framed menus. Every text is written with tokens — {primary}, {secondary}, {muted}, {success}, {error}, {prefix}, {bullet}, {action} — so a colour changed there changes everywhere. Shipped as "Or royal": gold and cream, a bold HCF » on the announcements, Label ➥ value scoreboard rows, black-framed menus with gold corners. Hex colours (&#rrggbb) now work in any text.
• Gradients: a colour of theme.yml may be "#F5B32E>#FF4D3D" — two colours or more — and the text it colours fades letter by letter.
• A whole look in one file: theme.yml may also set texts (messages, any key of lang/en.yml), the chat line (chat) and the Lunar nametags (nametags), in place of the other files.
• The Theme Builder (online): design the whole look — colours and gradients, prefix, menus, scoreboard, tab list, chat, nametags, holograms — with live previews in the game's typeface, items and skins, from 14 palettes, and download a complete theme.yml and ui.yml, one by one or zipped. It reads a theme.yml you already have.
• Two tab lists (ui.yml, tablist.style): the HCF grid — four columns of twenty cells in place of the player list: player info and location, team and members, server and events, top teams, every cell yours to write, with heads — an icon beside each category title, each member's face beside their name, a dark grey square in every other cell, and any account's skin or any mineskin.org skin wherever you want one — set in the Theme Builder by name or mineskin.org link — and the classic list, each player written with their LuckPerms prefix and suffix and ordered by rank, kills or name. auto, as shipped, shows the grid on an HCF server and the list on a kitmap. The grid needs nothing installed: the plugin sends the server's own tab list packets. The Theme Builder previews and writes both, and lets you change a title's head by clicking it in the preview — a player's name or a mineskin.org link.
• Menus page themselves when their items do not fit — /ability has two pages, /tickets is no longer capped at 54.
• Strikes by offence: a strike is given for an offence — cheating (50% of the team's points), bug abuse, kill boosting (40%), teaming (35%), other (25%) — and a team is disbanded at its 3rd active strike, whatever they were for (staff.yml, strikes.offences and disband-at). /strike add <team|player> <offence> [details]; /strike offences lists them. /team show writes a struck team's Strikes: N; a strike is no longer announced in the general chat — staff are told, and the team's members when it disbands them — and the details staff add are for staff only.

Changed

• The tab list is on by default, as the HCF grid (or the classic list on a kitmap), and its header and footer are redrawn every second — they were sent once, on joining. An existing ui.yml keeps its tablist: enabled: false; its old header and footer are no longer read: take the new tablist section from the jar and put your lines in hcf or classic.
• Staff mode: the Random Teleport is an eye of ender, and the Vanish switch a grey dye that turns green while vanished (vanished-material, a new toolbar setting). An existing staff.yml keeps its items: set material: ENDER_EYE in slot 1, and material: GRAY_DYE with vanished-material: LIME_DYE in slot 7.
• Strikes: the ladder (strikes.ladder, a sanction by number of strikes) is replaced by offences and disband-at. A staff.yml with a ladder keeps working with the shipped offences, and says so: move its numbers to strikes.offences and disband-at. /strike add now takes an offence before the details.
• Every shipped message, menu, scoreboard row, hologram line and chat format uses the theme. The Lunar nametags' team line uses the theme too. An existing lang/en.yml, ui.yml and the other files keep their look: take the new ones from the jar for the theme's, then put your changes back. The Pocket Bard menu is 27 slots, its sets at 10, 12, 14 and 16. staff.ticket.menu.more is gone.

Fixed

• %online% counted vanished staff, so the scoreboard and the tab list gave a vanished player away. It now counts the players each viewer can see; a vanished teammate also shows offline in the tab list's members to whoever cannot see them.

0.6.0 - 2026-09-19

Partner items, and the cooldowns of an HCF server: the ender pearl, golden apples and the like, all on the scoreboard and on Lunar Client. The scoreboard can be trimmed by each player in /settings.

Tried in game on Paper 26.2 with two players, except the damage a sword block takes off, which still awaits a two-player test.

Added

• Partner items: 42 abilities built in (abilities.yml) — Switcher, Thunderbolt, Combo, Lucky Mode, Rage Ball, Crafting Chaos, Focus Mode, Ninja Track, Portable Archer, Invisibility, Time Warp, Pocket Bard, Berserk, Close Call, Switch Stick, Belch Bomb, Reverse Ninja Track, Rose Thorn, Pumpkin Reaper, Hulk Smash, Sticky Web, Med Kit, Grappling Hook, Nausea Axe, Bunny Hop, Ice Berg, Antidote, Golden Head, Grabber, Poisonous Potato, Fake Pearl, Rocket, Combo Fish, Anti-Build Bone, Rotten Egg, Rage Strength, Olympia, Baguette, Sun, Scrambler, Lucky Bard, Disarmer Wand — and a commands type for your own. 38 types, several generic: effects, hit-effects, thrown-effects. An item may stay and count its uses on its durability bar instead of being used up (uses): the Olympia, 30 shots, the Pumpkin Reaper and the Nausea Axe, 10 each, spent only when they work, and the Portable Archer, 5. The Pocket Bard has no cooldown; the items it gives wait 60 seconds between two uses, each set apart, and the shared cooldown. The Ninja Track goes to the last player you hit, the Reverse Ninja Track to the last who hit you, 10 seconds back at most (types ninja-track and reverse-ninja-track). The Sun catches and counts only the enemies in range. A chance that misses (Nausea Axe, Pumpkin Reaper, Disarmer Wand) starts the cooldown but keeps the item and its uses. A shared cooldown after any ability (10 s), and zones where none works (a safe zone, a Citadel's claim, a running event's zone, the Nether, the End). /ability shows them with your cooldowns; /ability give hands one out.
• Ender pearl cooldown: 15 seconds between two pearls (pvp.yml, ender-pearl-cooldown), shown on the scoreboard (%pearl_line%), on the pearls in the hotbar and on Lunar Client (apollo.yml, ender-pearl). A death ends it. Until it is over, teleport commands are refused as in combat — /spawn, /team hq, /team stuck, /top, /world (block-teleport). An existing ui.yml needs "%pearl_line%" added to its lines to show it; pvp.yml and apollo.yml work without the new keys, with the defaults.
• Item cooldowns (pvp.yml, item-cooldowns): the Gapple waits 1 hour, the Crapple 10 seconds, the chorus fruit 15, the totem 2 minutes — any item can be added. A use meanwhile is refused; a totem on cooldown saves nobody. Kept on the player, so the Gapple's hour survives logouts and restarts; shown on the scoreboard (%cooldown_<id>_line%), on the item and on Lunar Client. An existing ui.yml needs the %cooldown_<id>_line% rows added to show them.
• /cooldown reset <player> [what] ends a player's cooldowns — all (the default), abilities, global, pearl, items, or one ability's or item's id (hcfcore.cooldown.admin).
• The scoreboard, section by section, in /settings: team, statistics, balance, combat tag, cooldowns, class, events, timers. A row of ui.yml belongs to a section by a tag at its start — [team]&cTeam: &f%team% — placed as you like. In an existing ui.yml, tag the rows; in settings.yml, add the scoreboard-<section> switches to offered.
• Lunar Client shows every cooldown: besides the combat tag, countdowns and partner items, now the ender pearl, the item cooldowns, the shared partner item cooldown, the Pocket Bard's sets, a class's click items and backstab, and the crowbar — each switchable in apollo.yml (ability-global-icon, classes, crowbar). An existing apollo.yml works without the new keys.

Changed

• A class's held effect ignores an item carrying this plugin's data — a Pocket Bard's blaze powder in a Bard's hand gives the Pocket Bard's effect on a right-click, never the class's held Strength too, as its clicks already did.
• Partner items moved from kits.yml to abilities.yml, and /kit ability became /ability give (permission hcfcore.ability.admin). A commands ability of your kits.yml goes under abilities: in abilities.yml with type: commands; items already handed out keep working if their id is kept. A killstreak or redeem command using kit ability becomes ability give.

0.5.0 - 2026-09-18

Everyday commands, and the fixes of a first round of in-game tests: classes, the Bard, classic combat, effect commands.

Tried in game on Paper 26.2 with two players, except the damage a sword block takes off, which awaits a two-player test.

Added

• Everyday commands, as an essentials plugin gives them: /clearinventory (/ci, /clearinv), /feed (/eat), /fly, /god, /flyspeed, /walkspeed, /hat, /suicide, /extinguish (/ext), /workbench (/wb, /craft), /anvil, /enderchest (/ec, /echest), /i (/giveitem), /tphere (/s), /tppos, /gmc, /gms, /gma, /gmsp, /day, /night, /sun, /rain. One permission each, hcfcore.general.<command>, and .others to act on another player; operators by default. /tpa, /home, /back and /near are left out on purpose.
• A test reads every shipped YAML file with the parser the server uses: a file that does not parse fails the build.
• Classes: a class may have its own warmup-seconds. The shipped Diamond has none — it gives no effect, so there is nothing to wait for. In an existing classes.yml, add warmup-seconds: 0 under diamond.
• Classes: include-self on a held or click effect decides whether a team effect reaches its user too. The shipped Bard gives Strength I to the team but not to itself; its Strength II burst reaches it as well. In an existing classes.yml, add include-self: false under the Bard's held BLAZE_POWDER.

Changed

• Classes: the archer tag adds 15% damage as shipped, not 25% (damage-multiplier: 1.15). An existing classes.yml keeps its value: set it under the Archer's archer-tag.
• Every name and lore line the plugin writes on an item is upright, no longer in the game's italics: /dyes, /settings, the ticket menu, the staff toolbar, partner items, the King's kit, the crowbar, custom enchant books, /rename.
• Classes: held effects follow the scroll wheel — an item's effect comes the moment it is in hand, and is renewed four times a second instead of once (held-effect-interval-ticks in classes.yml, 5 ticks). Existing files do without the setting: the default applies.
• Classes: an effect a class gives its user alone (the Rogue's jump, the Archer's speed) says how long it lasts — Used Jump Boost V - applied for 5s — rather than how many players it reached, which is for the Bard's team effects.
• Classes: the warmup and the energy show on the scoreboard only (%class_line%, %class_energy_line% in ui.yml); the warmup chat message ships empty. A burst says the energy it cost and what is left. An existing lang/en.yml keeps its warmup message: set classes.warmup: "" to silence it; an existing ui.yml needs the two lines added to its scoreboard to show them.

Fixed

• Classic combat: the modern regeneration still spent a hurt player's hunger fast — the game charges it even when its heal is refused. The food bar's own regeneration is now held off while classic regeneration is on, and given back otherwise.
• Classic combat: a rod's bobber stayed on the player it hit until reeled in, pulling them. It comes back at once (fishing-rod.remove-hook, on as shipped), and reeling in a hooked player is refused, so a right-click at the moment of the hit pulls nobody.
• The effect commands' messages showed their raw key (effect-commands.on): YAML reads a key on or off as a boolean. They are given and taken now, and a test refuses such a key in every shipped file.

Documentation

• The documentation reviewed for consistency: effect caps and commands in every summary, the classes messages, effect commands in their own FEATURES section, and which modules still await their in-game test.

0.4.0 - 2026-09-18

Potions, effects and the Bard.

Added

• Effect caps (limiters.yml, effects.caps): the highest level an effect may have on a player, whatever gives it — potion, class, custom enchant, the King, golden apple, beacon, command, another plugin. /hcf reload and joining bring down what players already have.
• Effect commands (effect-commands.yml): /speed, /strength and your own give an effect at a configured level until death; typing the command again takes it off. Shipped: /speed (/sp, Speed II), /strength (/str, Strength I), /resistance (/res), /regeneration (/regen), /jumpboost (/jb, Jump Boost II), /fireresistance (/fres, /fr), /invisibility (/invis, /invi), /haste (/hst, Haste II), /nightvision (/nv). Permission hcfcore.effect.<command>, operators only by default.
• Versioning: releases with their jar, this changelog, and a release workflow that refuses a tag not matching the plugin's version.

Changed

• A forbidden potion (capped at 0 in potions.caps) is no longer brewed, and drinking, throwing or shooting one is refused with a message, the potion kept, instead of being used up for nothing.
• The shipped Bard: holding gunpowder gives the team Invisibility I. Every held effect lasts 8 seconds after the item is put away, 5 before. The spider eye Wither II burst is removed; a click effect with targets: enemies still does it. An existing classes.yml is not changed: add the GUNPOWDER block under held-effects, set seconds: 8 on each held effect, and remove SPIDER_EYE from click-effects by hand.

Fixed

• A class turning off could take an infinite effect it had not given.

0.3.0 - 2026-09-18

Classic 1.7.10 combat.

Added

• Classic combat (combat: classic in config.yml, tuned in pvp.yml's legacy-combat): no attack cooldown or sweep, criticals while sprinting, sword blocking, 1.7 knockback, no off-hand or shields, 1.7 potion and pearl throws, no pearl cooldown, 1.7 regeneration and golden apples, rodding.
• 1.7 weapon damage — swords harder, axes softer, shown in the tooltip — and 1.7 Sharpness, +1.25 per level. A blow is rebuilt the 1.7 way: weapon, Strength, critical, Sharpness, so a critical or Strength never multiplies Sharpness.
• 1.7 Strength, a percentage of the weapon's damage (+130% per level), with its own nerf, a percentage too (legacy-combat.strength.nerf, +65%).

Fixed

• The Strength nerf took the Strength bonus out of arrows, which never carried it.

0.2.0 - 2026-09-18

Classes and events.

Added

• Classes: Diamond, Bard, Archer, Rogue, Miner, and your own in classes.yml — armour set, passive, held and click effects, energy, archer tag, backstab. /class.
• Dyed sets (dye-effects): an Archer's arrows have a 20% chance to give an effect by the dye colour of the set — green Poison I, black Wither I, blue Slowness I. /dyes lists them.
• Citadels in a claimed Citadel (citadels: in events.yml): on its land, ender pearls, partner items, chorus fruit, elytra and Riptide are refused at all times; class abilities keep working.

Changed

• Kill the King: the King's position is a scoreboard row (%king_location_line%), and the chat says where the King is once a minute with their health (announce-interval-seconds). coordinates-interval-ticks is no longer used.
• Every configuration example in the documentation is quoted from the shipped files.

0.1.0 - 2026-09-18

Added

• First public version: teams, territory and DTR, combat and deathbans, lives, capture events (KOTH, Citadel, Conquest, Kill the King), Mountains, SOTW/EOTW/Purge, economy with Vault, kits and abilities, custom enchants and limiters, moderation tools, scoreboard and chat, holograms, redeem codes, the Lunar Client integration, and this documentation.