Skip to content

HCFCore 0.10.0

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 29 Sep 18:55
· 19 commits to main since this release

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.