Changelog

v1.7.4 developer notes

Built on Hytale Update 7 like 1.7.3, so ServerVersion is unchanged, against ZiggfreedCommon 2.5.1 and the RPG Stations 1.1.3 api (contract 10). MMOSkillTreeAPI and the api project are unchanged, and nothing is removed.

Breaking changes

• Requires ZiggfreedCommon 2.5.1. ziggfreedCommonVersion and MMOSkillTreePlugin.REQUIRED_ZIGGFREED_COMMON read 2.5.1, so the manifest's ^2.5.1 refuses 2.5.0 by name. The jar calls nothing 2.5.1 added; the pin moves so every server on 1.7.4 runs 2.5.1's fixes and its rollback sweep. rpgStationsApiVersion stays 1.1.3, and the manifest's optional Ziggfreed:RpgStations range stays >=1.1.1 <2.0.0.

Technical

• The Skills Menu Scroll and the retired Quest Book open on right click. Mmo_Menu_Scroll's Charging chain into mmo_menu_open and Mmo_Quest_Book's into mmo_quest_menu_open move from Primary to Secondary, as CommonLib 2.5.1 moves the Objective Book, so a left click no longer opens either.
• The Item Rewards room check asks CommonLib. CommandRewardService asks CommonLib's room probe (GroundSpillSinks.pickupFits: hotbar, storage and backpack, the room vanilla /give fills) before an authored /give, on the Item Rewards Collect and for auto-claim rewards at level-up. It asked only the Storage section (canAddItemStacks), so a full storage refused a reward the hotbar or backpack had room for. It still fails closed with no live reference.
• A level's /give rewards share one room check. One Collect press and one level-up auto-claim pass ask about each /give reward together with the gives already let through (the new commandreward.GiveBatch over GroundSpillSinks.pickupFits), since a dispatched /give lands later on the command pool: two rewards that each fit alone could both pass, and the second was lost. A reward that would no longer fit waits for the next press, and the rewards after it still pay when they fit. CommandRewardService.claimSingleReward takes a GiveBatch (GiveBatch.of(player)) in place of the Player. Test: GiveBatchTest.

v1.7.3 developer notes

Built on Hytale Update 7 like 1.7.2, so ServerVersion is unchanged, against ZiggfreedCommon 2.5.0 and the RPG Stations 1.1.3 api (contract 10). MMOSkillTreeAPI and the api project are unchanged, and nothing is removed.

Breaking changes

• Requires ZiggfreedCommon 2.5.0. ziggfreedCommonVersion and MMOSkillTreePlugin.REQUIRED_ZIGGFREED_COMMON read 2.5.0, so the manifest's ^2.5.0 refuses 2.4.x by name: the jar calls 2.5.0's ObjectiveTargetNames and RequiresVolumeAudit.auditAll (below). rpgStationsApiVersion moves to 1.1.3 (RPG Stations' Greater Disenchanting Table recipe fix), and the manifest's optional Ziggfreed:RpgStations range stays >=1.1.1 <2.0.0.

Technical

• Swords gets its XP ladder, and the combat ladders pay combat. Achievements/MMOSkillTree/Combat/Weapons/Swords_Xp_T1.json to _T3.json copy the Axes ladder rung for rung (chain swords_xp, GAIN_XP on SWORDS at 10,000, 100,000 and 1,000,000, paying Swords Mmo_Xp 500, 2,500 and 50,000 and a 2x Swords boost for 60 minutes at the top; melee SortOrder 70 to 72), with four new mmoskilltree.lang keys (achievement.swords_xp_t1.title to _t3.title, achievement.announce.swords_xp_t3.title) in every locale. In the combat_kills and combat_damage ladders, First_Blood pays an Mmo_Lamp of 100 over COMBAT in place of Defense Mmo_Xp 100, and Warlord and Force_Of_Nature drop their Swords Mmo_Boost_Token (2x, 90 and 60 minutes), keeping their 50,000 Mmo_Lamp over COMBAT, so every rung of both ladders pays a combat lamp. (A boost token naming the COMBAT category reads as a non-active skill to the achievement audit, NON_ACTIVE_REWARD_SKILL.)

• The last direct hand-overs go through CommonLib's delivery. The mastery respec's item refund (MasteryService), the Class System's starting items (ClassService) and the ability cast item restore (AbilityCastItemService) hand items over through CommonLib's one delivery (LootRewardKinds.handToPlayer) instead of adding them straight to the Storage section. The respec refund is one spill: what fits goes where the player's pickup settings route it, with the game's pickup notice, the rest at their feet, and a part that lands nowhere is parked on the pending-rewards spool as a plain give line, which LootRewardKinds.replayParked pays at the next connect (never a CommonLib Item reward, which would count as loot for loot quests); the call is wrapped so a throw cannot skip the bookkeeping after the currency refund. The cast restore probes GroundSpillSinks.pickupFits first, so it counts the hotbar and backpack, and still refuses on a full bag rather than spilling, so its "free up space" line stays true.
• Gear-set steps name the set. TargetNameResolver asks ZiggfreedCommon's ObjectiveTargetNames for a kind it has no reading of its own for (GEAR_SET_TIER today) before prettifying the id, so a gear-set step with no text of its own names the set by its TitleKey on the MMO's pages too. objective.text.gear_set_tier reads "Wear {0} pieces of the {1}", retranslated in every locale.
• /mmoconfig validate reports trigger-volume gates. ContentAudit registers the gate domain, "ZigRequires volume validation", from ZiggfreedCommon 2.5.0's RequiresVolumeAudit.auditAll(), so /mmoconfig validate and the startup content audit report a pack's ZigRequires trigger-volume problems beside every other content domain.
• Tests and docs. HallowsEveRetrofitPinTest's Old Jack conversation method and HarvestFeastPackContentTest's Martha intro method, which pinned the hosts' ForgottenTemple opening beats and temple-scoped greeting memory that Seasons of Orbis 1.3.0 drops, are deleted with their helpers. SeasonsOfOrbisFactionTest.everyReputationAndWalletThePackPaysOrChargesIsOneItOrAGatedCompanionShips again checks that every reputation and wallet the pack pays or charges is one it ships or a gated companion pack's (the bounty pack's Life_Essence behind its mod gate), with a fixtures test for its gate branches. CONTENT_PACKS.md's encounter macros table lists CommonLib's Zc_Wave_Rise and Zc_Wave_Chain, and ZigFeedback's row names the wave argument every beat carries.

v1.7.2 developer notes

Built on Hytale Update 7 (0.7.0) like 1.7.1, so ServerVersion is unchanged, against ZiggfreedCommon 2.4.0 and the RPG Stations 1.1.2 api (contract 10). MMOSkillTreeAPI and the api project are unchanged. What a pack, an owner file or a caller can no longer reach is under Breaking changes and Removed.

Breaking changes

• Requires ZiggfreedCommon 2.4.0. ziggfreedCommonVersion and MMOSkillTreePlugin.REQUIRED_ZIGGFREED_COMMON read 2.4.0, so the manifest's ^2.4.0 refuses 2.3.0 by name: the jar uses 2.4.0's round kinds and its default board reading (below). rpgStationsApiVersion reads 1.1.2, the RPG Stations release this build compiles against; the manifest's optional Ziggfreed:RpgStations range stays >=1.1.1 <2.0.0, since the jar calls nothing 1.1.2 added.
• The jar no longer ships Hallow's Eve's MMO layer. Its eleven Hallows_Eve files go: the boost rule Mmo_Hallows_Eve_Harvest_Moon, the mob-kill map Mmo_Hallows_Eve, the XP map Hallows_Eve, the station extensions Mmo_Hallows_Eve_Carving and Mmo_Hallows_Eve_Carving_Hallowed, the four skill dailies Mmo_Hallows_Eve_Daily_{Artillery,Crafting,Harvesting,Mining}, the gear set Mmo_Hallows_Eve_Hallowed and the lootable Mmo_Hallows_Eve_Geode_Crack, with their lines in all nine locales (board.grade.hallows_eve_skill, boostrule.mmo_hallows_eve_harvest_moon.title, gearset.mmo_hallows_eve_hallowed.tier_full and the dailies' quest.mmo_hallows_eve_daily_* pairs). Seasons of Orbis has carried the same ids and keys since 1.1.0 (its hallowseve.mmo.lang), so a server running it sees no change. HallowsEveLayerTwinTest, which held the two copies equal, is deleted; the layer tests (HallowsEveLayer, HallowsEveJarContentTest, HallowsEveMmoLangTest and the rest) read the pack alone.
• Items keep their own interaction maps. AbilityInteractionInjector, which wrote MMO_Trigger_Ability1 into every item's Ability1 slot, is retired with its registration and test: the per-player key claim already owns Q whenever a bound slot can cast. The never-loaded Server/UnarmedInteractions/Empty.json and its scan directory go. The three unreachable hold-to-charge roots MMO_Trigger_Ability1_Charged, MMO_Trigger_Ability2_Charged and MMO_Trigger_Ability3_Charged are removed, so a third-party item that names one loses that item at load; it re-authors on the plain MMO_Trigger_Ability1 to MMO_Trigger_Ability3. TriggerKey's dead labels go; MmoCastAbilityInteraction's Trigger and NativeInput docs, CONTENT_PACKS.md and the trigger roots' comments match the code, and the interaction and ability schemas are regenerated. Player-visible only in one case: Q on an item with a free Ability1 slot while abilities are off is now silent.
• Three player commands check their own node. /mmoachievements, /mmoabilities and /mmoability's player subcommands (use, bind, unbind, input, list) check mmoskilltree.command.mmoachievements, mmoskilltree.command.mmoabilities and mmoskilltree.command.mmoability when command permissions are on, like every other command. Every per-command denial goes through one helper, PermissionUtil.requireCommandPermission, on the existing cmd.no_permission key instead of raw English, so it reads in the player's language.
• School resistances are CommonLib's DamageResist_ stats. The eleven MMO_SchoolResist_ stat assets are removed, with no grace version: SchoolResistStats aliases each to its successors (Physical to DamageResist_Physical and _Projectile), so an item enhanced before reads its roll under the new ids (StackStats normalizes through the aliases) and stores them on its next stamp. Its eleven itemTooltip.stats.MMO_SchoolResist_* lines stay in client.lang, as the retired MMO_Bonus ones did: the tooltip a stamp wrote onto such an item (ItemDisplayMetadata, written by StampTooltip only at a stamp or /mmoitemenhance refresh) still names the old key until then. A third party's item naming an old id in its native StatModifiers still loads, but that stat gives nothing (the engine skips a stat id it does not know): rename it to DamageResist_, a Physical resistance on both _Physical and _Projectile.

Technical

• One applier for school resistance, CommonLib's. Every writer (a claimed SCHOOL_RESIST and class passives through foldGlobalContributions, mastery's schoolResist mirror, /mmoitemenhance's armor roll) writes DamageSchools.resistStatIds as a modifier on the stat's Max, which is what resists (a permanent MmoChangeStat moves the value, so it resists nothing, as before; it still syncs), and ZiggfreedCommon 2.4.0's DamageResistReconciler keeps the engine's resistance in step with those stats every tick, so SchoolResistReconciler, its MMO_SchoolResistSync_* effects (dropped by the engine at load, never swept) and its bridge listener go. SchoolResistStats installs the per-world combat-bonus rule (DamageResistances.installGate) and maps the SchoolResist clamp's Max onto the ceiling (installCeiling; maxPercent() for the clamps page and DamageSchoolValidator); the defense fold still reads no school term. Tests: SchoolResistReconcilerTest moves to CommonLib's DamageResistReconcilerTest (its defense-fold check to DefenseFoldNoSchoolTermTest, its clamp check to SchoolResistStatsTest, which also reads the alias table directly against the eleven retired ids); DamageSchoolsStatIdTest, the roster's resist-label check (now DamageResistStatsTest in CommonLib) and an armor roll's one-to-three entry count go, and AuthoredStatTypeDecodeTest drops the removed assets.
• Bounty boards open on CommonLib's quest page. ZiggfreedCommon 2.4.0's CommercePages.openBoard opens every board on the quest page with the board as its host, so Mmo_Board, BountyBoardOpenInteraction, /mmobountyui and the hub's contract deep link land there with no MMO change. MmoBounties.difficultyColor (both overloads) retires with COLOR_UNGRADED, boardOrNull and their imports, since CommonLib paints a contract's grade from its board's own colours; MmoBountiesTest and its MmoBountiesTestBoards, which covered only them, are deleted. Comments that named the old board page or board screen (BountyBoardOpenInteraction, ProgressStateMigration, ProgressionUnclaimedMoveTest, MmoHubPage, OnboardingPage) name the quest page.
• The Objective Book's contracts read CommonLib's default board reading. MmoObjectiveBookDeps no longer fills boardManaged: its BountyPresentation, bountyPill and gradePill go, and ZiggfreedCommon 2.4.0's BoardContracts paints a carried contract's tag word, its grade pill in the board's own colour and where it hands in. ui.quests.bounty_pill and ui.quests.bounty_at_board leave all nine locales; MmoObjectiveBookDepsTest's two tests of the retired pills are deleted.
• Records' Skills tab ranks each period by XP gained. SkillRecordsSplit opts into CommonLib's StatSplit.offAllTime: on a week, a month or a season, Total Level, each category and each skill pick rank Xp_Earned gained in that period (StatisticsComponent.KEY_XP_EARNED, counted at each grant: the total on Total Level, beside abilities cast and station cycles, a category's skills summed, a skill's own line), headed ui.leaderboard.header_xp_gained ("XP GAINED"), with the player's All Time level beside their name (StatSplit.Meta over SkillGauges.SKILL_LEVEL, parts over 1, ui.leaderboard.level_beside_name = Lv {0, number}). All Time ranks level with XP breaking a tie, as in 1.7.1. The period buckets fill from this version on. New en-US keys ui.leaderboard.header_xp_gained and ui.leaderboard.level_beside_name; Mmo_Skills.json's $Comment says so.
• A level-up shows in an open page. notifyLevelUpByName sent only a HUD notification, which sits hidden behind an open page. With a toastable page showing it draws a REWARD page toast instead: the skill's icon and the same line the HUD notice carries (the new-player tip at levels 2 and 3, else the skill tree reward the level unlocks, else none), ranked ToastSpec.PRIORITY_EARNED, so the reach-level quest step fired right after waits behind it in CommonLib's toast queue. With no page open, the HUD notification as before; never both. The level-up sound still plays apart and the toast adds none.
• Reward toasts section their lootables. RewardListRenderer.toastLines hands its per-reward reading to CommonLib's RewardToastLines.linesBy, so a quest or claim paying XP and a Lootable shows the XP first and the bundle under its own heading; QuestToasts drops its duplicate cap. ToastablePage.showRewardToast(headline, skills, rewards) hands those rows, already sectioned and capped, straight to a private showRewardRows, so a receipt toast is capped once; the overload taking pre-built lines still caps the lines its callers built.
• A skill's item rewards preview its XP token. The global XP token reward gives XpToken_{skill}_Token, and only the claim filled {skill} (MmoPlaceholders.skillCommand), so the item-rewards ladder previewed the literal id, which no item answers to: the client showed "Invalid Item" over a blank slot. A skill's ladder fills {skill} first by the claim's own rule (new MmoPlaceholders.skillOnly, through a RewardPreviewBuilder.from overload ItemRewardsPage passes its skill to); the total level's ladder, with no one skill, reads the line as authored. Only the item and currency reads use the filled line; a boost line reads as authored, since the fill is a skill's display name.
• A named boost reward reads its boost as its description. A command reward's localizationKey (or displayName) replaces the typed boost line as its card's name, which left a named /mmoboost give row with no word of its multiplier or minutes. RewardPreviewBuilder's boost branch now uses MmoChipReading.boostLine as the description when the row names itself and writes no descriptionKey or description; a row with its own description keeps it, and an unnamed row reads as before. The taming pack's collected level rewards rely on it. Test: RewardPreviewBuilderTest.namedBoostCommandRewardEntry_withNoDescription_readsTheBoostLineAsItsDescription.
• Multi-criterion achievements read their own step lines. ZiggfreedCommon 2.4.0's AchievementReader asks each criterion's line by its authored Criteria id, the key CommonAchievementFold files it under, where it asked by position; no MMO change.
• Admin pages answer every click, and the Abilities page saves a bind when it is set. AdminSectionPage gains answer(), and every handleDataEvent exit that sent nothing (a missing player, a text-field echo, a missing action, a null dropdown or row value, a default arm, a caught bad number) answers, in all 15 section pages and the admin hub. A refused admin re-check shows cmd.no_permission on the page's status line through a new overridable statusSelector() (#AddStatus on CommandRewards, MobKillXp and MobDropCommands, whose documents carry no #ActionStatus); WhiteLabelConfigPage no longer reaches its switch with a null action. The General page's skill and command permission switches re-check OP on the event, not only on the binding. The HUD & Abilities page's Bar Panels note says what the HUD bars page sets (ui.admin.hud_bars_note reworded), and a failed open reports its own line (new ui.admin.status.hud_bars_failed). New ability/input/AbilitySlotBindingService binds, unbinds and re-keys a slot (mutate, save SKILLS, reconcile key claims), shared by /mmoability's three writes and AbilityBindPage.route(), so the page's binds save when set (the database backend saved them only at logout before); a throwaway component is never saved or reconciled, and AbilityCastItemService.restoreMissing saves when it gave anything.
• Native damage-over-time ticks skip the swing path. Since Update 7 an owned burn, poison or rune tick carries its caster (Damage.EntityEffectSource), so each tick ran the held weapon's cancels, fold, crit, next-hit buff and mark spends, combo, passives, lifesteal and damage XP. MmoDamageSource.isNativeDotTick classifies such a tick (never the MMO's own DotDamageSource); CombatDamageEventSystem lets it deal its native damage untouched, and CombatXpEventSystem pays it XP only through a tag: row mapped to the effect, never a cause: row or the held weapon. Kill credit, DEAL_DAMAGE progress and a mob tick's Defense reduction are unchanged; a mob tick's Defense XP keys on a tag: or cause: row, else the mob. A guard test pins the classifier.
• Small fixes. /mmoconfig validate folds CommonLib's LootAudit.auditAll, so reward-kind files and bonus rows are audited too and may report problems a pack already had. The absurd-cooldown and absurd-cost audits (AbilityValidator) read their ceiling from the live ParamClampTable (an owner's ability-clamps.json included), falling back to the shipped Max, and state the real bound. DamageSchools.resolveSchool walks Inherits through the engine's DamageCause.isOrInherits, the nearest school winning. SkillType's Swords icon names Weapon_Sword_Crude. SchooledDeployableAoeConfig drops the handleDetection override the engine no longer needs. skill-config.json's never-read comboChainId and comboChainLength are gone with SkillConfig's accessors. HitDamage.json's comment and ModifierClampsPage's javadoc state the clamp as it runs. presets/ is an input of :test.
• Name ladders and key probes are CommonLib's. TargetNameResolver stays the MMO's seam and delegates prettify and the entity and zone name ladders to NativeNames; LocalizationConfig's full-key and client-key probes ask LangCatalog; the four canonical copies they replaced go. Output is unchanged, except that a whitespace-only target id names nothing instead of a space, and a probe before the language module is up answers false instead of possibly throwing.
• The retired MMO_Bonus ids' alias is pinned. SchoolBonusStatsAliasTest reads every MMO_Bonus_ and MMO_BonusFlat_ id from the shipped en-US tooltip labels and asserts each resolves to exactly CommonLib's DamageBonus_ or DamageBonusFlat_ (Physical to both Physical and Projectile), that unrelated ids stay unaliased, and that a saved stack's Physical roll reads in full under both.
• Dialogue findings come from CommonLib's conversation audit. The MMO claims ZiggfreedCommon 2.4.0's first-join dialogue audit (DialogueAudit.claimLateAudit) beside the placement one, so the first join logs [dialogue] content findings are reported by MMOSkillTree and CommonLib reports no lines of its own. MmoDialogueValidator runs DialogueAudit.auditConversations with its switched-off-feature exemption and keeps only the MMO's own Reward and CompleteQuest checks and its ids inside a Requires block (below); QuestValidator takes completion findings from DialogueAudit.completionFindings. In /mmoconfig validate's dialogue domain an unknown quest state is one error (QUEST_STATE_UNKNOWN); unknown quest ids are also found in node conditions, AnyOf/AllOf/Not branches, Start beat actions and extension lines; UNKNOWN_QUEST_STATE is gone and ACTION_MISSING_QUEST covers CompleteQuest only. The test that pinned a duplicate check goes.
• Gate and HasActiveBounties are CommonLib's; Reward and RunCommand are deprecated for Grant. ZiggfreedCommon 2.4.0 registers the Requires dialogue condition (with Gate as its deprecated spelling) and HasActiveBounties, so the MMO registers neither: MmoDialogueConditions goes (Removed, below), Mmo_Hub_Intro.json's six gates are written as Requires, and MmoDialogueEngine latches on CompleteQuest. MmoDialogueValidator reads a held-shut line through CommonLib's RequiresDialogueCondition.Block, warns REWARD_ACTION_DEPRECATED and RUN_COMMAND_DEPRECATED on each use on a conversation's own lines and Start beats (both actions still run; dialogue-extension lines are not walked), and checks only this mod's ids inside a Requires block through the new ValidationChecks.checkOwnVocabulary, which checkGate shares: an unknown mmoskilltree:feature is UNKNOWN_FEATURE (an ERROR), with unknown skills and the mastery-node param's shape. The block's generic audit is CommonLib's, so nothing is reported twice. CONTENT_PACKS.md teaches Grant, Requires and HasActiveBounties and marks the three deprecated. Tests: DialogueValidatorTest.aMistypedFeatureInARequiresBlockIsAnErrorReportedOnce, and optionGatedOffByFeature_questRefsNotAudited on Requires.
• A hard Gobliterator win earns the standard rung too. Goblin_Gobliterator_T1's ENCOUNTER_DEFEATED criterion matches Goblin_Gobliterator_Encounter by PREFIX where it matched EXACT, so it counts both scripts (the standard fight and Goblin_Gobliterator_Encounter_Hard); with no Qualifier, a first win on hard earns it and Goblin_Gobliterator_Hard together. The criterion key is unchanged. achievement.goblin_gobliterator_t1.desc drops "with Hard Mode off".
• A turn-in line reads a character's own sentence. ObjectiveTextRenderer reads objective.text.turn_in.return. or objective.text.turn_in.find. (the id lower-cased; this mod's catalogue first, then any pack's) before the shared Return to {0} and Go to {0}, so a character whose name needs its article writes the whole line. New en-US keys for mmo_hub and mmo_hub_temple: "Return to the Adventurer's Guide" and "Go to the Adventurer's Guide".
• New: the dungeon round kinds. ObjectiveType gains INSTANCE_ROUND_STARTED and INSTANCE_ROUND_LOST, both quest-producible, their targets named the way the other round kinds' are. CONTENT_PACKS.md lists the four round kinds with a dungeon run's target (dungeon:) and qualifier (the dungeon id).
• New: the gear-set tier kind. ObjectiveType.GEAR_SET_TIER mirrors ZiggfreedCommon 2.4.0's kind (ObjectiveKinds/Gear_Set_Tier.json, fired by its gear-set producer when a tier comes on): Target the set id, no Qualifier, the amount the tier's piece count. It is value-based and quest-producible, so the MMO's folds, validator, sentences and name paths keep such a step. New en-US keys objective.text.gear_set_tier ("Wear {0} pieces of {1}") and objective.text.gear_set_tier.any. ObjectiveKindVocabularyTest's calendar and reputation checks share one helper and check the new kind file too.
• New: the encounter feat kind. ObjectiveType gains ENCOUNTER_FEAT, ZiggfreedCommon 2.4.0's built-in kind for a boss fight won a particular way (Target the encounter script id, as for ENCOUNTER_DEFEATED; Qualifier the name of a feat the binding row authors under Progression.Feats), quest-producible beside the other encounter kinds, so the MMO's fold, validator, target names (TargetNameResolver) and objective icons (MmoObjectiveIcons, the encounter icon) know it; CommonLib produces it. CONTENT_PACKS.md's binding-row and encounter-kind tables name Feats and the kind.
• The Adventurer's Guide's questlines are main quests. The onboarding quests Getting_Started, Craft_Starter_Tools, Gather_The_Basics, Into_The_Fray and Climbing_The_Ranks and the Temple quests What_The_Stones_Remember, The_Watch_Below and Keeper_Of_The_Deep write Listing.MainLine true (ZiggfreedCommon 2.4.0), so a quest list shows them first with the star and the gold bar; every other quest (Forgot_Something, the four under Onboarding/SideQuests/, Temple_Tribute and The_Gobliterator) writes none.
• CONTENT_PACKS.md follows CommonLib 2.4.0's boss credit and loot tables. The Participation row and "Who gets credit" name DamageToAdds, the weight for damage dealt to a fight's adds, and its default of 0; a Lootable reward reads as its table by default, with PlainBundle, ListContents and a roll's HideInPreview.
• /mmoconfig validate reports dungeons and runs each validator once. ContentAudit registers ZiggfreedCommon 2.4.0's dungeon domain (DungeonValidator.audit() folded through ValidationChecks.fold, as auditGearSets does), so the startup audit and /mmoconfig validate report a pack's dungeons beside every other content domain; CommonLib's ZigRequires trigger-volume audit stays a check CommonLib runs at every boot. /mmoconfig validate ran every validator twice, once for the chat summary and again for the log: it runs them once and hands the same result to logAll, now public, the one logging path runAndLogAll and the boot pass use, so the chat and log lines read as before. labelOf names exactly the registered domains plus the two that register at runtime (ability_mod, station_bridge): hit_tag, encounter, gear_set, reputation, dungeon and station_bridge gain labels, and bounty, shop and station, which no caller passes, leave. ContentAuditLibraryDomainsTest pins dungeon with the other library domains.
• /mmomigrate names CommonLib 2.4.0's retired reputation pieces. MigrationClassifier.classifyPack and classifyOwner run their old bodies, then one check: a JSON under a pack's shared or MMO store, or a live owner JSON (not a leftover copy or a _defaults echo), whose Factor leaf is exactly ziggfreedcommon:reputation_earned (which now fails closed) gets REPUTATION_EARNED_REPLACEMENT appended to the row of the family that already claims it (a converted row stays converted, any other becomes needs-hands), or a needs-hands row of its own; a Factors/ file that only names the retired factor is told to delete itself (REPUTATION_EARNED_NAME_OVERLAY_DETAIL), and a Reputations/ file with a top-level Gear (inert since CommonLib 2.4.0) gets REPUTATION_GEAR_RETIRED_DETAIL, naming Gear.Stat and the ReputationGain stats that replace it. Report only: boot converts neither, and OwnerApply leaves an owner file naming the factor as it is. New migration-corpus cases (old-jack-reputation-earned, retired_reputation_earned_quest, owner_mastery_reputation_earned, reputation_earned_name_overlay, retired_reputation_gear, and negative_reputation_gain, which is not a finding); tests in MigrationClassifierTest and OwnerApplyTest.
• One writer for _reference. config/ReferenceFiles is the one writer of mods/mmoskilltree/_reference/ and writes a reference only when its bytes change, so a boot that changes nothing touches no file. ReferenceFiles.removeRetired deletes seven retired references by exact name once at setup (the defaults-.json files for luck-loot, abilities, elite-mobs, currencies, mastery, classes and mob-drop-commands), leaving any other file there alone. MasteryConfig, ClassesConfig and MobDropCommandsConfig write no reference, since theirs held no defaults, and RewardIconsDefaults.byCombatTarget is insertion-ordered so its reference stays put. ui.help.mastery.how and ui.help.mastery.examples describe per-field overrides as they work. Test: ReferenceFilesTest.
• Tests. For the Headless Horseman's content in Seasons of Orbis, HallowsEveRetrofitPinTest loses noIdIsAddedOrDropped (with DROPPED_ON_PURPOSE), theIdsLeftOutAreExactlyTheLayersLibraryStoreTwins and noOtherIdCarriesTheMmosRows (with LATER_CONTRACTS), and SeasonsOfOrbisMmoRowsTest loses thisModIsNamedOnlyInTheRewardRowsOfQuestsContractsAndAchievements (with HARVEST_FEAST_SKILL_JOBS, dropRows and withoutComments); the classes' other checks stay. HallowsEveRetrofitPinTest allows Old Jack's opt.board leaving his menu and the two reputations dropping their Gear leaf, only where the current file has none; the frozen tree is untouched. HarvestFeastPackContentTest.theConversationOpensNoClosedDoorOffSeason keeps its two live checks and drops the door count. HallowsEveRetrofitPinTest also drops the one line pinning Old Jack's Start.Quests rows, which The Rider's row grows on purpose (the loop over every frozen quest's offer, brief and hand-in still runs); the frozen-lock comparison and its LOCK_DROPPED_ON_PURPOSE set, which The Hollow Lantern's new Requires blocks; the pin that opt.shop is written once, since Old Jack's sweets answer reuses it (opt.standing and opt.almanac keep theirs); and aChildOfABaseThatWritesItsOwnRequiresStillHidesOffSeason, which with SeasonsOfOrbisFactionTest.everyReputationAndWalletThePackPaysOrChargesIsOneItShips (also deleted) blocked Old Jack's Life Essence offers, a companion pack's wallet behind a mod gate the unit JVM reads as absent. Since each season's keepsake became its last quest's own pay, HallowsEveRetrofitPinTest takes achievement:hallows_eve_lantern_keepsake out of its collected-on-purpose list and HarvestFeastPackContentTest drops its check that the keepsake achievement's stack carries @year. DialogueContentResolutionTest registers DungeonDestinations, since the Gravekeeper's conversation opens a dungeon. SeasonsOfOrbisMmoRowsTest derives which Seasons of Orbis files must pay MMO rows from the pack itself, in place of its hand-kept list: every quest, contract or achievement with pay beyond a title carries a gated MMO row, and every dungeon Claim and boss daily Claim a gated Mmo_ contribution. LethalHitAttributionTest's expiry case reads the clock after record stamps its entry, so a slow build can no longer leave the entry live past the spin.
• One ready-time gear recompute. PlayerReadyFlow no longer calls recomputeAll itself: ZiggfreedCommon 2.4.0 recomputes every player through the equip-stat bridge at a LATE PlayerReadyEvent (GearSets.onPlayerReady), so the MMO's pass only repeated it. The plugin still takes the installed bridge for its key segments and listeners.
• A Skill Lamp and a parked reward land like a pickup. SkillLampService.give (behind /mmolamp give, so the Mmo_Lamp reward kind, and a rub's hand-back) hands the lamp over through ZiggfreedCommon 2.4.0's LootRewardKinds.handToPlayer: where the player's pickup settings route it, with the game's own pickup notice and sound, else at their feet through the overflow policy. It answers the new SkillLampService.Handed (BAG, FEET, LOST, read off GroundSpillSinks.pickupFits before the hand-over) in place of InventoryGrant.Landed, and /mmolamp give says when a lamp could not be placed at all. The PendingRewards spool now drains in PlayerReadyFlow's NORMAL pass, after the hydrate, instead of at PlayerConnectEvent, where no item could reach a bag: RewardExecutor.deliverPendingRewards(PlayerRef) replays each line through LootRewardKinds.replayParked, so a parked item reward lands the same way (and parks again on a live grant's terms) while every other line still runs as the console. The green "You received {0} quest reward(s)!" summary after a drain is gone, since the game's own pickup notices say what arrived, and its key notify.quest_rewards_delivered leaves every locale.

Removed

• SkillComponent.setInventoryCastingMode(boolean) and isInventoryCastingMode(), deprecated since 1.0.1 (a no-op and an always-false). The inventory casting mode no longer exists.
• IntegrationRegistry's typed getters getFishingIntegration, getParriesIntegration, getCitizensIntegration, getEnchantingIntegration and getActiveIntegration, which nothing called.
• MmoBounties.difficultyColor, both forms, with COLOR_UNGRADED and boardOrNull. CommonLib paints a contract's grade from its board's colours.
• MmoDialogueConditions (GateCondition, HasActiveBountiesCondition) and MmoBounties.hasActiveBounties. CommonLib 2.4.0's RequiresDialogueCondition and HasActiveBountiesDialogueCondition answer both.
• About 260 lang keys nothing read, from all nine locales: the legacy ability.summary templates (155), the old bind page's lines, ability.condition, the pre-gate status lines, reward.cape, the old XP panel, the retired leaderboard and settings lines, page, boost, time and tip leftovers, achievement.hidden and its progress line, the shadow NPC names, notify.xp_gain_bonus, notify.quest_rewards_delivered and npcs.lang's Mmo_QuestGiver.hint.
• About 1,600 lines nothing called: eleven QuestService members, pages/ConfirmGate, pages/render/PlayerNameText, CommandRewardService's run-every and inventory helpers, the join-time StatisticsComponent zero-init, SchoolResistReconciler.sweepRetired (the engine already drops an effect whose asset is gone), NativeChainAudit.decide, license/LicenseGate, SkillDisplayUtil's chat-era formatters, CostChipRenderer's dead renderers and colours, SkillTreeService's unused getters, a dozen small members and the boot sweep of *_backup_backup* files. The tests that pinned only them go (ConfirmGateTest, PlayerNameTextTest, NativeChainAuditTest's cases).

v1.7.1 developer notes

The Update 7 port of 1.7.0, built against the 0.7.0 server jar (patchline=pre-release until Oct 12), ZiggfreedCommon 2.3.0 and the RPG Stations 1.1.1 api (contract 10). Behaviour changes only where Update 7 moved the ground under the mod.

Breaking changes

• Requires Hytale Update 7 and ZiggfreedCommon 2.3.0. ServerVersion reads >=0.7.0-pre.0 <0.8.0. ziggfreedCommonVersion and MMOSkillTreePlugin.REQUIRED_ZIGGFREED_COMMON read 2.3.0, so the manifest's ^2.3.0 refuses the 0.6.8-built 2.2.0 by name. rpgStationsApiVersion reads 1.1.1; the optional Ziggfreed:RpgStations range rises to >=1.1.1 <2.0.0. MMOSkillTreeAPI's signatures are unchanged; getStatistics returns a read-only copy of CommonLib's stat record (Technical, below).
• The school damage bonus stats are CommonLib's. The 22 MMO_Bonus_ and MMO_BonusFlat_ stat assets are removed. A pack item's native StatModifiers naming one counts for nothing, since the engine skips a stat it does not know, so it names DamageBonus_ and DamageBonusFlat_ instead, a Physical bonus on both _Physical and _Projectile. Rolls an item saved through enhancement read under the new ids by themselves (Technical, below).
• Ability inputs move to the free keys. MmoSlot.defaultInputs() is slot 1 on P (middle mouse, Pick), slot 2 on PC, slot 3 on A4 (H, Ability4). TriggerKey.freeInputs(), so the picker and stance mode's off-move fallback, run middle mouse, crouch+middle mouse, H, crouch+H. Every save moves there once at its next ready, whatever it held (AbilityInputMigration, run in PlayerReadyFlow's player-data pass behind the new SkillComponent key AbilityInputLayout, and saved at once with markDirtyAndFlush, since the database backend re-hydrates on every world entry). A one-time chat line goes only to a player with an ability in a slot. TriggerKey gains ABILITY_4, ABILITY_4_CROUCH, PICK and PICK_CROUCH (codec A4, A4C, P, PC), which a 1.7.0 jar parses as no input.

Technical

• The Temple's Due's pay table draws its pool (ZiggfreedCommon 2.3.0). temple_tribute pays Mmo_Temple_Offering through a Lootable reward, which on ZiggfreedCommon 2.2.0 read only a table's Rolls. ZiggfreedCommon 2.3.0's Lootable reward resolves the whole table, so the offering's Pool (one Eternal seed bag) draws on every claim, and its 1% relic roll, a Lootable reward naming the pool-only Mmo_Temple_Relic that threw before, pays one Ancient Steel piece. No MMO code or content changed.
• The hookshot pull and NPC impulses. 0.7.0's Role.processSetVelocityInstruction applies a Set times the role's KnockbackScale and skips the drag discount (preScaleKnockback), where 0.6.8 multiplied X and Z by about 0.044. MmoHookshotPullInteraction drops NPC_DRAG_CANCEL_SCALE (25) and its NPC branch: every target takes the resolved speed through Sizing.pullVelocity(...). VelocityImpulseUtil never scaled by caster kind, so its maths stays; it moved into the pure impulseVelocity(...), and an NPC caster's dash or dodge covers its full authored distance on 0.7.0 (about four percent of it on 0.6.8). Tests: MmoHookshotPullSizingTest (the NPC-only pair replaced by the 0.7.0 contract on the same targets), VelocityImpulseUtilTest.
• The ogre's XP tier moves to Goblin_Glutton, and the Feastmaster boss gets rows of its own. MobKillXpDefaults and DefenseDefaults key Goblin_Glutton (700 HP, its own model; Coffer_Goblin_Glutton and Dungeon_Goblin_Glutton match it by longest substring) where they keyed Goblin_Ogre, which Update 7 deletes. The final 0.7.0 split the pre-release's Goblin_Feastmaster into that overworld elite and the Deepworks boss, whose two phase roles Dungeon_Feastmaster_Boss and Dungeon_Feastmaster_Feeding take 2,500 kill XP and 30 Defense per hit taken, the top boss rate; they are keyed in full, so the Dungeon_Feastmaster_Scrapper adds never take a boss's row. Goblin_Guardian (90 HP, the goblin model at 1.1 scale) stays on the plain Goblin row. An owner override on Goblin_Ogre matches nothing now. No test: HeavyGoblinXpKeysTest, which pinned the removed role, is deleted.
• The Gobliterator gets boss rows of its own. MobKillXpDefaults keys Goblin_Gobliterator at 5,000 and Goblin_Gobliterator_Phase3_HM at 15,000, and DefenseDefaults the same two at 30 per hit taken, the top boss rate (a Defense row pays on each hit a player takes from that role, so its number stays per hit while the kill XP carries the scale). Goblin_Gobliterator takes every role of the fight, the _HM twins included, and the longer Goblin_Gobliterator_Phase3_HM wins over it by longest substring, so a hard win pays 15,000 and never also 5,000. The phases swap role in place (ChangeTargetRole, invulnerable through each swap) and only Goblin_Gobliterator_Phase3 or _Phase3_HM can die, so a win pays once; the barrels, the legs and Goblin_Pilot are invulnerable, and Goblin_Pilot misses the row. No test.
• The shipped presets' ogre steps. presets/balanced_rpg.mmop.json, hardcore_survival.mmop.json and adventure_explorer.mmop.json each had two KILL_ENTITY steps (kill_ogres, trophy_goblin) on Goblin_Ogre, which no 0.7.0 role matches; they are ENCOUNTER_DEFEATED steps on Dungeon_Feastmaster_Encounter, the Deepworks boss's fight, with their ids (saved progress) kept and their amounts cut for a boss: kill_ogres from 5 to 1 in Adventure Explorer and Balanced RPG and from 10 to 3 in Hardcore Survival, trophy_goblin 1, and 2 in Hardcore Survival. Their raw displayText reads "Defeat the Feastmaster", with the count where it is above one (the import converter drops it). A server that applied one of these presets keeps the old target in its own quest files. Test: ShippedPresetKillTargetsTest (no shipped preset's kill step targets a role Update 7 removed; the removed set is the 0.6.8-to-0.7.0 role-file diff, 23 ids, frozen in the test).
• New: boss ladders for Update 7's fights. Three ladders in Combat > Bosses, each at 1, 10 and 50. Goblin_Feastmaster_T1 to T3 count ENCOUNTER_DEFEATED on Dungeon_Feastmaster_Encounter through both phases, under a criterion renamed from the pre-release's elite kill so no such kill carries. Voidtaken_Grizzly_T1 to T3 count Bear_Voidtaken (EXACT). Blight_Warden_T1 to T3 count Kweebec Nightmare's KweebecNightmare_Warden_Encounter, hidden without it (hytale:mod_installed). Every rung pays Defense XP to collect. Each 50 rung grants a title on unlock and announces: Mmo_Goblin_Feastmaster (The Feastbreaker), Mmo_Voidtaken_Grizzly (The Voidhunter) and Mmo_Blight_Warden (The Wardenbreaker). No test.
• New: the Gobliterator's achievements. Two files in Combat > Bosses. Goblin_Gobliterator_T1 counts one ENCOUNTER_DEFEATED on Goblin_Gobliterator_Encounter (EXACT; the script id, so it holds through the machine's phases), tier 1 of the chain kills_goblin_gobliterator, 20 points and 1,000 Defense XP to collect. Goblin_Gobliterator_Hard counts one on Goblin_Gobliterator_Encounter_Hard with Qualifier hard, which CommonLib 2.3.0's binding row for the hard script writes, 60 points and 5,000 Defense XP. The two scripts are separate, so a hard win pays the hard one only. Every player the fight credits earns them. No title. New en-US keys achievement.goblin_gobliterator_t1.* and achievement.goblin_gobliterator_hard.* (title and description), in all nine languages. No test.
• New: the Gobliterator quest. Quests/MMOSkillTree/Temple/The_Gobliterator.json, given and taken at Mmo_Hub_Temple (TurnInId giver) behind meet_at_the_temple: one ENCOUNTER_DEFEATED step on Goblin_Gobliterator_Encounter (CONTAINS, so the _Hard script counts too), credited through CommonLib 2.3.0's binding rows for both scripts, and a Claim Mmo_Lamp of 5,000 over COMBAT, pick 1. The step words its own line (TextKey objective.text.quest.defeat_gobliterator), since CommonLib's shared objective.encounter_defeated sentence names the boss by its boss-bar name, Gobliterator MkIIII. The fight stays in the Deepworks; the temple only gives the errand and takes the report. New en-US keys quest.the_gobliterator.title, .flavor and objective.text.quest.defeat_gobliterator. Test: ShippedQuestContractTest.SHIPPED_IDS gains the_gobliterator.
• Damage types are Hytale's, plus CommonLib's three. Every hit keys an Update 7 type or one of ZiggfreedCommon 2.3.0's Arcane, Void and Life (moved from this jar to CommonLib's zc-core, Inherits Elemental, each with its DamageTextColor and DeathMessageKey). The jar's Server/Entity/Damage/Lightning.json, Water.json and Poison.json, which replaced Update 7's own, are deleted, so those types keep the game's colours and death lines.
•     The 13 per-ability types retire: SchoolCauseGenerator, its MMO_Cause_ leaves, LeafCauseDeathLines, the ability..death keys and Tags.MmoCauseAncestor are gone. Each ability's Cause or BaseDamage key names its school's type, so a kill reads that type's death line: Arcane, Void and Life carry their own, Poison keeps the game's, Bludgeoning (Ground Slam, Bull Rush, Sunder) keeps its own, and Update 7's other types take Elemental's or Physical's through Parent (the only field that inherits that way). Vortex Pull (was Arcane) and Wind Dancer (was Lightning) deal Wind.
•     Retired ids: every MMO_Cause_, Seasons of Orbis's Hallows_Eve_Lantern_Burst and Kweebec Nightmare's four KweebecNightmare_* types. An owner's xp-maps.json cause: key naming one matches nothing (the shipped Artillery keys move to tag:), and a pack's native damage node, projectile or resistance keying one fails to load, as any unknown damage type id does (an MMO damage step's Cause naming one falls back to Physical, and AbilityValidator flags it). The audit findings that watched the generated leaves, NATIVE_DAMAGE_CAUSE_UNBRIDGED and SCHOOL_RESIST_LEAF_HOLE, retire with them.
•     DamageSchools.SCHOOL_IDS reads Physical, Fire, Ice, Lightning, Water, Wind, Earth, Poison, Arcane, Void, Life, with Crush among the Physical sub-types. Wind and Earth ship MMO_SchoolResist_ stat files (their damage bonuses are CommonLib's DamageBonus_Wind and _Earth, below), and item enhancement's roll pool follows the roster.
•     DamageSchools.displayColor reads DamageCause.resolveDamageTextColor through the type's chain; FALLBACK_COLOR is only for a type that is not loaded.
•     Hit tags: a damage node can carry native Tags, read back through CommonLib's damage/HitTags. An XP map's tag: key (CombatWeaponUtil.TAG_KEY_PREFIX) is checked before cause: keys, so a thrown bomb that deals Fire still pays Artillery (Hallows_Eve.json's tag:Hallows_Eve_Lantern_Bomb); an entity effect's own native Tags count on each tick of its damage over time too (CommonLib 2.3.0's HitTags, zc 7758a2d27), so a bomb's burn pays the same row, and the native-chain abilities' damage nodes carry an MmoAbility tag (AbilityCatalog.ABILITY_HIT_TAG, read by abilityIdForHit, which replaces abilityIdForCause) that ties the hit back to its ability for XP, per-ability damage channels and conditional damage, which retiring the per-ability types had given up. HitTagValidator (domain hit_tag) reports in /mmoconfig validate an xp-map tag: key no loaded interaction declares (UNKNOWN_HIT_TAG, info, so a server without Kweebec Nightmare or Seasons of Orbis sees no warning for the shipped Artillery rows) and an MmoAbility tag naming no loaded ability (UNKNOWN_ABILITY_TAG, a warning); never an error, since the mod dealing the hit may not be installed.
•     Tests: ShippedDamageTypeIdsTest (every type a shipped asset keys on is an Update 7 type or one of CommonLib's three, since an unknown id drops the mod at boot), DamageSchoolsRosterTest. The generator's and the leaf lines' tests go with them, as do AbilityCatalogTest, DamageCauseDeathLineTest and an ItemEnhanceRollTest method; NativeDamageCauseResourceCrossCheckTest, CombatWeaponUtilCauseRoutingTest and AuthoredStatTypeDecodeTest shrink to the types and keys that remain.
• Resistances, school bonuses and auras on native mechanisms.
•     One resist path: a SCHOOL_RESIST tree reward writes MMO_SchoolResist_ through the tree's stat substrate, as gear and mastery do, and SchoolResistReconciler alone mirrors that stat into native resistance effects, through CommonLib's new RuntimeEffectGrid. ResistEffectRegistrar and its per-node MMO_Resist_* effects retire; any left on a player are swept at ready.
•     School damage bonuses are CommonLib's DamageBonus_ and DamageBonusFlat_. Mastery's school nodes and /mmoitemenhance write them, a Physical bonus landing on DamageBonus_Physical and _Projectile alike so it still covers arrows. The 22 MMO_Bonus_ and MMO_BonusFlat_ stat assets are removed, with no grace version: CommonLib's StatAliases maps each to its successors, so an item enhanced before reads its bonus through StackStats under the new ids and stores them on its next stamp, and their itemTooltip.stats.* lines stay in client.lang for the tooltips those items saved. A third party's native StatModifiers naming an old id stop counting; an MmoChangeStat interaction naming one without a duration changes the successors (a timed one is not aliased: its effect still names the old id). SchoolBonusStats replaces SchoolBonusSources and gates CommonLib's per-type step with the world's combat-bonus rule (TypedDamageBonuses.installAttackerGate). The hit tooltip, line colours and the stat-channel audit read the new ids. Tests that pinned the old ids or a weapon roll's one-to-three entry count go. CombatDamageEventSystem orders itself before CommonLib's TypedDamageBonusSystem, so a school bonus now multiplies with the global and per-skill bonus after armor instead of adding into the HitDamage-clamped sum, with no cap. A damage-over-time or zone tick gets the school bonus from item enhancements too (HitDamageBonus.schoolTermsFor).
•     Buff auras: MmoBuffAura applies a native timed OutgoingDamage effect (AuraOutgoingEffects, ids MMO_AuraOutgoing_*) that raises every hit for the aura's duration, each aura's bonus retuned to match. ability.summary.mmobuffaura.value gives way to ability.summary.mmobuffaura.every_hit.
•     Clamps as safety rails: every other shipped ModifierClamps default Max and MaxTotalPercent doubles (every Min and MinTotalPercent stays), DefenseReduction rises from 0.58 to 0.8 and SchoolResist from 0.3 to 0.8, and CritChance is retired (a chance past 1.0 already crits every hit). An owner's ability-clamps.json keeps applying; an override of CritChance now does nothing. StatCeilings.usable counts defense picks for Power Level's StatRewards pillar up to the new 0.8, so a defense build past 58% now scores a higher Power Level, which mob scaling reads. ui.clamps.name.critchance and ui.clamps.about.critchance are gone, and ui.clamps.about.defensereduction and .schoolresist call those caps safety rails, not balance settings. AbilityValidator's absurd-cooldown and absurd-cost warnings sit at the CooldownMs and Cost clamps' own Max (20 minutes, 200000).
•     Tests: CritChanceClampAssetTest, ResistEffectReconcileTest and SchoolResistParseTest go with what they tested; StatCeilingsTest and SchoolResistReconcilerTest drop the cases the old mechanisms needed, and BodyMigrationFidelityTest drops dxPassBody_isSemanticallyEquivalentToPreDxPassDigest and everyNonExcludedLeafValueSurvivesIntoTheEmittedBody.
• A per-hit XP row matches whatever its case. A tag: or cause: row spelt differently from the hit only in case was routed but paid nothing (a cause: row already did in 1.7.0) and pays now: the hit pays through the matched row's own key (CombatWeaponUtil.routingKey, the row the gate found), since SkillService.bestTriggerMatch matches case-sensitively. NativeChainAudit.probe and its Probe record, with no caller left, are gone.
• The quest audit stays quiet about what the mod gate refused. ValidationChecks gains achievementKnownOrModGateRefused and npcKnownOrModGateRefused beside the quest one, and QuestValidator reads its achievement requirements, its four giver checks and the probe it hands CommonLib's quest audit through them, so a quest naming an achievement or a character whose file the mod gate refused reports nothing, while an id nobody authored still warns.
• CodecDocumentationMarkdownTest keeps its guard. 0.7.0's Documentation.stripMarkdown follows CommonMark and never throws, which left the test's four fixtures failing and its source scans passing vacuously. The test carries its own copy of the 0.6.8 stripper's balance rule (emphasisUnbalanced, checked against that stripper on every fixture and two million random strings), plus two fixtures for runs longer than one.
• Who owns E and R against Update 7's runes. AbilityInputOverrides.TRIGGER_ROOTS gains Ability4 to MMO_Trigger_Ability4 and Pick to MMO_Trigger_Pick (each a crouch Condition with NativeInput {Defer, Fallback}).
•     Claims come from the pure KeyOwnership.claims(...): the free keys a bound slot uses always (Pick never in Creative, re-run on ChangeGameModeEvent by AbilityInputGameModeSystem), and Ability1-3 only in stance mode's MMO stance, so a slotted rune and the weapon signature are natively predicted everywhere else.
•     AbilityInteractionInjector writes only Ability1 into item maps. 0.7.0's InteractionContext.forInteraction sends Ability2/Ability3 with a main-hand item to the abilities section, so an item's own row for them runs only with an empty main hand and an offhand item. Without the MMO's rows that case is the game's, and a slot on E or R reaches its player through the claim.
•     MmoCastAbility resolves the displaced move through DisplacedRoot: the slotted rune's Cast root on the abilities section, the default unarmed map for an empty hand, else the item's own map. Defer never yields to a rune (its cast opens with UseAbilityCost and no cost map, which NativeInputGate reads as not ready). A Trigger on ABILITY_1-3 casts nothing outside the MMO stance, the injected Ability1 row and pack roots included.
•     Tests: TriggerKeyFormsTest, TriggerRootsTest, AbilityInteractionInjectorTest, KeyOwnershipTest, DisplacedRootTest, AbilityInputMigrationTest, InputChoiceTest.
• New: stance mode. Two new SkillComponent keys, AbilityStanceMode and AbilityRuneStance, read through the one seam AbilityStance.of(skills).
•     Plain H with stance mode on flips the stance (AbilityStanceService.flip, after the Defer check, so a crossbow still reloads), and stance mode always claims Ability4 for it.
•     Turning stance mode on or off saves at once (markDirtyAndFlush). A flip only marks the save (markDirty): the database backend writes it at its next sweep or at logout.
•     Turning stance mode on moves a slot on plain H to the first of E, R or Q that no slot uses and starts in the MMO stance. Turning it off moves every slot on a stance key to its free-key default, or to the first free key no slot uses when another slot holds that default (StanceMoves).
•     The cooldown HUD's fourth pip is the stance badge (StanceBadge).
•     Tests: StanceMovesTest, AbilityStanceTest, StanceSurfacesTest.
• New: XP boosts on CommonLib's buff bar. BoostBootstrap registers BoostBuffSource with CommonLib's TimedBuffs: every live timed boost XpBoostService.getActiveBoosts lists (the list the Boosts page reads), keyed mmoskilltree:boost:, a server-wide boost on the SERVER pool and a personal one on PERSONAL, ending at its start plus its duration. XpBoostService calls TimedBuffs.refreshAllOnline() after each activation (template, admin, token) and both clears; CommonLib re-syncs on its own at every ready and respawn, and a boost that runs out takes its tile with it. Standing BoostRules stay off the bar.
•     A boost token can name its own tile. Mmo_Boost_Token declares an optional Effect param, and its command line reads mmoboost give --args={player}|{Skill}|{Multiplier}|{DurationMinutes}|personal|{Effect}; /mmoboost give takes the effect id as a sixth value (pipe form only, since ids carry underscores), read through BoostGiveLine.effect, so BoostGiveLine.BoostGive gains effect. BoostToken and ActiveBoost carry it (saved as effect only when set, so a 1.7.0 jar reads either), and BoostBuffSource shows it, or the scope's default tile when the id is not loaded (named once in the log). Boost templates and XP token items keep the default tile.
• ItemLineage moves into CommonLib. item/ItemLineage is gone; ItemEnhanceCommand, ActionRequirementService and CombatWeaponUtil import ZiggfreedCommon 2.3.0's inventory/ItemLineage (the same walk, moved unchanged), and the ActionRequirementsDefaults and ItemEnhanceRoll javadocs name it. ItemLineageTest keeps the classifier cases (action requirements, the enhance roll's gathering skill) over the library's lineage; the walk's own cases moved with the class.
• New: the content audit folds five more CommonLib audits. ContentAudit (/mmoconfig validate and the boot audit) adds calendar events and their spawns (calendar), titles (title), Almanac pages (almanac), derived factors (factor) and NPC identity overlays (identity), each through its own fold beside the gear-set and reputation ones. The last two audits existed in CommonLib and nothing called them. A factor term is asked of GateFactors.registry(), the vocabulary every requirement here resolves through, so only a term no mod answers reads as UNKNOWN_FACTOR. Test: ContentAuditLibraryDomainsTest.
• Statistics fold into CommonLib's stat store. StatisticsStateMigration runs first in PlayerReadyFlow's player-data pass, right after the hydrate, and folds StatisticsComponent into PlayerStatsComponent (ZiggfreedCommon:Stats) once through its importOnce, claimed mmoskilltree:statistics@1: every key keeps its spelling and adds to what the store holds, swapped and claimed in one step. StatisticsComponent stays registered, attached and decodable and is never written again; database STATISTICS rows are untouched.
•     StatisticsService.handleEvent counts only this mod's own fires, through PlayerStats.add: SPECS lost kill, break, place, craft, pickup, talk, encounter, death and the three station kinds, which CommonLib counts. Damage taken and the sprint and swim distances write through add; accumulatePlaytime is gone (CommonLib counts playtime and deaths); MmoMomentReactions counts nothing, and its encounter, talk and station reactions are gone.
•     Readers take StatisticsComponent.viewOf(StatsView), a detached copy under the same keys: MMOSkillTreeAPI.getStatistics returns that copy (null without a record), so a write to it changes nothing.
•     21 stat files ship under Server/ZiggfreedCommon/Stats (the Skill_Level and Skill_Xp gauges, this mod's own sums, and five Station_* stats CommonLib counts off RPG Stations' moments, _By_Station as TargetAtQualifier), plus the Mmo_Skills section in StatSections. Their names are mmoskilltree.stats.* (new, in all nine languages) or the Statistics book's ui.achievements.stats.*.
• The skill leaderboard retires into Records. LeaderboardDataStore, pages/hub/LeaderboardPage and Pages/LeaderboardPage.ui are gone. SkillGauges publishes Skill_Level and Skill_Xp through PlayerStats.gauge (a line per skill, and the totals): at ready, on an XP award (10 s throttle, at once on a level-up), on an admin XP edit and at disconnect. LeaderboardCacheImport publishes leaderboard-cache.json at start(), after the sections load, once: StatBoard.importOnce claims mmoskilltree:leaderboard-cache@1 in the board's own imports, saved with the rows, so a restart never imports again and an offline player's later level is never set back. The file stays.
•     Mmo_Leaderboard (still behind the owner's switch), /mmoleaderboard and the class hub tile open RecordsDestinations.RECORDS; a refused open answers the click, and the command says nothing is ranked yet. MmoMenu drops its Leaderboard tab (mmo.leaderboard): CommonLib's own Records tab is on the rail, so the owner's switch (isLeaderboardEnabled) now gates only Mmo_Leaderboard.
•     Pages/LeaderboardRow.ui is gone with the page that drew it.
•     pages/hub/SkillRecordsSplit splits the Skills tab as the retired page did, through CommonLib's StatSectionConfig.split on Mmo_Skills, registered in setup() so the lines LeaderboardCacheImport publishes at start() rank: the first choice is the tab's own columns (ui.leaderboard.filter_total), then GATHERING, COMBAT, CRAFTING and MISC (the old filter_* buttons), each the listable skills of its category (SkillFilterUtil.listableSkillIds, read as Records opens), named by Messages.skillNameMsg. Its columns are Skill_Level (ui.leaderboard.header_level, a category counting only levels past 1, as getSummedTotalLevel does) and Skill_Xp (header_xp), so a tie on level goes to XP; the picker's first entry is ability.bind_page.skill_filter_all. A viewer sees the skills PermissionUtil.canGainSkillXpByName allows (its new PlayerRef form), and a category with none of them is hidden. Both gauges are all-time only, so a category or a skill reads All Time with the period row hidden. No new lang keys.
•     MmoFactorContributions sets no ziggfreedcommon:counter source: CommonLib's store answers it. /mmobulksetxp * queues offline players from PlayerDirectory.knownIds().
•     The Settings tab's Online status card is gone; ShowOnlineStatus stays in the save, read by nothing.
•     Tests: StatisticsStateMigrationTest. LeaderboardDataStoreTest and StationStatisticsTest are deleted, with the cases that named the retired page or card (RailPagesDryTest, PlayerNameTextTest, MmoSettingsTest).
• A per-skill stencil reserves 16 sort positions a skill. CommonAchievementFold.SKILL_SORT_STRIDE goes from 6 to 16, so the Skill Mastery Pack's thirteen-rung Mastery Point ladder (2.1.1) reads skill by skill instead of running into the next skill's rungs. The levelling ladder's six rungs keep their order, and the server-first races at SortOrder 10000 and up still sort last.
• Three dead feedback moments are gone. FeedbackEvent drops BOUNTY_COMPLETE, BOUNTY_REROLL and SHOP_PURCHASE, and FeedbackConfig.loadDefaults their rows: nothing in the plugin fired them once the boards and shops moved to CommonLib. An owner's feedback.json that still names one loads as before (readOverrides skips a key FeedbackEvent.fromString does not know), and SCHEMA_VERSION stays 1.
• Achievements keep a criterion's Targets and Qualifiers. CommonAchievementFold rebuilds every shared-schema criterion as an ObjectiveSpec, and AchievementDefinition.toRuntime hands it back to the engine; both dropped CommonLib 2.3.0's list leaves, so a criterion naming several targets or qualifiers counted any. ObjectiveSpec gains targets beside target and qualifiers beside qualifier (a constructor that omits a list keeps it empty), read by parse and CODEC, written by SharedSchemaJson.objectiveLeaves, carried by fromRuntime, and copied as authored by LegacyQuestConverter for a kind this mod does not produce; toRuntime rewrites each target through a kind alias as it rewrites Target. ObjectiveTextRenderer and MmoObjectiveIcons name the first target when Target is blank (namedTarget()). The owner-file parser (AchievementConfig.parseAchievement and parseCriterion) reads a targets list as it reads qualifiers, carried by the new AchievementDefinition.Builder.targets, so a legacy criterion naming only targets no longer reads a blank target and counts every kill. Tests: CommonAchievementFoldTest.severalTargetsSurviveTheFoldTheRuntimeRebuildAndTheWriter, SharedLayoutExportTest.aLegacyTargetsListReachesItsCriterionAndTheExport.
• Big Game Hunter and Apex Predator name their three bears. Their kill-entity-bear criterion trades Target Bear under CONTAINS, which also took Update 7's Bear_Voidtaken_Tentacle and Bear_Voidtaken_Tentacle_Marker, for Targets Bear_Grizzly, Bear_Polar and Bear_Voidtaken under EXACT. The criterion key is unchanged, so saved progress carries over. With no Target, the definition's summary getTarget() reads blank: only @skill reads it (TemplateArgs.expandMsg), and both files bind @amount alone. Tests: none new.
• New: the Skill Lamp. One item, Mmo_SkillLamp (the desert lantern's model, texture and icon), whose numbers ride the stack's metadata (lamp/SkillLampMeta, key MmoSkillLamp): Amount (XP to each pick), Picks (1 to 10) and Skills (lamp/SkillLampPool: ALL, a category, or a comma list of skill ids, a skill id read before a category as Mmo_Xp reads it). The pool is written in one canonical spelling, so equal lamps stack and different ones never do, and a minted lamp's ItemDisplayMetadata description names its picks, amount and pool (lamp.item.description, lamp.item.description_from).
•     The Mmo_Lamp reward kind is a jar-shipped kind file running mmolamp give {player} {Amount} --picks={Picks} --skills={Skills} (Picks defaults to 1, Skills to ALL), so RewardSpecs.MMO_KINDS holds four kinds and the mod still registers no Java kind. RewardSpecs.refusalReason refuses an Amount under 1, a Picks outside 1 to 10, or a list with a space, an empty or malformed entry, a repeat, or fewer skills than picks; ValidationChecks.checkRewards reports the same for shared-schema quests, contracts and achievements (MALFORMED_LAMP_REWARD, an error) and warns on a listed id the server has no skill for (UNKNOWN_LAMP_SKILL). Its chip reads through the kind file's reward.lamp.{Skills} key for the every-skill lamp, and through MmoChipReading's new Mmo_Lamp arm (reward.lamp.from, naming the category or the skills) for any other pool. The kind file's Hands (Mmo_SkillLamp, CommonLib 2.3.0) puts one lamp in the ask-first room batch (LootRewardKinds.canAddAll), so a lamp Claim waits for bag room like any item reward.
•     /mmolamp give [--picks=N] [--skills=...] (admin or console) hands a lamp over through SkillLampService.give: CommonLib's InventoryGrant (hotbar, then bag), else NativeLootService.spawnAtFeet. An offline player who has connected before gets the same line queued in PendingRewards.
•     Rubbing is mmo_skill_lamp_rub (SkillLampRubInteraction) on the item's Secondary, a one-second charge that opens SkillLampPage ($ZF.@ZigDecoratedFrame, cards from SkillResetCard.ui, CommonLib's ConfirmArm for the two-click confirm). A card is unavailable when its skill is at the player's level cap, gives no XP in this world or is held back by the player's class (SkillLampService.blockOf); the player picks the lamp's Picks distinct skills, or every available one when fewer are. SkillLampService.rub checks the choice again, takes one lamp with the same numbers from the bag, then pays each pick through SkillService.addXpByName, so boosts, class and world rules and level-ups apply. An award that throws stops the payout and is logged, and handBack returns the rubbed lamp when nothing was paid, or a lamp of the same amount and pool for the unpaid picks (a pick whose XP moved before the throw counts as paid, so nothing pays twice). Closing the page takes nothing.
•     Test: SkillLampMetaTest (the metadata codec's round trip).
•     The content: every Mmo_Xp row with Skill ALL on an achievement (45) or an achievement-point milestone (Points_3000 to Points_24000) becomes Mmo_Lamp with Amount 3X and Picks 3; an Mmo_Xp row paying one weapon skill on a kill achievement or kill quest (14), on Combat Master or the damage achievements Hard Hitter, Powerhouse and Force of Nature, becomes Mmo_Lamp with the same Amount, Picks 1 and Skills COMBAT. Defense and Acrobatics rows, boost tokens and titles are unchanged, and criterion keys and ids keep saved progress.
• Claim rewards added to an achievement already earned (CommonLib 2.3.0). AchievementDefinition gains getClaimAddedOn() and Builder.claimAddedOn(LocalDate): CommonAchievementFold reads CommonLib's ClaimAddedOn, toRuntime carries it onto the runtime achievement, AchievementConfig's disabled-meta rebuild keeps it and SharedAchievementWriter writes it back, so a pack achievement this mod folds offers its Claim rows to a player who earned it before they shipped, as one CommonLib folds itself does. AchievementService.claimAchievementRewards checks bag room for AchievementEngine.claimRewardsOwed (what this collect pays) instead of every Claim row, so a collect reopened for added rows is never refused for rows already paid. A reopened achievement reads unclaimed until it is collected, so meanwhile it drops out of the achievements power pillar (BuiltinPowerPillars.achievementsContribution counts claimed ones), one Pillars.Achievements.Factor share each. Tests: none new.
• /quest claim collects a bounty whose board is gone. PlayerQuestCommand's claim, one quest or all, asks QuestEngine.canCompleteAt(subject, quest, null) where it read quest.turnInAt() != null, as the quest book's Collect does, so a bounty taken at a board that is taken down or out of season is claimed from chat instead of refused with ui.quest.claim_at_site. Tests: none new.
• The guard bash's knockback and the riposte's stagger are files of their own. MMO_Guard_Bash_Hit and MMO_Parry_Riposte_Hit name MMO_Guard_Bash_Hit_Next and MMO_Parry_Riposte_Hit_Next by id, where each carried its Next inline. An inline Next is registered with the asset store's contained assets, after the guard and parry selectors' inline roots can already compile the hits, so on some boots the server warned "Missing interaction" and an early hit could skip its knockback or stagger until the post-load rebuild; a top-level file is registered in the main batch, before any root compiles. The numbers are unchanged. No test.

Removed

• event/EntityCombatTextSanitizeSystem and its registration (SystemBootstrap.registerCombatTextSanitizeSystem): nothing ships an extra CombatText asset to strip from an entity's UIComponentList any more.
• Server/Entity/UI/MMO_CombatText_Red.json and MMO_CombatText_Gold.json: the crit and level-up colours ride the CombatTextUpdate packet's color; a combat-text.json naming either id reads as its colour (#FF3B3B, #FFD700). critStyle and levelUpStyle take a colour (#RRGGBB), so one naming a pack's own CombatText asset falls back to the default colour with one warning at load (the game's own CombatText reads as white, #FFFFFF), and the crit and level-up text draw at the game's own size (48) where the two assets drew them at 56 and 52. For pack authors: on Update 7 the role builder puts every loaded EntityUIComponent asset on each role-built mob, so a pack that still ships a CombatText asset of its own draws its own extra damage number on every mob; delete it and write a hex colour into critStyle or levelUpStyle instead.
• ColoredCombatTextService.drainRestores(World, Store) and clear(), with the per-viewer UIComponentsUpdate swap and restore queue they drained; showTo and showAbove take a #RRGGBB colour where they took a style asset id.
• FeedbackEvent.combatTextStyle(), replaced by combatTextColor() (a #RRGGBB hex, null for the client's white).
• CombatTextConfig.getStyle(FeedbackEvent), replaced by getColor(FeedbackEvent).
• SkillDisplayUtil.combatTextCrit(SkillComponent), which nothing called.

v1.7.0 developer notes

Learns what RPG Stations 1.1.0 adds for a station that takes things apart: the consumed-piece objective kind, per-station statistics and a Stations section in the statistics. It also audits the library's gear sets and reputations, mirrors its reputation-rank kind, and lets an achievement criterion compare its qualifier by prefix. Beside the stations work it carries the player half of the power-vs-difficulty parity work (the mitigation and healing bounds that make a mob at difficulty N a fair fight for a player at power N, a ceiling on crit chance, and the power retune that anchors an all-L100 build at MaxPower instead of far past it), and a preventive fix ahead of the next Hytale update, which reshapes the floating-combat-text packet. Bonus drops gain a third moment, the hand harvest, so the lucky harvest that was coded in Java becomes a shipped row an owner can retune or switch off. It also ships the jar's half of Hallow's Eve: the skill layer over the seasonal pack, a boost-rule store and the Almanac in the menus. Its menu pages move onto ziggfreed-common's shared menu, its player settings onto the library's Settings tab, and COMPLETE_QUEST to the library's own producer. Its quest and achievement surfaces move onto the library's rebuilt Objective Book and its list-and-page kit: the statistics become a source for the book's Statistics view, the book's side column and the stat detail page retire, and the skill reward ladder and the hub guide's previews are rebuilt on the kit, and the Skill Overview's pinned and tracked panel retires. Built against ZiggfreedCommon 2.2.0 and RPG Stations 1.1.0 (api contract 10).

Breaking changes

• Requires ZiggfreedCommon 2.2.0 or newer. REQUIRED_ZIGGFREED_COMMON and the ziggfreedCommonVersion pin both read 2.2.0; the pin feeds the manifest's ^2.2.0 floor. The qualifier comparison, the gear-set validator and the declared-metadata list below are all 2.2.0's, so the two jars move together.
• The optional RPG Stations range is >=1.1.0 <2.0.0. The old >=0.1.0 <0.3.0 admitted neither RPG Stations 1.0.0, its last public release, nor the 1.1.0 held with this one. This jar compiles against the 1.1.0 api (rpgStationsApiVersion=1.1.0, contract 10); an older RPG Stations falls outside the range, and the MMO then runs stationless while RPG Stations runs standalone. The api artifact is versioned with the mod, not with its contract number (1.0.0 carried contract 9), and the stale "contract N ships as 0.N.0" comment in gradle.properties and the version facts in integration/stations/CLAUDE.md say so now.
• Player mitigation is bounded, and player health regeneration is gated. Three numbers move, all of them player-side ceilings, because parity is impossible without them: ModifierClamps/DefenseReduction.json Max 0.9 to 0.58, ModifierClamps/SchoolResist.json Max 0.9 to 0.3, and skill-tree health regeneration now waits 15 s after the last damage taken. The arithmetic behind it: the MMO's defense cap composes MULTIPLICATIVELY with the engine's own armor percent (0.40 on the top vanilla rung) and, for elemental hits, with school resist, so a capped build kept six percent of an incoming hit and a fully-regenerating one healed 38.6 HP/s through the fight. 0.58 composed with top armor leaves about a quarter of the hit, which is the bound the mob curve is now derived against. An owner who wants the old feel raises Max via ability-clamps.json and lowers mob damage to match; the two are halves of one sum.
•     The regen gate reads the ENGINE's own DamageDataComponent.getLastDamageTime() through TimeResource, the same field and clock its NoDamageTaken condition tests for NPC regeneration, so a player and a mob answer "am I in combat" identically and any damage source counts. Unreadable state answers false, so a missing component leaves regeneration exactly as before. Mana regeneration is deliberately NOT gated - mana is what an ability spends, so gating it would stop a caster acting rather than stop them out-sustaining a mob.
• Every server's power numbers change: PowerLevel/Default.json is retuned at source so a realistic all-20-skills-L100 character lands at MaxPower 200 instead of 295 (tank) or 369 (damage), and MaxPower itself stays 200. Power is recomputed live from a transient per-component cache and is persisted nowhere, so there is NO data migration: the first read after the update simply returns the new number, and a companion mod that scales mobs to power sees it at once. Four corrections, in order, each removing one measured distortion, and only the last one fitted:

1. The StatRewards pillar counts a saturated stat only up to the ceiling gameplay enforces on it (reward/StatCeilings.usable, the one per-stat ceiling table the pillar and the stat pages share): BLOCK_PCT up to the live DefenseReduction clamp (CombatDamageEventSystem.defenseReductionCeiling()), CRIT_PCT up to the new CritChance clamp (SkillTreeService.criticalChanceCeiling()), FALL_PCT up to FULL_FALL_REDUCTION (1.0, the semantic bound: a full reduction is no damage). The pillar read those ceilings from the same seams the hit uses, so retuning a clamp retunes what power pays for it. The raw sums it was paying full price for reached 3.58 defense (6.2x the usable 0.58), 3.05 (tank) to 11.12 (damage) crit depending on the pick order, and 1.65 fall. The gameplay clamps themselves are untouched and not applied twice.

2. Each scope-bearing factor is divided by its measured over-count ratio. sumAllScopesTreeOnly sums every weapon and skill scope at once, but a hit resolves the global channel plus ONE active skill's channel, so the pillar counted several times what any single moment can use. Every ratio is measured on the LOADED trees through the real claim path, as the all-scopes sum over the most ONE moment can resolve (the global channel plus the one skill's own channel, maxed over the roster that moment is attributed to: the combat roster for a hit, every skill for an XP award or a luck roll), each key on a build that picks it first: DAMAGE_PCT 4.2x (2.12 over 0.50, Axes) and CRIT_PCT 4.9x (11.12 over 2.29, Daggers) on the damage build, FLAT_DAMAGE 4.0x (432 over 108, Staves) there too; LIFESTEAL_PCT 2.4x (0.80 over 0.34), COMBO_PCT 7.0x (1.26 over 0.18), FLAT_LIFESTEAL 2.9x (49 over 17) and FLAT_COMBO 4.6x (123 over 27) on a build that picks lifesteal and combo first, since neither reference build ever picks them; XP_BOOST_PCT 14.7x (11.59 over 0.79, Crafting) on a build that picks XP boost first and LUCK_PCT 4.3x (5.37 over 1.24, Woodcutting) on one that picks luck first. The all-scopes READ stays (a Swords-scoped pick earns the same power as a universal one), so the correction lives in the factor. STAT_HEALTH / STAT_MANA / STAT_STAMINA / BLOCK_PCT / FALL_PCT / HEALTH_REGEN / MANA_REGEN are authored without a scope and are not divided.

3. The MaxHealth pillar is wired in and health is scored once. Modes.Balanced gains MaxHealth: 0.5 (the same weight as StatRewards: the health half weighs what the reward half weighs; CombatOnly 0.25 and Completionist 0.4 follow the same ratio), and STAT_HEALTH drops to 0.0 so a health pick is not paid for as a reward AND as live health. The pillar now counts health ABOVE BaseHealth (((max - BaseHealth) / BaseHealth) * Factor, Factor 9.0), so a fresh 100 HP character earns nothing from it and MinPower 1 still holds; class, gear and potion health count too, once, as they should.

4. What remains is scaled by 2.0 so both reference builds land on 200: post-correction factors STAT_MANA / STAT_STAMINA 0.09, DAMAGE_PCT 14.15, CRIT_PCT 9.27, LIFESTEAL_PCT 19.12, COMBO_PCT 4.29, BLOCK_PCT 30, FALL_PCT 6, LUCK_PCT 3.46, XP_BOOST_PCT 1.02, FLAT_DAMAGE 0.15, FLAT_LIFESTEAL 0.31, FLAT_COMBO 0.13, HEALTH_REGEN / MANA_REGEN 15.

•     Result, measured through the real PowerLevelService.computeWith fold over components built through the real claim path (every skill at the level named, one pick set per tier by the build's priority, then ability unlocks, then authored order), and stated as the CLAMPED number every consumer sees: fresh character 1; all-20 at L20 32 (tank) / 30 (damage), L30 52 / 46, L50 98 / 89, L80 165 / 161, L100 200 / 200 (the unclamped sums land at 204.2 and 201.7, so both reference builds sit on MaxPower, 2.5 apart; before, they sat at 295 to 369 and were held to the same 200). A three-skill specialist at L100 reads 92 (Swords + Defense + Acrobatics, tank picks) to 86 (three weapons, damage picks). Said plainly: a clamped scalar compresses the top of the range by construction, so the broad build read 200 before and reads 200 after, and the specialist did NOT rise against it. A crit-heavy three-weapon specialist read about 134 before, because 3.2 of summed crit chance was paid for at 22.5 a point; it reads 86 now. What the retune changes is what the top of the ladder is made of (a saturated stat and a scope over-count no longer carry it) and the spread between two L100 builds (2.5 where it was 74), not the specialist's share of the ceiling. Two figures in the plan's first distortion table came from a text parse of the Java tree defaults that mis-typed 23 flat-damage rewards as parry rewards: a FLAT_DAMAGE raw of 347 (the loaded trees sum to 267 tank / 432 damage at L100) and a CRIT_PCT raw of 10.22 (11.12 loaded). Every factor above is derived from a ratio measured on the loaded trees, not from that parse; the four percent ratios first taken from it moved when re-measured (DAMAGE_PCT 7.1x parsed to 4.2x loaded, CRIT_PCT 5.5x to 4.9x, XP_BOOST_PCT 13.2x to 14.7x, LUCK_PCT 4.4x to 4.3x, the last two because the measuring build now picks the key first rather than the reference build's leftovers), and the uniform scale stayed 2.0 because the re-derived pair still lands inside 190 to 205. XP_BOOST_PCT, 17.8% of the tank's stat pillar before for a stat that is not combat power, is under 3% of total power after.
•     Owner-facing: a power-level.json that re-authors a factor keeps working leaf by leaf, but its numbers were tuned against the old raw sums and want a second look; PowerLevel/Default.json carries a $Comment explaining every pillar and the health rule.
• Critical-hit chance is capped, at 1.0 as shipped, by a new reserved ModifierClamps/CritChance.json. The hit roll is one random.nextDouble() < critChance, so any chance at or past 1.0 was already a guaranteed crit and every point above it inert; the tree could sum to 3.05 (tank) or 11.12 (damage) across all scopes and up to 2.29 on a single weapon. The ceiling is SkillTreeService.criticalChanceCeiling() (fail-closed to 1.0 before the asset stores load): the hit roll applies it in resolveCriticalChance, whose one caller is CombatDamageEventSystem, and the Stats page and the power pillar read the ceiling itself through reward/StatCeilings against the summed chance, so what the three share is the ceiling, not one method; the number lives in the asset, never in Java, and an owner lowers it in ability-clamps.json under CritChance. The Stats page's crit label paints through the same capped-total renderer as the stat-sources page and the held-item panel (the summed chance, with the cap beside it once reached) and adds a hint line (ui.viewxp.buffs_hint_crit_capped, nine locales) so a player learns a further crit pick buys nothing.

Features

• Adds the STATION_INPUT objective kind. One stack a station consumed: target = the item id, qualifier = the station id, amount = the count, counted once when the consumption commits and never for a refunded input; an unattended settle has no worker and credits nobody. RPG Stations produces it and ships its kind file (ObjectiveKinds/RpgStations/Station_Input.json, not value-based, producible); this jar carries the ObjectiveType mirror so the quest and achievement folds accept it, joins it to the item-name family beside STATION_OUTPUT (TargetNameResolver, the countable-target set) and ships objective.text.station_input / .any in en-US. The MMO never listens to StationInputConsumedEvent: the moment reaches the statistics through the shared progression dispatch like the other two station kinds, so a listener would count every piece twice.
• Adds the USE_ITEM objective kind mirror. Ziggfreed Common 2.2.0 seeds USE_ITEM as a built-in kind (target = the item id, qualifier = how it was used, such as Throw, Crack or Costume, amount 1 per use), and a pack's item fires it through the library's ZigCreditProgress interaction step. This jar carries the ObjectiveType row (accumulating, quest-producible), so the quest and achievement folds keep a USE_ITEM step instead of dropping it and the content validator accepts one, and joins it to the item-name family in TargetNameResolver, so a step names the item by the name the item gives itself. The sentence is the shared vocabulary's objective.use_item / .any; this jar ships no key of its own and fires nothing.
• LOOT_RECEIVED joins ObjectiveType (quest-producible, accumulating; TargetNameResolver names its target as an item), so this mod's folds and validator keep a step on an item a reward hands over instead of dropping it; ziggfreed-common's ZigLootReceivedProducer fires it.
• The leaderboard paints a player's name through ziggfreed-common's PlayerDisplayNames (pages/render/PlayerNameText.of(playerId, storedName), on #PlayerName.TextSpans and #YourName.TextSpans), so a player's shown title appears beside their name on every row, online or not, a player hiding their status included (zc's ActiveTitles keeps and persists the choice): a decoration never tells a viewer who is online. Only a row with no player id reads its stored name. Test: PlayerNameTextTest.
• Adds station input statistics, and both station stack tallies break down per station. STATION_INPUT files Station_Inputs (total, and per item exactly like Station_Items). STATION_OUTPUT and STATION_INPUT also file per station off the moment's qualifier, under Station_Items_By_Station and Station_Inputs_By_Station, each entry named @ (StatisticsComponent.atStation); a moment with no station named files no station line, and a per-station count is the sum of that station's entries (StatisticsComponent.sumAtStations, ids matched without regard to case). Three persisted fields are appended to the statistics codec, PerStationInputs, PerStationInputsByStation and PerStationItemsByStation; a save written before them decodes them empty, and the golden StatisticsBlobCompatTest bytes are unchanged and now pin that. The counting rule lives in one store-free seam, StatisticsService.file, which StationStatisticsTest drives.
• Adds a Stations section to the statistics (the book's Statistics view, through MmoStatistics below) with two rows: Pieces Unmade (every stack consumed at Disenchanting_Table or Disenchanting_Table_Greater) and Essence Drawn (Ingredient_Life_Essence, Ingredient_Void_Essence and Ingredient_Voidheart handed over at those two tables, so the Sawmill's Essence of Life never counts). Both are sums across two tables rather than one raw breakdown (statistics/StationStatRows). The section shows only with RPG Stations installed and at least one of the two tables loaded (StationStatRows.sectionShown, over the bridge's new RpgStationsBridge.loadedStationIds(), ids matched without regard to case); a server without them shows no Stations section. Three new keys, ui.achievements.stats.stations, .pieces_unmade and .essence_drawn, in en-US.
• Achievement criteria carry QualifierMatchMode. ZiggfreedCommon 2.2.0 gives an objective a comparison for its qualifier beside the target's (EXACT / CONTAINS / PREFIX, unauthored = EXACT, so every shipped file keeps its meaning). This jar rebuilds every achievement criterion twice (the shared fold into ObjectiveSpec, then AchievementDefinition.toRuntime back into a fresh engine objective), so the leaf rides both trips: ObjectiveSpec gains the component (its constructors without it default to EXACT), parse, the structured CODEC and fromRuntime read it, SharedSchemaJson.objectiveLeaves writes it when it is not EXACT, the legacy quest converter knows the key, and the legacy achievements/ owner files read qualifierMatchMode too. A rung authored Qualifier Disenchanting_Table with PREFIX counts both tables, exactly as the library would (CommonAchievementFoldTest). Quest steps run on the library's quest engine directly and needed no change.
• /mmoconfig validate audits gear sets. ContentAudit registers the library's gear_set domain over GearSetValidator.audit(), so a set naming an item nothing ships or a tier with no condition reads beside every other content domain.
• /mmoconfig validate audits reputations. ContentAudit folds ziggfreed-common's reputation validator: it registers the library's reputation domain over ReputationValidator.audit(), beside gear_set, so a companion naming a group nothing ships, a native group with no NPCGroups key or a ladder of fewer than two ranks reads in the MMO's audit and its boot summary. The library also logs the validator's errors once at boot on its own, for servers without this mod.
• Declares the ability-mod record safe to destroy with its item. A consuming station refuses a stack carrying a metadata key nobody has declared; the item domain's new setup step (item/ItemBootstrap) declares MmoAbilityMods into the library's server-wide list of metadata keys that may go with their item (DisposableItemMetadata), so a station's fallback routes can unmake an enhanced piece that has no salvage recipe. The XP token's record is deliberately left undeclared: consuming a token anywhere but its own redeem path would destroy the XP it carries.
• Adds a Modifier Clamps page to the admin hub (pages/admin/ModifierClampsPage, the Modifier Clamps tile beside Power Level). The ceilings that decide fights (DefenseReduction, SchoolResist, CritChance, HitDamage's percent stack) and every other ModifierClamps asset had no UI: an owner hand-edited mods/mmoskilltree/ability-clamps.json and ran /mmoconfig reload. The page lists every clamp the ParamClampTable fold actually holds (a pack's or an owner-declared one included, never a hardcoded roster), reserved combat ceilings first, each under a sentence saying what it bounds in game; the three fight-deciding ones bind their LIVE ceiling as typed numbers, so a defense cap of 0.58 reads as "leaves 42% of an elemental hit", with the sentence adding in words that a physical hit lands lighter still once worn armor has taken its own cut (the armor figure is game data the page does not carry, so it quotes no number for it). Each of the four axes (Min / Max / MinTotalPercent / MaxTotalPercent) is one owner leaf with Default (the asset layer) / Current (what a hit is bounded by) / Edit / Reset, written through AbilityClampOverridesConfig.setOwnerLeaf and cleared through clearOwnerLeaf, so an untouched axis stays absent from the file and keeps inheriting the jar / pack value. A save re-folds the owner layer at once and bumps the clamp table's generation, one term of the power memo's epoch, so every player's cached power recomputes on its next read (AbilityClampOwnerLeafTest proves the write, the un-merge, the partial file, the owner-declared clamp and the epoch move). Fifty-eight ui.clamps.* lines in nine locales.
• The Power Level page edits the StatRewards.Factors map. The sixteen factors the retune above moved were the one section the page left file-authored. They are a MAP, not a fixed leaf list, so the rows are the StatKey roster plus whatever keys the resolved settings carry (a key the jar surfaces later lists itself with no page change), each its own owner leaf Pillars.StatRewards.Factors. with the same per-leaf override and reset as the rest of the page, and because the asset overlay merges the map per entry a cleared key reads the jar / pack value again, never a zero (PowerLevelOwnerLeafTest). A dash is a factor no layer names.
• Adds a third bonus-drop moment, PickupItem, and the lucky hand harvest becomes a shipped row. A row with When.Kind "PickupItem" answers a hand harvest, its Match read against the harvested item's id, and fires after the harvest itself has landed. Like BreakBlock it fires only when the harvest paid skill XP, and with no Chance it is as likely as the player's own summed luck for that skill. A harvest consults only PickupItem rows, never a BreakBlock one, so a released "*" BreakBlock row keeps meaning only broken blocks. The lucky harvest that was coded in Java is now Server/MMOSkillTree/BonusDrops/Mmo_Harvest_Luck.json (PickupItem, Match "*", no Chance, one Moment_Item reward, the note on), with the same odds and the same amount as before: one more of the harvested stack, at the player's summed luck. An owner switches it off with "Mmo_Harvest_Luck": {"Enabled": false} under drops in bonus-drops.json, retunes it per leaf, or adds a narrower PickupItem row for one crop; the most specific pattern wins, so a narrower row that should still hand over a copy writes its own Moment_Item. A PickupItem row's commands take {player} and {item} (the item id the XP matched on). A pack shipping a PickupItem row needs this version: on 1.6.x the moment is unknown, so the row names no moment and /mmoconfig validate reports it as an error.
• Adds Moment_Item to the bonus-drop reward vocabulary. Ziggfreed Common 2.2.0's reward for "another of the stack this moment is about": a true copy of the stack the game handed over (item, amount, durability, quality and metadata), handed over exactly like the harvest. Params.Count is in whole copies, fractional allowed (0.5 is one copy half the time), 1 when unwritten, summed across the pass and resolved once, and at most 64 copies a pass. It pays only in a PickupItem row. The audit names where it cannot pay: PASS_ONLY_REWARD_KIND in a BreakBlock or KillMob row's inline rolls (a warning) and in a quest's or an achievement's rewards (an error, as for every pass-only kind; Ziggfreed Common's own shop and board audits warn about one there), LOOT_MOMENT_COUNT_INVALID for a Count that is not a number above zero, LOOT_MOMENT_COUNT_ABOVE_CEILING for one above 64.
• Adds the mmoskilltree:moment_skill_luck factor. No Param: it reads the player's summed luck for the skill the moment paid XP to, in whole luck points, so {"Factor": "mmoskilltree:moment_skill_luck", "Weight": 1} in a BreakBlock or PickupItem row's Chance is exactly the unwritten default, and a Base or a second term adds to it. Unlike mmoskilltree:station_luck, which reads the same kind of sum as a fraction (0.05 for five points). A kill names no skill, so the factor is unanswered there and its term adds nothing; a named skill's luck stays hytale:stat terms over MMO_Luck and MMO_Luck_.
• Adds a running count to the bonus mob-drop note, on a line of its own. Several kills inside the notification cooldown read as one "Mob Drop! (+N)" (notify.mob_drop.stacked, new, nine locales), batched apart from lucky finds, on a feed line of its own so it never replaces a lucky-find note. Notify.Color has no single default any more: left out, it is #ffff00 on a BreakBlock or PickupItem row and #ffaa00 on a KillMob row.
• Boost rules. New structured store Server/MMOSkillTree/BoostRules/ (asset/type/BoostRuleAsset: Text, Enabled, Skills, Multiplier, Requires), folded defaults < pack < owner by boost/BoostRuleConfig, which keeps the usable rules as one snapshot (no owner file feeds the owner layer yet). XpBoostService.getTotalMultiplierByName adds each live rule to its GLOBAL bucket (stack mode and cap apply), gating through MmoGates.passes over the earner's saved skills; getLiveRules serves the boosts page's active list and the XP page's bar (pages/render/BoostRuleRows, an [EVENT] row per skill). Content-audit domain boost_rule (BoostRuleValidator): ERROR BOOST_RULE_NO_SKILLS, WARN BOOST_RULE_UNKNOWN_SKILL and BOOST_RULE_NO_LIFT, INFO BOOST_RULE_ALWAYS_ON.
• ObjectiveType.CALENDAR_ATTENDED (quest-producible, accumulating) mirrors zc-calendar's kind file; TargetNameResolver.calendarEventNameMsg names the event by its Presentation.TitleKey through zc ContentKeys; objective.text.calendar_attended and .any.
• ObjectiveType.REPUTATION_RANK (quest-producible, accumulating): the MMO's objective vocabulary mirrors ziggfreed-common's REPUTATION_RANK kind file (ObjectiveKinds/Reputation_Rank.json; target = the rank id on the library's ladder, qualifier = the reputation id, amount 1 per credit), which the library's reputation service credits for every rank a player's effective standing has reached and this mod never fires. Without the row the achievement fold drops a rank criterion, Seasons of Orbis's Jack's Confidant among them. objective.text.reputation_rank ("Reach {1}") and .any ("Reach a new rank") match the library's own sentences, so a step reads the same with or without this mod. A step with no TextKey of its own names the rank by its id ("Revered") through TargetNameResolver's default, never a reputation's own rank name; Jack's Confidant words its step itself. Test: ObjectiveKindVocabularyTest.theReputationRankKindFileAgreesWithTheEnum.
• ObjectiveTextRenderer rung 1b. A step's own TextKey that another loaded namespace ships renders as the sentence with the zone wrap and without the qualifier wrap, and compose stops deferring such keys to zc's neutral composer (which wraps the qualifier a second time).
• The Hallow's Eve jar layer (Hallows_Eve/ folders): XpMaps Hallows_Eve (ARTILLERY cause:Hallows_Eve_Lantern_Burst), MobKillXp Mmo_Hallows_Eve, Lootables Mmo_Hallows_Eve_Geode_Crack (ContributesTo Hallows_Eve_Geode_Crack, rolls only, MINING), GearSets Mmo_Hallows_Eve_Hallowed (a second set over the pack's members: both helms, Hallows_Eve_Jack_Helm and Hallows_Eve_Burning_Jack_Helm, and both shields, Hallows_Eve_Jack_Shield and Hallows_Eve_Flaming_Jack_Shield, the same four the pack's own set lists, so any helm with any shield takes its one Armor 1 / Utility 1 tier), Bounties Mmo_Hallows_Eve_Daily_{Artillery,Harvesting,Mining,Crafting} (Hallows_Eve_Daily in the Difficulty band Hallows_Eve_Skill, which only these four carry, so the board's optional Skill slot posts one of them every day; Weight 0.5 each sets the pick among the four; gated Hallows_Eve_Live; Rewards.Claim pays Hallows_Eve_Board_Pay, the skill's XP and two Reputation rewards, collected at the board like every contract's, favor with Hallows_Eve_Old_Jack and Hallows_Eve_Hallowed in the same amounts as the pack's own contracts; the band's badge is board.grade.hallows_eve_skill, "Skill Work", which zc's board labels find under any namespace), RpgStations Extensions Mmo_Hallows_Eve_Carving and Mmo_Hallows_Eve_Carving_Hallowed, BoostRules Mmo_Hallows_Eve_Harvest_Moon (1.25 on HARVESTING and ARTILLERY while calendar_live reads 1 for both Hallows_Eve and Harvest_Moon). Seasons of Orbis (Ziggfreed:SeasonsOfOrbis), the yearly-events pack whose first event is Hallow's Eve, hard-depends on ZiggfreedCommon and RPG Stations and never on this jar, so the carving extensions always find their bench where the pack runs. The pack's quests, contracts and achievements pay this mod's rewards in their own Rewards (Mmo_Xp in the skill the work trains, Mmo_Boost_Token on hallows_eve_the_hallowed and hallows_eve_jacks_guest; the pack's developer notes list each row), so no jar file contributes to Hallows_Eve_{Chain,Lantern,Daily,Board}_Pay: a roll there would pay the same work twice (SeasonsOfOrbisMmoRowsTest, HallowsEveJarContentTest). The four skill dailies' Hallows_Eve_Board_Pay now pays the pack's sweets and items only. On a server without this mod those rows are skipped at payout (one [grant] warning each) and dropped from every reward panel, and zc's boot audits warn UNKNOWN_REWARD_KIND once per row.
• The Almanac in the menus. The hub's Almanac tile and the menu's Almanac tab both follow zc's one rule (AlmanacPages.menuTabVisible); the setting is zc's $MenuTab in mods/ziggfreedcommon/almanac.json, which the admin General page's dropdown edits (config/AlmanacTabSetting: "While a season runs" is OnlyWhileLive: true, "Always hidden" Show: false, "Always shown" the defaults). seasonalTabMode, which no release wrote, is dropped: a leftover key is ignored on load and gone at the next save. The hub tile draws Deco_Scroll, the rail's Almanac picture, and its hint reads AlmanacPages.headline() while a season runs ("Hallow's Eve is on now"), else ui.hub.cta.almanac_hint (MmoHubPage).
• The Seasons statistics are the library's. The book's Statistics view lists the Seasons section zc-almanac contributes (a row per season, a page with its tallies and a button to its Almanac page); this jar ships no Seasons section of its own, and SeasonStats, added earlier in this cycle, is gone with its test.
• The title picker is ziggfreed-common's, opened from the Title card on zc's Settings tab; MmoSettings.register themes it (TitlePickerPages.deps), and its Back returns to Settings.
• MmoBounties.difficultyColor gives the seasonal band its own accent.
• Known on servers without Seasons of Orbis: the content audit lists the set's four members as unknown and the loot audit notes the five contributions, both at INFO in the boot log; /zigcommerce validate lists UNKNOWN_BOARD for the four dailies and /rpgstations validate the two extensions' unknown target.
• Tests: CombatWeaponUtilCauseRoutingTest (two cases), HallowsEveMobKillXpTest, HallowsEveJarContentTest (among its cases, each skill daily posts in the Skill slot and earns favor with Old Jack and the Hallowed), DialogueContentResolutionTest (registers the library's Reputation destination and Grant action as a server does, so Old Jack's favor lines decode), ObjectiveTypeContractTest, TargetNameResolverTest and ObjectiveKindVocabularyTest (one case each or two), MmoBountiesTest, ObjectiveTextRendererContentKeyTest, BoostRuleAssetTest, BoostRuleConfigTest, XpBoostServiceBoostRuleTest, BoostRuleValidatorTest, BoostRuleRowsTest, AlmanacTabSettingTest.
• The menu pages use zc's shared menu. pages/MmoMenu fills ZigMenu.consumer: the Skills section (Overview, the four categories, Class, Boosts, Abilities, Mastery, Leaderboard, Admin), the landing Mmo_Skills, the white-label branding, the theme's palette (ThemeRetint.menuPalette) and its frame paint. Each Skills tab carries a picture (MmoMenu.categoryIcon gives a category its lead skill's icon, Combat Weapon_Sword_Crude). ViewXpPage, BoostPage and AbilityBindPage sit in @ZigMenuFrame with their nav blocks gone; MmoObjectiveBookDeps fills the book's seams and no longer paints a column (see the book entry below); MmoBookRail.ui, SeasonalTab, TabNavHelper and SeasonalTabMode are gone. New destinations Mmo_Class_Hub, Mmo_Leaderboard, Mmo_Settings (opens zc's Settings) and Mmo_Admin (refuses a non-admin); Mmo_Skills takes an optional Category; Mmo_Quest_Log and Mmo_Achievements are aliases of zc's Quest_Log and Achievements.
• Mmo_Quest_Book retired. getting_started and forgot_something hand out Ziggfreed_Objective_Book (their flavor lines name it in every locale); the item and mmo_quest_menu_open stay, so an owned stack opens the menu on Quests.
• Settings is ziggfreed-common's tab. pages/settings/MmoSettings fills ZigSettings.consumer with three cards (Skill notifications, Skill HUD, Online status), shown before the library's own, and fills the library's HUD layout page (admin audience, theme) and title picker (theme); SettingsPage, its document, MmoHudSettings and MmoTitleSettings are gone; Mmo_Settings and the Class hub's tile open zc's Settings, and the Skills section has no Settings tab. player/SettingsStateMigration moves HudKey.QUEST hidden and questNotificationLevel into zc's store once on the ready pass (milestones to Milestones, objectives and quests to Finishes, none to None; a choice already made there wins) and resets the fields. /mmohud quest and MMOSkillTreeAPI.isHudVisible("quest") read and write zc's store, and /mmohud show|hide quest answers cmd.hud.quest_locked and changes nothing while the owner has locked the tracker's Show; MmoQuestSubject no longer answers FeedbackAudience (this mod's Achievement_Unlocked and Quest_Parked toasts carry PlayerLevel); the DB backend's HUD domain holds PlayerSettingsComponent; HudPreferencePersistence becomes PlayerSettingsPersistence.
• No copies of zc's UI. MmoFrames.ui is gone: the framed pages use zc's $ZF.@ZigDecoratedFrame (the same frame), and the bright tooltip the ability and skill-tree cards wear (@MmoTooltipStyle) moves to MmoButtons.ui. MmoButtons.ui drops the unused TurnIn, Neutral button-element, Option and chip-grid styles, and @MmoRowIconGridStyle for zc's @ZigIconGrid24. The admin pages draw zc's @ZigSectionCard and the hub zc's @ZigTile (Common/ZigCards.ui); MmoAdmin.ui keeps only its own styles. UIUtil's dropdown, field and button binders hand the call to zc's SettingsUiUtil.
• The rail pages. The Abilities page's filter, sort and hide chips are zc's rich tabs (@ZigRichRowBtnStyle, SettingsUiUtil.setTabActive), it gains the title row for right-mode branding, and the toolbar labels and the XP page's section title take @ZigSectionHeaderStyle. The XP page's buffs bar fits the menu frame's column with #BuffHint on its own line (RailPagesDryTest sums every fixed row against MenuFrame.BODY_WIDTH). Each page hands its own events to one route, and whatever it leaves unanswered is answered (PageExitsAnsweredTest, RowIndexTest), so a stale or refused click (item rewards while command rewards are off, a mastery link with no track, a boost that just ran out) no longer leaves the client waiting.
• White-label branding on the menu pages. Right mode shows the owner's logo scaled into each title row's AssetImage #BrandingLogo (134 x 50 on XP, Boosts and Abilities; zc's book and Settings size their own), reading the branding pack's Pages/logo.png (MmoMenu.LOGO_ASSET, MmoMenu.paintTitleRow), instead of appending the 105px Pages/branding.ui block, which overflowed every title row; a pack without logo.png shows the slot's blank fallback. The server's name is the title (or the title hides) and the description sits under it, on XP, Boosts, Abilities, the Objective Book and zc's Settings page, which regains the right-mode branding 1.6.2's settings page had. The Leaderboard, which brands its title row in both modes, takes the same scaled logo (MmoMenu.paintTitleRow(cmd)). Left mode still appends branding.ui at the top of the rail. Under a theme, a White Label accent turns the rail's pane see-through (MmoMenu.railPalette, zc's MenuPalette.BACKGROUND), so the accent-tinted frame shows through the rail as it does on the default theme; ThemeRetint.whiteLabelTint is the one reading of the accent for the frame, an external panel and the rail. RailPagesDryTest holds every title-row page, the Leaderboard included, to its four hosts and no page to appending into a title row, and MmoMenuBrandingTest the paint; ui.whitelabel.position_help says where each mode shows the branding, in nine locales.
• Every text size comes from ziggfreed-common's type scale. ZiggfreedCommon 2.2.0 names the family's sizes once, in Common/ZigType.ui: @ZigFontCaption 13 (the floor), @ZigFontSection 13, @ZigFontBody 14, @ZigFontEmphasis 15, @ZigFontHeading 16, @ZigFontSubtitle 18, @ZigFontTitle 20, @ZigFontDisplay 22, @ZigFontDisplayLarge 24, and @ZigFontMicro 11, the one step under the floor; com.ziggfreed.common.ui.ZigType holds the same numbers for Java. Every one of this jar's 95 documents that sets a size imports it ($ZT = "../Common/ZigType.ui"; from Pages/ and Hud/, $ZT = "ZigType.ui"; from Common/) and writes FontSize: $ZT.@ZigFontBody, MinShrinkTextToFitFontSize included, so no player text is drawn under 13 and one edit there resizes the family. Text at 9 to 12 px rises to Caption; row labels, names, buttons and fields on player pages rise to Body; uppercase section and table headers are Section; headings keep their sizes through same-size steps. The admin editors' row labels stay at Caption (13), since their narrow fixed controls would cut at 14. The hero sizes the scale has no step for (17, 26, 28 and 32 on ClassHubPage.ui, MmoHubPage.ui and OnboardingPage.ui) stay numbers. One label in a box too small for 13 takes Micro, up from 10: the cooldown HUD's slot label (MmoSkillTreeAbilityCooldown.ui). The skill card's percent (SkillCard.ui) reads at Caption: its bar row is 17 high with the 8px bar centred in it and the label 40 wide, centred, the room taken from the two gaps around the row, so the header column still holds 54. Rows whose label no longer fit grew where the parent had room (the skill card's XP, meta and hint lines and the reset card's count, 14 to 17 high). The sizes Java sets read ZigType: RewardListRenderer's compact title (BODY, from 13) and the four override editors' empty-list notes (CAPTION, from 12). Three admin pages (BoostTemplateOverridesPage.ui, XpOverridesPage.ui, XpTokenOverridesPage.ui) name MmoAdmin.ui's @AdminRemoveBtnStyle instead of the local copy the sweep had made byte-identical (LookNeutralDryTest). A document importing ZigType.ui needs ZiggfreedCommon 2.2.0, which this jar already requires: on an older library the import does not resolve, and a client fails every Custom UI document's parse, so every player disconnects at load.
• COMPLETE_QUEST is ziggfreed-common's moment. QuestService.fireCompletionHooks no longer dispatches it to either engine (it keeps only the bounty tail) and AchievementService.onQuestComplete is gone. The mod registers QuestService.completionQualifier (a quest's classifyQuestType, a contract's board cadence) through questCompletionQualifier, so the quest achievement chains count exactly as before, once per collected quest. classifyQuestType delegates to QuestCadence.qualifier(), and QuestCompletionCreditTest fails if a dispatch of the kind comes back.
• The statistics and every book entry point ride ziggfreed-common 2.2.0's rebuilt Objective Book. The library's book is a quest journal and an achievement Overview, Browse and Statistics view on its list-and-page kit (its 2.2.0 developer notes). pages/achievement/MmoStatistics is a LedgerSource contributed to LedgerContributions.STATISTICS at setup (from MmoNpcQuestDeps): sections Combat, Gathering, Movement, Leveling, Stations and Playtime read from StatisticsComponent, a row per stat with its top entry as meta (ui.stats.row.most, "Most: {0} x{1, number}", the name through TargetNameResolver) and a typed total, and a page whose lead line is the total ("N in all") and whose breakdown runs up to 100 lines, each with its rank, localized name and count, and the item's picture where the breakdown is items; every number binds through Msg.num or StatValueText. Gone: pages/achievement/MmoBookStatsPanel with MmoBookStatsPanel.ui, StatCategorySection.ui and StatCard.ui; pages/skill/StatDetailPage with StatDetailPage.ui and StatDetailRow.ui; MmoObjectiveBookDeps' side-panel painter and the stat route in its handleExt; the ui.statdetail.* keys and ui.achievements.stats_title where nothing reads them. Quest categories ship as data, Server/ZiggfreedCommon/QuestCategories/MMOSkillTree/{Main,Misc,Daily}.json, each naming the library's own book.quests.category.main, .misc or .daily as its TitleKey, and each achievement category under AchievementCategories/MMOSkillTree/ gains an Accent. AchievementsCommand, QuestPageCommand, MmoQuestMenuOpenInteraction and ClassHubPage open the book through ObjectiveBookPages.open (or a destination) instead of building the page. A section shows once one of its stats is above zero; Blocks Placed and Items Picked Up get their top entry and a breakdown too, and a breakdown cut at 100 lines says so (ui.stats.page.top, "Top {0, number} of {1, number}"). New keys, in all nine locales: ui.stats.row.most, ui.stats.page.caption, ui.stats.page.total, ui.stats.page.top, ui.stats.page.rank and ui.stats.empty. Tests: MmoStatisticsTest (a section shows when it has data, names localized, the breakdown sorted and capped, numbers typed), the category files' decode in the content tests, and MenuRetiredNavTest and MmoStylesRetiredTest for the retired documents.
• The skill reward ladder and the hub guide's previews are built on the library's kit, and the Skill Overview drops its tracked panel. pages/skill/ItemRewardsPage and ItemRewardsPage.ui are a list and a page inside $ZF.@ZigDecoratedFrame with Back: one level per ZigLedgerRow row (state and level; the Next row carries the progress bar the header used to), the chosen level's rewards as the page, and Collect in its action bar taking the whole level (the per-card claim buttons are gone); a reward's authored name colour gives way to one accent per row; a currency or boost reward line keeps its custom name and description as a hover tooltip (a kit DetailLine carries its own tooltip text); the previous and next skill buttons hide on the Total ladder. The pure pages/skill/SkillRewardLadder turns the tiers into rows and a tier into a DetailView with its claim plan (SkillRewardLadderTest); RewardCard.ui, RewardCardGrid.ui and RewardTierSeparator.ui are gone. ViewXpPage has no right-hand pinned and tracked panel (#SidePanel and pages/skill/TrackedPanel are gone): in its 320 px column a tracked quest's compact kit row left its two-line title a few pixels, and the client's label layout threw on it, so a player's quests and pins live in the library's shared Quests and Achievements menus; TrackedAchievementRow.ui is gone, and RailPagesDryTest keeps the kit's compact rows out of the jar's pages. OnboardingPage's previews read through the library's QuestReader and AchievementReader and paint with the kit, so their status words and the hidden-achievement rule are the library's (OnboardingPreviewTest: a preview row equals the reader's row for the same quest or achievement); PreviewMasterDetail.ui and PreviewRow.ui are gone. New keys ui.rewards.ladder.*, in all nine locales; ui.quests.status_* and the retired preview and tracked keys leave all nine locales.

• Titles from this mod's own achievements. The jar ships its first title assets, Server/ZiggfreedCommon/Titles/MMOSkillTree/Mmo_*.json (twelve, each id named after the achievement that pays it, so rewording a title never touches a saved unlock), with title..name, .flavor and .display in mmoskilltree.lang. Each is paid through ziggfreed-common 2.2.0's Title reward kind in the achievement's Rewards.Auto, so the title unlocks with the achievement while its XP and boost rows stay in Claim: the five metas (combat_master, legendary_warrior, gathering_master, legendary_gatherer, movement_master), the five server-firsts below, and deaths_t5 / fall_damage_t5, whose 50,000 Block XP and 2x token give way to the title (both farm off one cliff). The per-skill first (Skill_Level_First, a stencil) pays ONE shared title, Mmo_Skill_Level_First: a title per skill would need a file per skill, and a skill a pack adds would pay one nobody shipped. The picker lists an unearned title for everyone, so the server-first flavors read as feats.
• The server-first achievements are feats. server_first_all_50/75/100, the _100_first stencil and bounty_server_first author zc's Listing.Feat: true (the fold already reads it beside Meta.mmoskilltree.Feat) and Scoring Points: 0, CountsTowardTotal: false, since Feat changes only where a row is listed. Their XP, boost-token and announcement rows are unchanged.
• quest_daily_t1-t5 and quest_weekly_t1-t5 are live again. Meta.mmoskilltree.Feat and LegacySince: "1.4.0" are dropped and Scoring carries the pre-1.4.0 points (daily 10 / 25 / 75 / 175 / 400, weekly 10 / 40 / 150 / 300 / 500), counted. How they count is unchanged: a board contract still qualifies DAILY or WEEKLY by its board's rotation and a Reset: Daily quest DAILY (QuestService.completionQualifier), and progress was filed under the same ids and criterion keys all along. quest_weekly_t1 drops its TextArgs for "Complete your first weekly quest." (and deaths_t1 for "Die for the first time."). QuestAchievementAssetsTest.dailyAndWeeklyAreLiveLadders replaces dailyAndWeeklyAreRetiredFeats.
• The elite-kill rows hide without MMO Mob Scaling. rare_hunter, elite_slayer, legendary_slayer, first_legend_kill and the legendary_warrior meta author a top-level Requires {"Factor": "hytale:mod_installed", "Param": "Ziggfreed:MmoMobScaling", "Min": 1}, which FeatureLift lifts onto the hide axis (MmoFeatures.available answers a Group:Name id through the contributed mod-installed reading). Only the companion puts a rarity on a kill, so without it the rows could never be earned. Their descriptions name its tiers, Rare, Epic and Legendary.
• Two ladders gate on the feature they count. The twelve Quests/Bounties/ rows author Meta.mmoskilltree.Feature ["Bounty"] and the three Spellsword_* rows ["Abilities"], the Spender_* pattern.
• Adds achievement ladders for Excavation and nine weapon skills. Thirty-one new files under Server/ZiggfreedCommon/Achievements/MMOSkillTree/. Gathering/Excavation/Excavation_T1.json to _T4.json copy the Woodcutting ladder (Gathering/Woodcutting/, chain woodcutting) rung for rung with the target swapped: BREAK_BLOCK on Soil, MatchMode CONTAINS, amounts 500 / 5,000 / 25,000 / 100,000, points 10 / 40 / 150 / 300, Claim Mmo_Xp in EXCAVATION 500 / 5,000 / 50,000 / 50,000 plus a 2.5x EXCAVATION Mmo_Boost_Token for 120 minutes on T4, T3 and T4 announced; chain excavation, subcategory excavation. Combat/Weapons/_Xp_T1.json to _T3.json, for DAGGERS, POLEARMS, STAVES, AXES, BLUNT, UNARMED (subcategory melee), ARCHERY, ARTILLERY (ranged) and MAGIC (casting), copy the combat_damage ladder (Combat/Damage/Hard_Hitter, Powerhouse, Force_Of_Nature) with DEAL_DAMAGE swapped for GAIN_XP EXACT on the skill id: amounts 10,000 / 100,000 / 1,000,000, points 15 / 50 / 150, Claim Mmo_Xp 500 / 2,500 / 50,000 plus a 2.0x Mmo_Boost_Token for 60 minutes on T3, T3 announced, every row in the rung's own skill where combat_damage pays SWORDS; chains daggers_xp, polearms_xp, staves_xp, axes_xp, blunt_xp, unarmed_xp, archery_xp, artillery_xp, magic_xp. The criterion is skill XP because a kill or a hit does not say which weapon landed it. Swords keeps combat_kills and combat_damage and gets no XP ladder; Archery's kills_skeleton and Magic's spellsword (ABILITY_CAST) stay beside the new chains. Gathering_Master gains excavation_t3 and Legendary_Gatherer gains excavation_t4 among their MetaChildren (their descriptions name the fifth rung; a meta already earned stays earned); Combat_Master and Legendary_Warrior list no weapon rung. The ladders add 2,435 points to the pool (500 for Excavation, 215 a weapon). No backfill: GAIN_XP accumulates (ObjectiveType.isValueBased is false) and is credited only when SkillService's award path fires ProgressEvents with the XP it actually added, and the engine's selfHeal re-reads only STAT_THRESHOLD criteria, so a rung counts XP earned from 1.7.0 on and existing skill XP never seeds it. Forty-four en-US keys at the end of mmoskilltree.lang, under the block comment naming these ladders: achievement.excavation.desc ("Dig {0} Soil blocks."), achievement.excavation_t1-t4.title, achievement.announce.excavation_t3.title and _t4.title, the shared achievement.skill_xp.desc ("Earn {1} {0} XP.", {0} the skill's name off @skill, {1} the amount), and per weapon achievement._xp_t1-t3.title and achievement.announce._xp_t3.title; plus achievement.category.gathering.excavation beside its siblings, and AchievementCategories/MMOSkillTree/Gathering.json lists excavation after woodcutting. No test names the new files and none pins the shipped achievement count; the tests that walk every shipped achievement cover them: NewShapeContentCorpusTest (everyAuthoredAchievementDecodesAndFolds, noTwoAchievementFilesLandOnOneId), CommonAchievementFoldTest (aFileNameIsTheAchievementId, noTwoAchievementFilesShareAName, criteriaRenderInAuthoredOrderAndEveryNonCapstoneHasSome), DefaultContentLocalizationTest (everyDefaultAchievementResolvesTitleAndDesc, everyDefaultObjectiveAndCriterionRendersLocalized, shippedAchievementAssetsSayTextWithKeysOnly), ShippedCategoryPresentationTest.everySubcategoryThisModNamesHasANameKey and ShippedAchievementContentTest.everyShippedAchievementCategoryHasAPresentationAsset.
• The Temple's Due asks 75 essence and its table pays for it. Quests/MMOSkillTree/Temple/Temple_Tribute.json offer_essence Amount 50 to 75 (the fibre and kill steps are unchanged). Lootables/Mmo_Temple_Offering.json: the guaranteed essence moves from 6-9 to 8-12; Iron Ingots (20%, 2-3) and a Greater Essence of Life (4%) join the Copper Ingots (35%), the boost (8%) and the Warden's Longsword (2%); a Pool draws one of ten vanilla Eternal seed bags on every claim, weighted 3 / 2 / 1 toward the cheaper crops; and a 1% roll, cued Rare_Find, pays the new Lootables/Mmo_Temple_Relic.json, a one-pick Pool over the four Armor_Steel_Ancient_* pieces (Rare, item level 30, no working recipe on 0.6.8, otherwise dropped by Zone 4's burnt skeletons). Every id was checked against the installed 0.6.8 Assets.zip. The quest's Lootable row authors NameKey reward.lootable.temple_offering ("Temple Offering"), which zc's reward chips read in place of the generic "Loot Bundle", and both files' comments stop claiming the table returns more essence than the tribute takes.
• Six quest steps word themselves. objective.text.quest.kill_boars, .kill_trorks (Trork Ground and The Watch Below), .mine_stone, .chop_logs and .clear_rubble are step TextKeys, so the steps read plural instead of the singular role or block name the renderer prettifies.

Fixed

• A mastery card's costs drew over the rows under them. MasteryNodeCard.ui is 384x448 (was 332, and MasteryOrDivider.ui's cell follows): #NodeBody takes its content's height with a flex spacer under it, #CostRow is a Top column, #NodeLockReasons sizes to its lines and #ButtonRow shows only beside a visible BUY, REFUND or CONTRIBUTE, where before a flex body with fixed rows below let three or more 200 px chips, centred by LeftCenterWrap, spill over #NodeStatus and the lock reasons. MasteryPage widens the card's chips to the body's 344 px through CostChipRenderer.setAnchor (the confirm panel keeps 200, its #ConfirmCostRow now LeftWrap), and ui.mastery.contribute_progress takes the amount line as {1}. CostRenderer.currencyAmountMsg returns ZiggfreedCommon's CurrencyText.amountOf, so a wallet that ships currency..amount (the mastery pack's Mastery Points, the bounty pack's Bounty Token) reads in its plural on every MMO price line; an unknown id keeps the raw fallback.
• The temple guide's mastery pointer could name a trainer nobody ships. Mmo_Hub_Intro's temple_pointers mastery option gains the ziggfreedcommon:quest_known meet_the_mastery_trainer condition the sawyer option already carried: a QuestState NOT_STARTED cannot tell an untaken quest from an absent one.
• The statistics' distances read in blocks. MmoStatistics binds ui.achievements.stats.distance_blocks ({0, number} blocks) for every distance, where it switched to distance_km past a thousand; the sprint and swim achievements ask in blocks too. distance_km and distance_m leave en-US, and the other eight locales still carry them, unread.
• Ten buttons clicked silently. Their TextButtonStyles carried no Sounds leaf, in 1.6.2 as before it: RewardCard.ui's @ClaimButtonStyle (an item reward's Claim), SkillCard.ui's @TreeButtonStyle and @RewardsButtonStyle (a skill card's Skill Tree and Items), SkillResetCard.ui's @SelectButtonStyle (the skill reset page's Select), AbilityCard.ui's @CardSelectButtonStyle, @CardSelectButtonDisabledStyle and @CardMasteryButtonStyle (an ability card's Select and Mastery), AbilitySlotRow.ui's @ChangeButtonStyle and @UnbindButtonStyle (the Abilities page's Change and Unbind), BoostRow.ui's @ActivateButtonStyle (the Boosts page's Activate; the document now imports Common.ui as $C) and HeldItemStatPanel.ui's @HeldStatSourcesBtnStyle (the held-item panel's Stat Sources). Each names vanilla's $C.@ButtonSounds (the four card styles with the type scale, the ability card's three in an earlier UI cleanup this cycle, the last four after it), and the Java that repaints those buttons sets colours and text only, never a whole Style, so the sound holds through every repaint. RewardCard.ui itself goes with the skill reward ladder's rebuild (below), whose Collect is a kit action-bar button with its own sound.
• Seven buff-bar numbers on the Stats page were still server-formatted. ViewXpPage's XP boost, damage, lifesteal and combo percentages and the three flat bonuses went through String.format into ui.viewxp.buff_*_format while the three capped stats beside them already rode as typed params, so those seven printed one server-side spelling to every locale and a negative read "+-5%". All seven now bind through pages/render/StatValueText.signed (the sign and the unit in the nested value, the digits the client's), and the seven keys drop their authored +/% in all nine locales. The other number-bearing sites on that page (a tracked achievement's "3/5", an active boost's "2x" and time remaining) are not stat numbers and are unchanged.
• An owner clamp axis removed from ability-clamps.json kept its last merged value until a restart. The owner layer was merged INTO the effective clamp table, and a per-leaf merge can only tighten, so a removed leaf had nowhere to fall back to. ParamClampTable now keeps the asset layer (defaults < pack) apart from the effective table and foldOwner rebuilds the effective table from it on every owner fold, so /mmoconfig reload and the page's Reset both bring the shipped value back at once.
• An under-supplied typed {N, number} token survived literally on screen where a bare {N} was stripped: LocalizationConfig.applyArgs filled both shapes but stripped only the bare one. Both are stripped now (ApplyArgsTest).
• A capped-defense player took exactly zero damage from an ordinary mob, permanently. event/CombatDamageEventSystem.applyDefenseReduction returned baseDamage * (1.0 - reduction) as a raw float with no floor, and DamageSystems$ApplyDamage then applies Math.round, so anything under half a point lands as zero while the swing still counts as a completed hit. The fraction gets small fast: the MMO's own channel capped at 0.9 until this release (ModifierClamps/DefenseReduction.json, 0.58 now, see Breaking changes above), the engine's ArmorDamageReduction multiplies by (1 - armorSum) before it for a 94% total, and a 5-damage bite scaled by a mid-difficulty mob's 1.52 outgoing multiplier computes 5 * 1.52 * 0.06 = 0.456. keepLandingHitsLanding floors this reduction's own output at one point when the arriving hit was already worth that, exactly mirroring MobScalingDamageFilter's fix. The engine's ArmorDamageReduction has ALREADY run by then (it declares no dependencies and no priority, the Filter group orders its members by registration, and the core registers before any plugin), so this floor is the LAST reduction in the chain and a hit still worth a point after armor lands for at least a point. applyFallDamageReduction deliberately does NOT get the floor - a build reaching full fall reduction is meant to land for zero and trigger the safe-landing / dangerous-fall-survived XP, so its uncapped arithmetic is left exactly as it was. Found while measuring player power against mob difficulty, which also established that this same cap, at its old 0.9, engaging at skill-tier milestone L40 was the single cliff behind BOTH reported symptoms: mobs that cannot be killed below it and mobs that cannot win above it (at 0.58 the tree crosses it at L30 and the step is 1.65x, not 4.4x).

• The MaxHealth power pillar was dead on every default server. Modes.Balanced never named it and every builtin registers defaultWeight 0.0, which PowerLevelService.computeWith treats as "skip the provider", so the shipped BaseHealth 100 / Factor 10 tuning did nothing; Achievements under CombatOnly had the same latent shape. Wired in as part of the retune above, and the class of bug now reports itself: PowerLevelValidator WARNs OMITTED_PILLAR for a registered pillar the active mode never names and that brings no default weight, INERT_PILLAR (INFO) is reserved for a tuned pillar the mode explicitly switches off with 0.0, and every shipped mode names all six builtins (PowerLevelValidatorTest holds that structurally).
• The cached power could outlive a change of the player's health maximum. Wiring the MaxHealth pillar in made power depend on a LIVE value no component mutation announces: gear, per-stack item enhancement and the native Utility stats ziggfreed-common's EquipStatBridge applies on a held / armor / utility change, a class change (ClassService), a potion or any engine effect, all move the EntityStatMap maximum, and only skill, claim, mastery, ability and achievement mutations flipped the cache's dirty bit. Rather than an invalidation at each of those sites (and every one added later), the memo is fingerprinted on the live maximum at the ONE read: power/PowerLevelCache (the three transient fields it replaces on SkillComponent, plus the fingerprint) is valid while its dirty bit is clear, its config epoch is current AND the health maximum BuiltinPowerPillars.liveMaxHealth reads now equals the one it was computed against; a known maximum that differs is a miss, an unknown one (no store in hand) never invalidates, and a memo taken against an unknown maximum is replaced by the first real read. One stat read per power read, which a recompute did anyway, so the per-region-cross read the mob-scaling companion makes stays O(1). The ready-time drop this cycle first added is gone again: the fingerprint covers it. The config epoch the memo is pinned to is the SUM of every generation counter the fold reads off live config, each of which only grows, so any one of them moving is an epoch no memo was computed under: the power settings generation (PowerLevelService.setSettings), the pillar registry generation (register / unregister, so a sibling mod's pillar registered after players are online folds in on the next read), the ModifierClamps fold generation (ParamClampTable.generation(), bumped by every fold; the StatRewards pillar holds a saturated stat at a clamp ceiling), the skill-tree generation (SkillTreeConfig.generation(), bumped by every load and every save; the StatRewards pillar walks the live trees), the skill-roster generation (SkillRegistry.rosterGeneration(); the combat pillar walks the live COMBAT category and the StatRewards pillar every skill) and the leveling-curve generation (skill/LevelCurve.generation(), counted the moment a curve setting differs from the table in force; a combat level is XP read through that curve). /mmoconfig reload moves the last four at once and touches no power setting, which is why the epoch has to see them; a reload, a refold, a tree edit, a custom-skill registration or a curve change now lapses every player's memo at once, for a handful of counter reads per power read. The leveling curve itself moved out of SkillComponent into skill/LevelCurve (the component's calculateLevel / getXpForLevel delegate to it), which is where its generation lives, and SkillComponent.addByName drops the memo the way setXpByName already did, because the API's addXp reaches it with no level-up fan-out afterwards.
• The three fail-closed fallbacks MIRROR the shipped assets. CombatDamageEventSystem.DEFENSE_REDUCTION_CAP_FALLBACK (0.9, now 0.58) and SchoolResistReconciler.MAX_PERCENT (90, now 30) stood in for a missing clamp asset with exactly the ceilings this release lowers, so a failed asset load would have reverted the server to the old behaviour without a word. Each constant now carries the shipped Max and a comment saying the asset is the authority, and the new SkillTreeService.CRIT_CHANCE_CAP_FALLBACK follows the same rule from the start; DefenseReductionClampAssetTest, SchoolResistReconcilerTest and CritChanceClampAssetTest hold each equal to the file it mirrors (read, not pinned) and prove the fallback never leaks while an asset is loaded.
• A capped stat says so wherever its sum is shown. The stat-sources page (StatBreakdownPage: rail totals, section totals, the drill-in grand total) and the held-item panel showed the SUM of claimed picks ("Crit % +221%" for Daggers) with nothing saying the effective chance is capped. pages/render/CappedStatText is the one renderer for such a total: once the sum has reached its key's ceiling the ceiling follows in parentheses (ui.statsource.value_capped, nine locales, the total AND the ceiling bound as typed percent numbers so each client formats both), for CRIT_PCT, BLOCK_PCT and FALL_PCT alike, and under the cap the value is typed the same way through the new pages/render/StatValueText (ui.statsource.value_pct / _negative / _bare and the value_flat triple, nine locales: the sign and the unit in the key, the number a typed param, so on the stat-sources page, the held-item panel and the Stats page's buff bar every stat number is a typed param; StatSourceAggregator.formatStatValue is deleted). The stat-sources skill dropdown, a String-only engine sink, reads the same total through CappedStatText.plain, the same key resolved server-side in the default language (LocalizationConfig.applyArgs fills a {N, number} token there like a {N}), so it carries the cap note too. The Stats page's block, crit and fall labels paint through it as well (fed the summed LIVE channel, so the bar agrees with the held-item panel beside it while nothing else feeds the stat and differs by the gear once it does; the BLK / CRIT lang keys drop their own +{0}% frame for it, and FALL keeps its minus, FALL -{0} over the bare number, since a fall reduction reads as less damage taken), and the value slots on all three surfaces widened to fit. The ceilings themselves moved out of the power pillar into reward/StatCeilings (of / usable / reached), the ONE per-stat table the pillar, the two pages and the Stats page hint read, each entry still the live clamp seam (defenseReductionCeiling(), criticalChanceCeiling(), FULL_FALL_REDUCTION). It has NO arm for LUCK_PCT, by design: luck stays uncapped, and StatCeilingsTest pins that.
• The Stats page crit hint fired for every combat-equipped player when an owner authored a CritChance ceiling of zero, because a capped read equals a zero ceiling trivially. It now tests the SUMMED chance before the cap (SkillTreeService.summedCriticalChance, what resolveCriticalChance caps) through StatCeilings.reached: "you have invested up to the ceiling", which a player with nothing invested has not.
• PowerLevelService.unregister(id) removes a registered pillar (copy-on-write like register), for a mod that unloads its pillar and for the tests, which used to park neutralised fixture pillars in the process-wide registry and made PowerLevelValidatorTest filter around them; both now clean up and the validator test asserts the registry holds exactly the six builtins.
• Three public-facing statements about mitigation were wrong and are corrected. ModifierClamps/SchoolResist.json said school resist was a third multiplicative layer cut after defense and armor; the engine's DamageSystems.addResistanceModifiersFromEntityEffects sums an effect's DamageResistance into the SAME per-cause bucket as worn armor and takes one (1 - sum), so it now says that, with the elemental arithmetic (0.42 x 0.7 = 0.29). ModifierClamps/DefenseReduction.json said 0.58 composes to about a quarter of the hit; true for Physical and Projectile, which vanilla armor resists (115 of 115 pieces each), but nothing in the vanilla set resists Elemental, so an elemental hit sits at 0.42 and the comment says so. CombatDamageEventSystem.keepLandingHitsLanding's javadoc said the cap was 90% and that the engine's armor ran afterwards; both wrong (the cap is the asset's Max, and armor runs first, see above). The same ordering sentence in this file's own zero-damage entry above, in the patch note, in CURSEFORGE.md's copy of it and in CombatDamageEventSystem's own Filter-stage comment, and the "90% defense cap" / "0.9 cap" wording in SkillTreeService (twice), MasteryService, SchoolResistReconciler, the skilltree/ router, the rewards skill and CONTENT_PACKS.md, are corrected with it; a grep for the "90% cap" / "0.9 cap" wording over the main source, the assets, the skills and the docs finds no survivor (the one hit left is a test comment describing its own 0.9 fixture cap).
• CombatTextUpdate is built field by field, so crit and level-up numbers survive the next server update. The generated packet class gains a trailing nullable Color field in the build now on the shared source's release patchline, and the two-argument CombatTextUpdate(float, String) constructor feedback/ColoredCombatTextService called goes away with it, which would have made every crit and level-up float a NoSuchMethodError the day that server shipped. Both the installed 0.6.8 jar and the incoming one carry the no-argument constructor and the public hitAngleDeg / text fields, so one private combatText(angle, text) helper builds the packet through those and both call sites use it; a field the newer build adds keeps its own default. No reflection, no version branch, no deprecated API.
•     A family-wide audit of the generated-Protocol constructors the family calls found no other such break. MapMarker also gains parameters, but ziggfreed-common's worldmap/WorldMapMarkers.marker builds markers through the engine's own MapMarkerBuilder, which only gains methods, so the library needs no change. FormattedMessage, Page and ParamValue changed without touching their constructors.
• When that update lands, the same class also carries the per-cause damage-text colour the engine now resolves itself (DamageCause.resolveDamageTextColor), which is the thing ColoredCombatTextService currently achieves by swapping a per-viewer CombatText component and restoring it. That is a simplification for the release that follows, not this one.
• Shadowstep did not blink, and a blink fired mid-flight threw. interaction/MmoTeleportInteraction built its component with the raw new Teleport(target, rotation) constructor and added it with store.addComponent, the only structural component write in the whole interaction/ package that bypassed the chain's own CommandBuffer. Three corrections, all of them the first-party shape (TeleportInstanceInteraction and HubPortalInteraction are the SimpleInstantInteraction exemplars): the component is built through Teleport.createForPlayer(position, rotation), which routes the full look rotation to the HEAD and only its yaw to the body so a caster who blinked while looking up or down lands upright instead of pitched at that angle; it is added through commandBuffer.addComponent; and the caster's archetype is checked for an outstanding Teleport or PendingTeleport first, because the engine throws IllegalArgumentException on a duplicate component and PendingTeleport survives until the client acks the previous blink. A blink refused for that reason resolves Failed and refunds through the existing MmoCastFrame.failCast seam rather than dropping an exception into the chain, which had been taking the invulnerability window and the aggro drop down with it. createForPlayer, CommandBuffer.getArchetype, Archetype.contains and PendingTeleport were each confirmed against the installed 0.6.8 jar before use.
• Smoke Bomb did not drop aggro, which is the one thing its name and its smoke cloud promise. The ability's whole body was the two-beat armed strike (1.8x, then a 1.5x re-arm on the hit) plus the cosmetic MMO_SmokeBombAura, so a player reading "Vanish in a billow of choking smoke" and a status effect called Smoke Screen got a damage buff and nothing else. Server/MMOSkillTree/Abilities/Daggers/Smoke_Bomb.json gains an MmoAggroSuppress node on the cloud's own Next, at Radius 12 and DurationMs 3000: tight enough to stay a self-extraction tool rather than a camp-wide aggro wipe, and deliberately shorter than both the 5 s cloud and the 5 s armed window so the opening has to be spent rather than waited out. The tooltip picks the line up from the node, so no authored copy changed. Aggro suppression needs an AggroAPI provider on the server; with none present the node is a silent no-op and the cloud and the armed strikes are unaffected.
• A skill-tree claim card hid the ability's hard casting gate. ability/catalog/ChainDescriptionRenderer.renderCardMsg returned the authored flavor sentence alone whenever an ability declared one, so castingRequirementLines reached the hover tooltip and the Abilities tab but never the card. Mark of Death authors Casting.SelfHp.Max 0.5 and reads on its card as "Brand a target for execution", with nothing saying the cast is refused above half health; a tier pick is permanent, and on a server with skill reset switched off a player who claimed on the flavor alone could not undo it. The card now appends the same gate lines the full tooltip ends with, in the same position under the cooldown/cost envelope, so the two surfaces read in the same order.

• Display numbers on the surfaces this round touched bind typed, so each player's own client writes their digits. RepoHygieneTest's rule 5b fails the build on an unmarked String.format / NumberFormatter / NumberFormat / SkillDisplayUtil.format* call under pages/, ui/, i18n/, feedback/, event/ and player/, and its rule 5c fails a line there that spells a number by String.valueOf, a boxed toString, or a literal concatenated into a raw Message, a translation param or a .Text sink. Both scan those roots line by line, so a number spelt in another package and handed in as a String, or parked in a local first, passes them; the test's javadoc says so, and the fix for such a site is at the point the number is spelt, not a wrap at the sink. Retyped: the reward.short.* chip keys and the reward.format.* / reward.desc.* sentences (Messages, RewardChipFormatter), the mastery card's modifier lines (MasteryModifierRenderer), the quest and achievement objective counts (ObjectiveTextRenderer binds the amount as a nested Msg.num, so it groups whichever family's key it lands in: a pack's authored key, a kind file's, this mod's convention key or the shared vocabulary's, which carry a bare {0}), the tier and track counts (CountText), the boost multipliers, the boost and ability cooldown spans (DurationText over time.span.*), the class page's multipliers, the statistics' distance and playtime figures (then the achievement book's cards, now MmoStatistics rows, below), the combat notifications, the XP-token grants, the rested-XP notice, the item-requirement line behind a refused swing or block break (new pages/render/RequirementText, the same line the admin item-requirements editor lists), the boost activation refusal (XpBoostService.activateBoost / activateToken return a client-resolved Message; the cooldown rides DurationText, the counts bind on boost.limit.*, and three new boost.refused.* keys replace the English literals), the mastery lock line and toasts (MasteryService's PurchaseResult / RespecResult / ContributeResult carry a Message; the amount slots of ui.mastery.locked_need_more, toast.contributed, toast.refunded and toast.refunded_remaining are {N, number}, and ui.mastery.toast.refunded_track is new), the leaderboard ranks and level breakdown (new ui.leaderboard.rank / rank_none), the Stats page's card XP line and the skill wizard's reward value column (Messages.rewardValueMsg / rewardValueWithTargetMsg, the value half of the sentence renderers made public). Marked // NUMBER-OK: with the reason on the line: the compact k/M XP totals, the admin editors' echo of a config value beside the field that edits it, the clock's zero-padded seconds, a hex colour, and the String-only console helpers. Still server-formatted, on pages this round did not touch, and pinned by exact line count in the test's SPELT_NUMBER_DEBT ratchet so the count can only fall: 37 lines across eight admin pages, two renderers and the DB schema manager, plus SkillTreeOverridesPage's reward value column (a helper-returned String the rule does not see), the ability summary sentences under interaction/ and the station summaries under integration/stations/, both outside the scanned roots.

• A clamp read could land inside a fold and take the fail-closed fallback. ParamClampTable.fold / foldOwner cleared the effective map and refilled it while get read unsynchronized, so a damage hit, an ability cast or a power read arriving in that window saw a miss for a key authored before and after, and every owner save from the Modifier Clamps page and every /mmoconfig reload opened it. Both layers now live in one immutable snapshot behind a volatile field, built in full and published in one assignment (the shape the mob-scaling companion's DifficultyConfig uses for its index), so a reader sees the old table or the new one and never a half-filled one; ParamClampTableSnapshotTest races a reader against four thousand folds and holds the miss count at zero, and proves a map handed out before a fold stays complete after it.
• The Modifier Clamps page carried a copy of a balance figure. Its defense-reduction sentence multiplied the live ceiling by a hardcoded top-armor resistance to print "about 25% of a physical hit", a number that belongs to the game's armor set and to the asset's own comment, not to Java. The sentence now binds the live ceiling and the elemental share and says in words that a physical hit lands lighter still once worn armor has taken its cut; its school-resist line reads SchoolResistReconciler.maxPercent(), the same seam the hit uses, instead of a second fallback of its own; and the unread effective parameter on aboutFor is gone, so the sentence and the row under it read the same table.
• A lucky hand harvest could cost the player the harvest itself, and an extra that did not fit the backpack vanished. The game fires its pickup event before it gives the harvested stack, and the bonus copy was added to the backpack inside that event, so with a nearly full bag the copy took the room the harvest needed; whatever of the copy did not fit was simply lost, and the "Lucky!" note counted the whole stack either way. The bonus is now rolled after the harvest lands. The copy goes where the player's own pickup settings route that item, topping up a partial stack first, so it stacks with the harvest; only what does not fit drops as one pile at their feet, and the note counts only what landed. The odds and the amount are unchanged.
• A slain creature whose facing could not be read dropped no bonus loot. The corpse drop needed both a position and a head rotation and handed over nothing without either. It now lands at the corpse as the game drops a dying creature's own loot, facing nowhere in particular when there is no head rotation; only a corpse with no position still drops nothing, now with a warning.
• The bonus mob-drop note ignored the player's luck-drop notification setting, and read in English in seven languages. It now follows the same setting as a lucky find, and notify.mob_drop and notify.mob_drop.hint are translated in all nine locales.
• A kill row whose Notify.Color could not be read showed no note at all. The colour threw and the note was skipped with a warning; it now falls back to the moment's own colour.

Technical

• Every reward the jar's quests, board contracts and point milestones author is collected. A Claim row, never Auto, except an achievement's title or a boost token, which may land on unlock. Converted: Getting_Started (its two items; the guide's welcome and its skip finish it through QuestService.complete, whose forced completion pays both lists on the spot through QuestEngine.tryForceComplete, so a new player still holds the scroll and the book at once, and craft_starter_tools, which requires it claimed, is still accepted in the same beat), the four Mmo_Hallows_Eve_Daily_* contracts (collected at Old Jack's board, which a contract's Claim parks at: a job finished in the event's last hours waits there until the board posts again), and the five Points_* milestones (each Mmo_Xp row moves to Claim, collected through AchievementService.claimMilestoneRewards; each Mmo_Boost_Token stays Auto). The titles this release adds pay from Auto, the exception. ShippedQuestContractTest and HallowsEveJarContentTest assert the Claim bucket where they asserted Auto.
• The content audit's prose pass changes en-US only. Achievement names and descriptions, the onboarding tour, fifty ability.*.desc lines, the guide's lines, the quest toasts (notify.quest_ready_to_claim, .contract_ready_to_claim, .quest_inventory_full, ui.rewards.inventory_full, .claim_success, which now say collect), the capes, the ability-slot items and the XP token sizes. Two keys lose their {0}, achievement.quest_weekly_t1.desc and achievement.deaths_t1.desc, so their eight translations are removed for the lang wave rather than left failing LangFileIntegrityTest's placeholder parity. The token sizes' other locales come from tools/i18n/generate_xptoken_langs.py, whose per-locale adv words for Piece, Token, Grand_Tome and Relic need the same re-rank. objective.text.calendar_attended and .any keep their keys with ziggfreed-common's new wording ("Take part in {1}"): the renderer's shared rung reads the progression vocabulary, not the calendar file that holds objective.calendar_attended, so without them the step falls to the generic line, which ObjectiveKindVocabularyTest fails.
• The MMO registers only what it adds to the library's conversations. ZiggfreedCommon 2.2.0 now ships a default quest binding for conversations (RuntimeDialogueQuests), the completion-conversation host, the HasOfferableQuests condition and the TALK_TO_NPC credit, so MmoDialogueQuests extends the library's binding and declares only subject(ctx) (the payload self-heal), MmoQuestDialogueHost and MmoTalkCredit are deleted, MmoDialogueConditions no longer registers HasOfferableQuests, and the talk statistic rides MmoMomentReactions on the library's TALK_TO_NPC moment (one count per conversation). A quest the pool no longer carries reads its stored state in the library itself, so the MMO's reader override is gone. MmoRegistersOnlyWhatItAddsTest fails a re-registration of any of them.
• Template_Mmo_QuestGiver is now a Variant of Ziggfreed Common's Template_Zig_QuestGiver, which carries the whole body; it re-declares the same five parameters with the MMO's defaults and forwards them, so a pack Variant still modifies exactly Appearance, NameTranslationKey, Weapons, OffHand and DefaultOffHandSlot. Quest givers built on it now show the library's press-F hint key, whose English text is unchanged. MmoRoleTemplateParameterTest reads the library template from disk and checks each Variant against the parameters of the role it references.
• NewShapeContentCorpusTest walks every gear set a pack or RPG Stations ships (Server/ZiggfreedCommon/GearSets), decoding through the library's real GearSetAsset.CODEC with Parent resolved and holding each to the validator's shape checks; no two of those files may land on one id (the store keys a set by its bare file name, so one would silently replace the other). ObjectiveKindVocabularyTest checks the new kind file against the enum, and MmoMomentReactionsTest covers the new kind's payload gate.
• A reward kind that pays only inside a pass carrying its collector (Ziggfreed Common's CollectingRewardKind; RPG Stations 1.1.0 registers its three station kinds that way, rpgstations:output_items among them, and the library's own Moment_Item is one) is not payable at a quest, achievement, shop or dialogue site. RewardSpecs.isPayable answers false for one (RewardSpecs.isPassOnly), ValidationChecks.checkRewards reports it under the library's PASS_ONLY_REWARD_KIND code with a message that says what it needs instead of calling it unknown, and RAISE_TO_ERROR raises that code beside UNKNOWN_REWARD_KIND, so a folded quest or achievement authoring one is exactly as loud as when its kind still read as unknown (PassOnlyRewardKindAuditTest). The loot-table audit needs no change: the station kinds are known now, so the 13 LOOT_UNKNOWN_REWARD_KIND warnings the stations pack's tables raised at boot are gone.
• A lucky block break and a kill's bonus drops hand their items and native drop lists over through Ziggfreed Common's ground-spill preset (GroundSpillSinks) instead of two hand-built sink pairs: LuckUtil spills at the broken block and counts every spilled stack as found, as before, and the bonus-drop pass in MmoMomentReactions.handleMobDrops spills on the library's corpse ground, GroundSpillSinks.atEntity (the corpse's position read at drop time, lifted one block and facing as the engine drops a dying entity's own loot, identity facing without a HeadRotation), counting what that ground answers it dropped; the MMO's own spillAtCorpse, which dropped nothing without a head rotation, is deleted. A drop list nothing claims is now warned once by the library's native roll rather than by a second check of the MMO's own. The corpse facing is the one change a player can see (see Fixed).
• The bonus-loot changes landed pin-first. Pure seams choose a bonus note (LuckUtil.noteSpec over each moment's NoteDefaults, answering a BonusNote record), the kill row's chance gate (MmoMomentReactions.killRowFires), the pickup gate (pickupBonusConsidered, which now asks that the pickup PAID XP, xpAwarded > 0, where it read the result's presence) and the harvest pass (LuckUtil.pickupBonusPass, harvestOf), pinned by BonusNoteTest, MmoMomentReactionsTest and PickupBonusPassTest. build.gradle gains ziggfreed-common's tag split: engineItemTest runs the tests tagged engine-items (they build a real engine ItemStack) under the engine's log manager, the plain test task excludes them, and check runs both.
• BonusDropsAsset.Kind gains PICKUP_ITEM, appended after KILL_MOB so fold and listing order never move. Each constant declares whether an unwritten Chance borrows the player's luck (unwrittenChanceBorrowsLuck, unauthoredChance), and the collectors its pass carries are ziggfreed-common's BonusMoment.carries() (MomentItems for PickupItem, nothing for the other two), which the shared audit reads; a pass carries MomentItems only when its site hands it the harvest. BonusDropsConfig.onPickupItem answers only PickupItem rows. Entry.chanceFraction reads a NaN result as no chance (a min/max clamp alone kept NaN, which the kill gate read as firing). When.Kind's editor schema lists the three moments, and Notify.Color drops its one declared #ffaa00 and documents each moment's default instead. BonusDropsValidator audits each row's inline rolls through ziggfreed-common's BonusRowAudit, which hands the four-argument LootableValidator.auditRef its moment's carries() set, so a Moment_Item outside a PickupItem row warns PASS_ONLY_REWARD_KIND; a table the row names stays on the silent table path (BonusDropsAssetTest, BonusDropsValidatorTest).
• mmoskilltree:moment_skill_luck (content/gate/MmoFactorContributions) answers 100 x SkillTreeService.resolveLuckChance for the skill a MomentSkill payload names (content/gate/MomentSkill, riding the FactorContext's one payload slot), and is unanswered without that payload or a live subject (MomentSkillLuckFactorTest). The block and harvest passes build one moment context (LuckUtil.momentContext: the store, the player, the harvested stack as the item, the skill); a kill's context carries no payload. A context holding MomentSkill cannot also hold a GateSubject, so the gate vocabulary's saved-record overrides fall through to their live reads there, as for a context with no payload.
• The harvest bonus is one deferred pass. MmoMomentReactions.onPickup pays XP inside the producer's dispatch and, when it paid, LuckUtil.tryLuckBonusForPickup queues ONE World.execute task (a world refusing tasks while it shuts down means no bonus), because the engine fires InteractivelyPickupItemEvent before it gives the stack. The task re-reads the event (harvestOf: a cancelled or emptied pickup pays nothing, and the stack copied is the event's FINAL one, whatever another plugin swapped in), rolls the row's chance against the moment context, and rolls its loot with a MomentItems collector over that stack layered on the subject (subject.withFacets). The row's own items and the resolved copies hand over through ONE GroundSpillSinks preset, pickupRoutedFirst(player) (the library's GroundSpillSinks.pickupRouted, the engine's own Player.giveItem routing with partial stacks filled) and then one pile at the feet (NativeLootService.spawnAtFeet); the note counts the pass's landed items plus the landed copies. The event is never replaced or fired again, tryLuckBonusByName is deleted, and the pass's source id is pickup:.
• One bonus note for all three moments: LuckUtil.notifyBonus(kind, ...) sends through MmoNotify under NotificationCategory.LUCK_DROP, each moment's NoteDefaults naming its keys, colour, throttle and feed subject. BreakBlock and PickupItem share notify.luck_drop* and NotificationThrottle.LUCK_BONUS; KillMob speaks notify.mob_drop* under the new NotificationThrottle.MOB_DROP on its own feed tag (subject mob_drop), and killNoteCount counts at least one item, since a kill row's note fires for a command or a reward too. An authored colour that does not decode falls back to the moment's colour. sendDropNotification and killNote are deleted. notify.mob_drop.stacked is new, and both stacked keys bind the count as a typed {0, number} in nine locales.
• Adds a deprecation gate: the build fails on a call to a deprecated API, not just one marked for removal. gradle/deprecation-gate.gradle compiles every source set a second time with -Xlint:deprecation and fails check on any deprecation warning whose line, or the line above it, carries no // DEPRECATION-KEPT: comment; the kept calls each say why at the call site. compileJava keeps -Xlint:removal -Werror as it was, and the api module compiles with -Xlint:removal -Werror too. Every sibling mod's build applies a byte-identical copy of the file, and RepoHygieneTest fails a copy that drifts, a build script with the removal flag that skips the gate, and any @SuppressWarnings naming deprecation or removal (the old DEPRECATION-OK exception is gone).
• RepoHygieneTest holds the type scale over every shipped .ui in the jar and every present sibling mod, ZigType.ui itself excepted. everySmallUiTextSizeIsATypeScaleStep fails a FontSize under 15 written as a number, and any MinShrinkTextToFitFontSize written as a number, so nothing drifts under the floor and one edit resizes every page (a heading or hero size of 15 or more may stay a number where the scale has no step). theMicroTypeStepStaysInTheExemptHudBoxes allows @ZigFontMicro in four HUD documents only: ZigHudBars.ui, ZigHudBarGrid.ui, MmoSkillTreeAbilityCooldown.ui and MmoscalingMobInspector.ui. everyUiCrossDocumentReferenceResolves fails a $Alias.@Name whose document declares no $Alias import or, when the import is a family document, whose target defines no @Name; the client merges every mod's Common/UI/Custom into one tree, so the check reads them as one, and a reference into a vanilla document is checked for its import only. One unresolved reference fails the client's parse and disconnects every player at load, which no server-side check sees.
• MMOSkillTreeAPI.getSkillTypes() is marked @Deprecated, like the eight SkillType methods beside it: skills are string ids, so use the String skillId methods, and getAllLevelsByName (every skill id, built-in and custom) or getAllXpByName. Its signature is unchanged.
• StatSourceAggregator.sumAllScopesTreeOnly sums through a label-free walk (forEachClaimedTreeReward) shared with the breakdown page's row collector, so the power pillar no longer bakes a localized row label per claimed reward it only ever adds up, and the SHIPPED StatRewards pillar runs in a server-less JVM. PowerLevelServiceTest drives that shipped pillar over picks claimed on a fixture tree (value x factor for an unbounded key, ceiling x factor past the cap, the aggregator read beside it, and a tree edit lapsing the memo through the pillar itself), replacing a drift check that compared an empty component's zero with zero and a tree-edit proof that substituted a fixture pillar.
• The hytaleServerVersion pin reads 0.6.8, the version the installed jar reports, and the shared-source checkout moves to the 2026-09-24 sync. The whole family recompiles clean against 0.6.8 with tests green, and the headless boot check passes with zero family SEVERE.
• The shared source's release sync can be AHEAD of the released server jar. The 2026-09-24 checkout describes a build that had not shipped, so EntityEffect.OutgoingDamage, DamageSystems.ScaleOutgoingDamageFromEntityEffects, DamageCause.resolveDamageTextColor and the IgnoreDisableNPCIncomingDamage component are all absent from 0.6.8 (javap against the installed jar is what settles it). A new engine surface read from that tree is not available to shipped code until the build ships, and the same holds for ASSETS: the tree carries Crush, Earth, Lightning, Water and Wind damage causes that 0.6.8's Assets.zip does not. This jar's own Server/Entity/Damage/{Lightning,Water,Arcane,Void,Life}.json are deliberate early support for that vocabulary; Crush has none yet, so nothing may key a resistance on it until either this jar adds one or the update lands.
• The achievement fold reads ziggfreed-common's Listing.Feat and Listing.LegacySince beside this mod's own Meta.mmoskilltree.Feat and LegacySince (either marks a feat; the meta block's version wins), and leaves an achievement the library mints for one yearly occurrence of a calendar event to the library's own layer (CommonAchievementFold.foldsHere), whose availability and feat flag are live readings this mod's model would freeze.
• Bonus drops run on ZiggfreedCommon's bonus-row engine. BonusDropsConfig folds and matches through zc's BonusTable, reads a row's percent Chance through BonusChance and resolves its rolls through BonusRolls; the break, harvest and kill passes run through BonusPasses, and BonusDropsValidator through BonusRowAudit with its released BONUS_DROP_* codes. The MMO keeps its layer: the XP gate, the luck default and moment_skill_luck, the notes, bonus-drops.json and mob-drop-commands.json; every released surface reads the same rows. The kill path's reward subject carries the killer's skills, as the break and harvest paths' do. A cue toast on any of the three follows no notification setting: the subject no longer answers FeedbackAudience (see the Settings entry), and Rare_Find carries no Toast.PlayerLevel. BonusDropsConfig.patternedEntries(Kind) is gone: table() hands over the folded table (zc's BonusTable) for the shared audit and any reader that speaks the library's moments, and entries() still lists every folded row. Tests: BonusDropsRebaseTest, KillBonusPassTest, KillSubjectTest, and the released bonus suite unchanged.
• DamageUtil.isCause reads the resolved cause only. The fallback to Damage.EnvironmentSource.getType() is gone: Update 7 removes that method (a 0.6.8-built jar would throw NoSuchMethodError past isCause's catch (Exception) there), and the branch was dead on both lines for its two callers, the fall checks in CombatDamageEventSystem and CombatXpEventSystem. Test: DamageUtilTest.

[1.6.2] - 2026-09-15

A hotfix over 1.6.1: the empty bounty boards, the gear-namespace mismatch in the stat taxonomy, and the warning storm at boot. The first and the third are ZiggfreedCommon 2.1.1 fixes this version rides.

Breaking changes

• Requires ZiggfreedCommon 2.1.1 or newer. REQUIRED_ZIGGFREED_COMMON and the ziggfreedCommonVersion pin both read 2.1.1; the pin feeds the manifest's ^2.1.1 floor, which is what the engine enforces (it drops the mod at load and names the version it wanted, the server itself still boots; the in-jar probe only catches a missing library). The board fix is the library's, so the two jars move together.

Fixed

• Every bounty board rendered its empty state. ZiggfreedCommon has published the folded contracts (CommerceCatalogs.publishBounties, off the Bounties load event) and the shared quest fold (ProgressionDefaults.publishAssetContent) under the SAME owner name since 2.0.0, and a publish replaces that owner's whole layer, so whichever ran second wiped the other. Before 1.6.1 the shared fold ran first and lost, invisibly, because this jar published its own quest layer then; 1.6.1 moved the shared publish onto the runtime build, so it ran last and the contracts were what vanished: the 2026-09-12 boot log reads quests=67 (ziggfreedcommon 67) with 88 contract files loaded, and ZigBoardPage skips every contract the quest engine cannot name. 2.1.1 publishes the contracts as a named SLICE of the library's layer (ProgressionRuntime.publishQuests(owner, slice, layer), additive; the two-arg call is the default slice), so each fold replaces only its own slice on a reload. Nothing changes in this jar beyond the floor.
• Enhanced gear was filed under Other, and a DOT's GearEnhancement: false opt-out removed nothing. The shared equip bridge is installed as EquipStatBridge.install("ziggfreedcommon") and writes ziggfreedcommon:held:0 / :armor: / :offhand:0 / :util:, while reward/MmoStats.KeySegments only recognised mmoskilltree:-prefixed keys, so isEnhancementBridgeKey was always false and categoryOf never answered GEAR for a stamped stat. The taxonomy now reads the namespace off the installed bridge instance (KeySegments.bindBridge, called first thing in event/SystemBootstrap.registerSystems, the one place the plugin already hands the installed bridge through, before any trigger system can fire a recompute; unbound, the taxonomy recognises no bridge key at all rather than guessing), a bridge key is GEAR and is what the DOT opt-out drops, and CombatDamageTrack3FoldTest, HitDamageAttributionParityTest and MmoStatsKeySegmentsTest use the real spelling (they had the mmoskilltree:held:0 one, which is why they passed). The flat / percent partition was already right, since a non-MMO key folds before the percent multiply either way, and stays so.
• About five hundred 'ziggfreedcommon' and 'mmoskilltree' both publish the achievement ... lines at every boot. The library's commerce wiring registered ziggfreedcommon at CONSUMER rank before its progression bootstrap could claim LIBRARY-DEFAULT rank (ProgressionRuntime.newRegistrar keeps the first rank an owner asks for), so the MMO's reading of a shared achievement clashed with the library's instead of outranking it silently, and load order decided which stood. 2.1.1 registers the library at default rank everywhere and warns once when an owner comes back asking for a different rank.

[1.6.1] - 2026-09-12

Breaking changes

• Requires ZiggfreedCommon 2.1.0 or newer. REQUIRED_ZIGGFREED_COMMON and the ziggfreedCommonVersion pin both read 2.1.0, and boot refuses an older jar by name rather than starting with enhancements that silently do nothing or a boss framework that is not there.
• strictPlacedBlockCheck and placedBlockExpireMinutes are retired (hard break, one boot WARN each naming the change). A placement earns nobody credit whoever placed it, and it is remembered until broken - free now that keeping it costs nothing. Both are still read from skill-config.json solely to notice a server carrying them, and are never written back, so a save drops them. Migration: delete both keys from skill-config.json; where the lenient setting was standing in for a builder putting ore up for players to work, grant that builder mmoskilltree.placedblocks.exempt instead (OP and creative placements are exempt already).
• mods/ziggfreedcommon/placed-blocks.json is retired to .legacy on first boot with one notice. Rows are not carried across: a saved position cannot be put back onto an unloaded chunk, and holding the file in memory until its chunks arrived would keep the cost being removed. Blocks placed before the update stop being remembered; everything after is guarded as before. Migration: nothing to carry across; the .legacy copy is never read and can be deleted.
• Your own quest files move to mods/ziggfreedcommon/quests/, one file per quest in the shared shape, once, on the first start after the update (hard break for anyone still editing mods/mmoskilltree/quests/). Every mods/mmoskilltree/quests/*.json (sub-folders included, the retired _defaults/ echo excepted) is converted into mods/ziggfreedcommon/quests/.json, the folder ziggfreed-common reads a server owner's quests from, and the original is renamed .legacy beside itself; one boot notice names every file, every quest and every leaf the shared shape has no home for (a raw description, which reads from quest..flavor now; npcDisplayName; a permission or requireLevel that hid nothing). A file that cannot be converted (a template no pack provides, a quest with nothing to do, a body the shared codec refuses, a target file that already exists) is left where it is, whole, and named with the reason; a file already in the shared shape is moved across untouched. It is the rewrite the docs-site Migration Converter performs on the same file, so either route lands the same files. Migration: nothing to do for a file that converted; read the notice for one that did not, fix it, and restart. Author new quests straight into mods/ziggfreedcommon/quests/.json (a same-id file merges leaf by leaf over the quest the jar or a pack ships, so {"Enabled": false} alone switches one off); the old folder is not read any more.
• A pack's Server/MMOSkillTree/Quests/ files still load, converted at every start; author new quests in Server/ZiggfreedCommon/Quests//. Each legacy pack quest (its extends/params templates resolved against the pack's QuestTemplates) is converted into the shared shape at load and handed to ziggfreed-common's quest store as a contributed layer, above the shared files and below the owner folder; one boot line per pack names it and points at the web converter and the shared folder. A quest the converter refuses is named and left out, never half-loaded. The pack-control Replace mode for quests is not honoured any more (one boot WARN names the pack); /mmomigrate reports each such file as handled by the jar, and a QuestTemplates/ file as needing hands. Migration: a pack keeps working as it is; drop a "Quests": "replace" line from its Control file (the key is unused), and move each quest to Server/ZiggfreedCommon/Quests// through the web converter when you next touch the pack.
• Meta.mmoskilltree.Feature on a quest is retired (one boot WARN per quest still carrying it, naming the replacement). A feature a quest needs is a top-level Requires factor, {"Factor": "mmoskilltree:feature", "Param": "", "Min": 1}, which Ziggfreed Common's fold lifts onto the quest's own availability so the quest does not exist here while the feature is off, exactly what the knob did; the older owner format's requiresFeatures list converts to that factor on its own. The knob stays on an ACHIEVEMENT's Meta.mmoskilltree. Migration: move each Feature entry into the quest's Requires.Factors; until then the quest is in circulation with the feature off, and the boot line names it.
• A save's quest and achievement record is moved once, and the move is claimed on that first login whatever it could not re-key. The two legacy per-player records (QuestComponent, AchievementComponent) stay registered and read-only and are never stripped from an entity; what changes is when the claim is spent (the first Fixed entry below). Migration: nothing to do. On a server that came up from 1.5.x before this version, each player gets one last copy of the old record at their first login after the update; an administrator who hand-cleaned a player's file on the shared side only removes the legacy mmoskilltree:quests and mmoskilltree:achievements sections too before that login, or that last copy brings the old state back once.
• /mmopacks exports and the config presets carry a server owner's quests in the shared shape. The exporter writes what mods/ziggfreedcommon/quests/ holds, verbatim, at Server/ZiggfreedCommon/Quests//.json (a file that only retunes a shipped quest is named in the log, because on its own it is a partial body); a preset's quests carrier is a map keyed by id (schemaVersion 2), and a legacy preset's quests array is still imported through the converter.
• An item's description is authored on the engine's own key, never generated (hard break for a pack that used .description.base). The mod wrote items..description into its runtime language pack as a copy of an authored items..description.base key, and that pack registers at plugin start, after every item has loaded; the engine checks an item's TranslationProperties.Description key against the loaded languages as the item decodes (ItemTranslationProperties.SERVER_LANG_KEY_VALIDATOR, with no plugin hook before it), so every such item logged [LOC] Key 'server.items..description' does not exist in server.lang! at every boot, and the copy bought nothing once the generated stat lines it used to carry were gone (the client's native tooltip stats section rows Utility.StatModifiers for every carrier). ToolStatDescriptionGenerator and LocalizationConfig.canonicalItemDescriptionBase are deleted; the roll-entry parser, points formatter and family colors that ItemEnhanceDisplay and ItemEnhanceRoll read for a per-stack enhancement line move to item/StatLineFormat; the generated-lang pack carries only the per-skill tooltip labels, and a server.lang an earlier version staged under mods/mmoskilltree/generated-lang is removed at boot. Migration: in your pack's server.lang, rename every items..description.base line to items..description, the key the item JSON already references; an item still on the old key has no description, and that [LOC] line names it at boot. The shipped examples/phase-i-school-pack is renamed the same way.

Features

• A placed character shows you what they have for you, over their head and on the map. Adds quest/QuestIndicatorService: over every placed NPC (an entity carrying ziggfreed-common's PlacedNpcComponent), each online player sees the picture for the highest of the four situations that character is in for THEM (a scroll for a quest they could take, a gold bar for an errand they can hand in, a small pile of gold coins for a reward waiting; a map for a quest they are still on exists as a look but ships switched off), and the world map and compass mark every character with a quest on offer under the new quest.marker.available hover line ("Quest on offer: {0}", the quest's own title nested). The MECHANISMS are Ziggfreed Common 2.1.0's: the per-viewer picture is its new entity/overhead/OverheadIndicators primitive (one transient, intangible, never-persisted marker entity per host and state, sent only to its audience inside the engine's own visibility pass, moved after its host on a quarter-second cadence), the availability answer is its objectives/indicator/QuestIndicators over the same lifted CharacterQuestListing the NPC quest page lists by (so the cue over a head and the list behind a press-F can never disagree), and the map marker is a SECOND WaypointTargetSource on the existing QuestWaypointService (the tracked-quest source stays first, so a character the player is already being sent to keeps that marker). This mod supplies what only it knows: which entities are hosts, the alias answer set (the page's own MmoNpcQuestDeps seam), the hover wording, and when a viewer's answers are recomputed: on the six quest events and at player ready for the one player, and on two engine-throttled DelayedEntitySystems (one indexing the placed characters per world, one evaluating every player against that index) every five seconds for what no event covers; a disconnect forgets the viewer everywhere. Registered from quest/ProgressionBootstrap, refreshed from player/PlayerReadyFlow, cleared from player/PlayerDisconnectFlow; the plugin file is untouched. Four look files ship under Server/ZiggfreedCommon/OverheadIndicators/ (Quest_Available a scroll, Quest_Ready_To_Turn_In a gold bar, Quest_Reward_Ready a small pile of gold coins, Quest_In_Progress a map, each three quarters size, lifted 1.1 above the head so it clears a tall headdress, spinning the way a dropped item does), each floating one of four MARKER ITEMS under Server/Item/Items/MMOSkillTree/Markers/ (Mmo_Marker_Quest_*, a Parent child of the vanilla Deco_Scroll / Ingredient_Bar_Gold / Deco_Treasure_Pile_Small / Deco_Map that draws the same picture, sits in no creative category, and carries the coloured halo vanilla draws around a rare drop: ItemEntity.ParticleSystemId Drop_Rare for the scroll, Drop_Legendary for the gold bar, Drop_Epic for the coin pile, Drop_Uncommon for the map; the halo is read off the item asset and never off the entity, which is why each look needs an item of its own). A pack overrides a look or a marker by id, and ShippedOverheadIndicatorsTest holds the set to exactly the four situation defaults and pins that every item a shipped look names is a marker item this jar ships.
• Whether a quest situation shows, and how, is authorable at three scopes, merged per leaf. The shared Indicator block (Ziggfreed Common's QuestIndicatorSpec: Collect / TurnIn / Available / InProgress, each {Enabled, State, Overhead: {Enabled}, Map: {Enabled, Icon}}, plus one Enabled over the block) is read at the server's global Server/ZiggfreedCommon/QuestIndicators/Default.json (owner file mods/ziggfreedcommon/quest-indicators.json), on a quest, and on a step for the situation that step raises; the narrowest leaf wins. The block reaches the engine on the shared Quest itself (indicator(), stepIndicator(objectiveId)), folded by the library from the file; this mod models no quest of its own, so nothing here carries it, and an older-shape quest file's indicator (quest and step scope) is carried into the shared body by migrate/LegacyQuestConverter. The shipped default enables the map for Available alone, with Coordinate.png; overhead is on for Collect, TurnIn and Available and OFF for InProgress (the library's Default.json sets InProgress.Overhead.Enabled false, so a character where only a carried quest applies shows nothing and any higher situation still shows; one leaf in a pack's Default.json, the owner file or a quest's block turns the map picture on). A block pointing a situation at a state no look file describes is a quest-domain WARNING (UNKNOWN_INDICATOR_STATE) in /mmoconfig validate and the startup audit, folded in by QuestValidator beside the pool audit.
• XP gain is a progress bar, not a line on the notification feed. Every skill has a bar on Ziggfreed Common's new progress-bar panels: the moment a skill gains XP its bar comes up, the name and the XP gained since it came up sit on the first line, the fill underneath is progress to the next level with the level you are in at its left end and the level you are climbing to at its right (MAX there, and a full bar, once the skill is capped), and a bar fades a few seconds after the skill stops gaining. A gain that crosses a level paints its bar gold, and the next ordinary gain paints it back. Which panel the bar lands on follows what you are DOING, not where the XP came from: out in the world it comes up on the wide World panel, which sits top-right by default (above the quest tracker, six across and growing leftward, so a bar already on screen stays where your eye left it; the bottom-left spot is the other one shipped for it, three columns above the hotbar and filling upward, with a band left clear across the rows so a busy stretch straddles the player's own health and mana bars instead of climbing into them and a cut that steps the far column around the utility slot); while you work a station it sits on the tall Activity ledger in the top-left column beside that session's item, lucky and session rows, HELD with the rest of the ledger until the run ends rather than fading on its own clock, whatever skill earned it (Defense XP from a mob hitting you while you mill belongs on the panel you are looking at). Where a panel sits is a spot file, a player's own pick or the HUD settings page (see the next entry). The XP gains notification toggle keeps its meaning: off, and no bar shows. Everything else on the feed (a first-gain welcome, level-ups, the rewards-waiting reminder, luck drops, quests, achievements) is exactly where it was. Nothing is authored for a bar and nothing is registered with the library: skill/SkillHudBar.moveFor derives every skill's row from the skill registry and one read of the saved skills (the row is the skill's own id; its name, its icon, its category's colour, its place in the stack, how far the level is filled, and the two captions, ui.skillbar.level binding the level as a typed number and ui.skillbar.max in all nine languages), and SkillService.notifyXpGain asks RpgStationsBridge.isWorkingStation and hands all of it to the right panel with the gain itself, so a skill added by a pack or custom-skills.json gets a bar exactly like a built-in one and no award call carries a source parameter. The station answer is a live record StationBridgeListeners keeps off RPG Stations' session started / completed pair (player to running session, cleared by session id so a stale stop never clears a newer session), read through a plain-typed facade that is a safe false with RPG Stations absent or disabled. A server owner who wants one row different authors a Server/ZiggfreedCommon/HudBars/.json whose Source is the skill's id (MINING), or an entry in mods/ziggfreedcommon/hud-bars.json. The category colour every skill surface reads now lives once, on SkillCategory; the single-skill reset card's strip reads it too, so combat there is the XP page's red and a custom skill's category shade is the XP page's.
• Where the bar panels sit is a spot a player may pick, and the page that edits it is the library's. Ziggfreed Common 2.1.0 names a panel's spot from its HudSpots store (Top_Left, Top_Right, Bottom_Left shipped; a pack adds one by dropping a file), keeps a player's own pick or hide on its HudPreferenceComponent, and ships the HUD settings page (a Mine tab every player may open, a Server tab for whoever the consumer's audience admits) plus /zighud. This mod adds only what the library cannot know: the HUD PlayerDataDomain and player/HudPreferencePersistence (one listener on the native ZigHudPreferenceChangedEvent, registered from quest/ProgressionBootstrap, marking the domain dirty and flushing it so the DB backend carries a pick between servers; DbBlobCodec and both sessions know the domain), PlayerSession.hud() for the peek, a HUD bars button on the Settings menu and a Bar Panels button on the admin HUD page, each launching the shared page through pages/hub/MmoHudSettings with the admin audience, the theme and where Back goes (the paradigm: a setting about a shared surface is the library's page, a consumer's menu launches it; MmoNpcPlacementAdmin and MmoProgressionSwitches already do the same). Seven new keys in nine locales (ui.settings.hud_bars*, ui.admin.hud_bars_*). HudPreferencePersistenceTest drives the listener against FakePlayerDataRepository.
• Every jar quest with a report-back step keeps that step off its list until the work before it is done. All twelve quests naming Npc.TurnInId (the starter chain, its four side quests and the four temple quests) author Ziggfreed Common 2.1.0's Flow.HideLockedSteps, and their $Comments say what it does for the reader. The leaf reaches the engine on the shared Quest the library folds; an older-shape quest file spells it hideLockedSteps (or HideLockedSteps, like its siblings) and migrate/LegacyQuestConverter carries it into the shared body, which /mmopacks export copies out with the rest of the owner file; SharedLayoutExportTest rides it round the export. It is quest-level because it has to reach the report-back step QuestAsset.toDefinition appends one order after everything else, which no per-step leaf could carry.
• A quest says who may see it before taking it, carries its own fallback prose, and reaches a level by name. Three shared-schema seams land with Ziggfreed Common 2.1.0 (its own changelog has the detail, this mod only consumes them): Listing.ShowWhen, a block in the same shape as Requires that hides the quest until it passes, independent of the accept gate, the third visibility knob beside Hidden and RequirePrerequisites; Text.Lore {Incomplete, Active, Complete}, one raw paragraph per lifecycle state, outranked by the quest..md. key whenever one ships; and an objective-kind alias, which is how this mod's REACH_LEVEL runs as STAT_THRESHOLD on the skill's level channel while every sentence and picture keeps the skill the author named. A server owner's own quests live in mods/ziggfreedcommon/quests/.json, one shared-shape file per quest, a same-id file merging leaf by leaf over the shipped quest (Breaking changes, above).
• A boss fight is a quest step, an achievement criterion and a bounty objective. Ziggfreed Common's boss framework fires three shared step kinds, ENCOUNTER_DEFEATED (once per credited participant when the boss falls), ENCOUNTER_ATTEMPT (once per participant when a fight settles, won or wiped) and ENCOUNTER_PHASE (once per live member on each phase beat), and this mod's own fold, validator, icon and name paths know them: a step reads {"Kind": "ENCOUNTER_DEFEATED", "Target": "KweebecNightmare_Warden_Encounter", "Amount": 1}, Target the encounter SCRIPT id (never the boss creature's, which a phase swap changes under the player), Qualifier the run's difficulty label or the phase's own state name. The step reads as the boss does everywhere else (its binding row's NameKey, through TargetNameResolver) and, for a boss whose binding row puts a marker on the world map, is drawn with the same glyph the map shows (MmoObjectiveIcons); a boss with no marker keeps the kind file's own picture. The step's sentence is the library's own objective.encounter_* line, in all nine languages, read through the shared fallback every kind has since 1.6.1; this mod ships no copy of it. A world first over a boss kill is won by the whole party that killed it, not raced between its members (a library change this mod needs nothing for). Needs Ziggfreed Common 2.1.0.
• Adds the Encounters_Defeated lifetime statistic, per encounter script id, fed by the shared defeat moment through this mod's one reaction listener (the statistic only: what a fight pays is the framework's own, and the boss creature's death still produces the ordinary kill moment with its XP and drops). It is one more line the new ziggfreedcommon:counter requirement reading can ask about ({"Factor": "ziggfreedcommon:counter", "Param": "encounters_defeated/KweebecNightmare_Warden_Encounter", "Min": 1} gates a shop row, a dialogue branch or a harder contract on having beaten the Warden), because this mod installs its statistics record as that reading's source: every tally the stats screen shows, plain total or per-thing line, is readable by content the same way.
• The encounter content-audit domain. /mmoconfig validate and the startup audit report the library's own encounter findings (a mistyped zc: beat, a binding naming a script nothing ships, a defeat beat with no ClearEncounterBossBar) beside every other domain, folded through ValidationChecks.fold.
• A generated family can fan out over every boss on the server. The library's ziggfreedcommon:encounters axis is installed into this mod's one generator registry beside the two skill axes, binding each row to the encounter script id and its encounter_name_key, with {"Difficulty": "hard"} as the one filter, so a slay-every-boss chain or a boss shelf stays right as packs add fights.
• Adds Server/ZiggfreedCommon/Factors/Mmo_Counter.json, the naming overlay for the ziggfreedcommon:counter reading, beside the jar's four other Mmo_* factor overlays, so a shop row, a dialogue branch or a contract gated on a lifetime tally reads "Requires a lifetime tally" on a locked surface instead of the generic requirements line, with the new factor.counter line in all nine languages. It carries Text alone and no ParamNames: the reading's Param is a plain total or a category/name breakdown line, and the name of the thing behind a per-thing key lives on the thing itself (a mob's own key, an encounter's NameKey), where no key pattern can reach it, so a pack that wants one tally named ships its own overlay with a Keys entry. CONTENT_PACKS.md's Condition factors chapter gains the reading's paragraph: the two-form Param grammar, what an unknown key reads (0) and what no source, no Param or no live player reads (null, and the gate stays shut).
• The worked contracts ship in the bounty pack, the first fight is Kweebec Nightmare's, and CONTENT_PACKS.md gains the chapter that builds a boss. The bounty-contracts-pack 1.2.1 carries the Open Warrant and The Muster Roll, two any-boss contracts, and kweebec-nightmare 1.2.0 runs the Warden on the framework; each one's own notes carry the detail. The Scarak Brood Queen, an overworld boss a server owner places once (one prefab paste and one /zigencounter spawn, per world, ever), is authored in the zone-quests-pack, which is held back and not part of this release. The new "Encounter authoring (boss fights)" chapter is the how-to: the six files a boss is, the zc: beat grammar, the _Encounter naming rule, the Once rule and the three other engine facts, the five Zig Types with their flat keys, the binding row key by key with its owner layer, the participation rule, the four moment files, the three step kinds, the validator's findings, and placement and respawn on a live world.

• An authored mastery Icon is the picture that renders, on the track card, the track header and every node card. MasteryPage.resolveTrackIconItem discarded the leaf outright and derived the art from the track's target, which left every GLOBAL track (each of the seven damage schools among them) drawing the same Ingredient_Bar_Iron, and made the two codec leaves that document themselves as "Item id shown as the track icon" and "Item id shown on the node card" both dead. An authored Icon now wins, the rule ShopEntryIconResolver already follows, and the derive-from-target paths stay exactly as they were for a track that names none. A node's own Icon wins over its track's through the new resolveNodeIconItem; node cards previously painted the track's picture unconditionally.
• A currency step shows the wallet it is about. Earn_Currency and Spend_Currency declare TargetNames.Currency, so a step naming a wallet is drawn with that wallet's own icon - the same one its balance strip and every price already use - with no per-wallet authoring here.

• A quest or achievement step shows what it is about. Every listed step is drawn with a picture beside it now: the item a craft or gather step names, the creature a hunt step names, drawn from that creature's own generated portrait. It reads on the giver's screen, in both tabs of the objective book and on a board's contract detail, and the picture is decided once in ziggfreed-common so a step cannot look one way on one screen and another elsewhere. A step nothing can picture keeps reading as its text alone rather than borrowing an unrelated thing's picture.
• This mod ships a file for each of the seven step kinds it adds that a screen has to picture (Server/ZiggfreedCommon/ObjectiveKinds/MMOSkillTree/*.json; the two station kinds are RPG Stations' and their files ship there), the same shared schema its quests and achievements already use: what the kind counts and how, what its target names, and what it is drawn with. A level target is the exception, being authored sugar for the shared level-threshold kind: it READS through that kind, and it draws as the skill it is about, since the runtime step names the channel carrying that level rather than the skill (MmoObjectiveIcons reads the skill back out through SkillLevelChannels.skillIdOf, leaving the summed total, highest and combat channels to the kind's own picture). The SENTENCE is not in these files: a kind's wording stays in the per-type key the renderer resolves by convention. A step whose target is a SKILL or an ABILITY is pictured by pages/render/MmoObjectiveIcons, since those are ids in this mod's own registries and nothing outside it knows that a mining objective has a pickaxe beside it wherever else this mod draws one. Everything else is pictured by the shared reading off its own target, with no fill from here.
• A step kind's wording can be re-tuned by a file. ObjectiveTextRenderer reads the Presentation.TextKey its kind's file gives it, under an objective's own key (one step saying something specific still wins) and over the per-type convention template, so a server rewording every kill step writes one file instead of overriding a key it has to know the name of. A step naming no target reads that key's .any twin where one is authored, so a base sentence with a blank for the target is never handed a step that has nothing to put in it - "Cast abilities 10 times", not "Cast 10 times". ShippedObjectiveSentencesTest folds the shipped kind files the way a boot does and renders real quest and achievement content through them, so a file whose wording cannot be filled by the step it is drawn for fails the build instead of reaching a screen with a hole in it.

• Adds STATION_OUTPUT as a step kind this mod accepts and renders. A quest step or an achievement criterion of that kind counts the stacks a station hands its worker (target = the item id, qualifier = the station id, amount = the stack's quantity; a console-command payout and unattended output never count, by RPG Stations' own rule). It is quest-producible, its target is named as an item, and it reads through objective.text.station_output ("Collect {0} {1} from a work station", with an .any form) in all nine languages.
• Adds the Station_Items statistic: a lifetime total plus a per-item breakdown (PerStationItems) of everything a station has handed the player, beside Station_Cycles. A save written before the field existed decodes with it empty; nothing is migrated and nothing is regenerated.
• Adds skill XP for unattended station work, paid at gather. RPG Stations' unattended flow lets an authored station keep converting its placed materials while nobody stands at it, with the accrued batch forwarded when a player collects the output; the stations bridge now listens for that moment and awards the batch's skill XP to the GATHERING player - a real present-player grant, per skill, behind the same permission gate every station cycle uses, at exactly the amounts the engine forwards (it already applied the idle rate and the gatherer's own scaling, so nothing is re-scaled here). No session exists at a gather, so none of the per-session summary or toast-coalescing state is touched. Needs an RPG Stations build carrying its api contract 6 or newer; RPG Stations 1.0.0 ships beside this version.
• /mmonpc place --role= [--id=] [--dialogue=] [--world=] captures the sender's position, yaw and world into a new fixed-coordinate placement, writes it to the owner file, re-reads and sweeps. An alias over ziggfreed-common's own /zignpc place and its shared NpcPlacementAuthoring, so the two cannot drift; only the gate and the wording are this mod's. It refuses an unknown or abstract role, and an id already in use.
• An NPC Placements tile in the admin hub, opening ziggfreed-common's own placement admin page. The MMO supplies only what the library cannot know: the admin audience (the same gate the hub checks), the theme, and Back returning to the hub. No MMO placement logic lives in the screen.
• mods/ziggfreedcommon/npc-placements.json accepts whole placements beside its enabled switches, at schema 1 (the lower-case gate leaf and the upper-case asset fields cannot collide, so every existing file still reads). Entries are decoded against the folded pack layer and installed as the placement store's owner layer once the packs have landed.
• Adds the MMOSKILLTREE_AUDIT_ON_BOOT environment variable. Set to 1 or true (either case, surrounding whitespace ignored; the same environment-variable convention as MMOSKILLTREE_DB_*), it runs the startup content audit at plugin start, once every pack has merged and every fold has settled and before the "booted" banner, instead of waiting for the first player, and prints one line, content audit on boot: finding(s) across domain(s), after the usual per-domain reports and the aggregate. A headless boot-check is what it is for: the audit needs no player and no world, so nothing is lost by running it early, and a boot that audited at start does not audit again when a player joins. dev-server.ps1 exports it on its own; /mmoconfig validate is unchanged.
• Mmo_Xp takes an AmountMax. The skill-experience reward kind took a single Amount, so every payout of it was a flat number while the loot layer beside it had expressed a ranged item quantity for as long as it has existed. It takes an optional AmountMax (content/reward/RewardSpecs) and draws evenly between the two, decided once per grant, mirroring Count / CountMax exactly. It is a command-backed kind, so the range travels as a declared parameter into the command template and the roll happens in AwardXpCommand, once, before the skill fan-out: an ALL or a category award pays the same rolled number into every skill rather than rolling per skill. A reward that authors no AmountMax substitutes the declared default and behaves exactly as it always did, which is every Mmo_Xp reward in the family before the stations pack's trim wages; ValidationChecks leaves an AmountMax equal to Amount alone as an intentional flat payout.

• Adds restedXpMinOfflineMinutes (skill-config.json, default 30): the shortest absence that earns rested XP at all. RestedXpService.creditOnConnect measures the gap between the stored lastSeenMs and the connect, and an absence under the minimum credits nothing; at or past it the whole stretch is credited, still clamped by restedXpMaxOfflineHours. The lastSeenMs stamp is untouched by the gate, so a quick relog resets the clock exactly as it always did, and a server that wants every gap to count writes 0. The admin Rested XP page carries a Min Offline (mins) field beside the max, saved with the rest of that page and refused when it exceeds the max offline window; /mmoconfig restedxp with no argument prints the window it is running. Defensive load and no CONFIG_VERSION bump: a config written before the key existed reads the default.
• Both quest screens say how often a quest comes round. A quest with a repeat rule is badged Daily, Weekly or Repeatable beside its row, on the list at the character handing it out and in the quest log, through Ziggfreed Common's one QuestCadenceBadge reading over QuestCadence (the longer of the rolling wait and the calendar window decides, the same bucket the finish N dailies achievement qualifier has matched on since this release). A one-shot is unbadged. This mod ships no Java for it. Needs Ziggfreed Common 2.1.0.
• The shipped quests stop hand-labelling their own cadence. Temple_Tribute and Forgot_Something drop the Repeatable tag from their Listing.Tags, and so do the mastery, stations, taming and zone quest packs (Repeatable, Daily, Weekly across seven files) - the badge derives it now, and three of those tags were WRONG: a calendar daily authored "Reset": {"Period": "Daily"} was tagged Repeatable in the mastery and stations packs as well as here. ui.quest.tag.* keeps its cadence words, since an owner may still tag a quest that way for their own grouping and the label still resolves; nothing ships one.

Fixed

• A player's quests and achievements no longer wind back on every login and every world change. On a server that came up from 1.5.x, any player with a tally the achievement catalogue could not fully account for (an achievement from a pack that is not installed, or one no longer shipped) had their OLD quest and achievement record copied over the live one again at every login and every world change: a quest an admin had reset came back, a bounty already collected reappeared as collectable, a hand-edit of the record never stuck, and progress since the update on any quest the old record knew was wound back to what it held on upgrade day. The copy happened once per ready because the move withheld its "done" claim for those tallies, meaning to retry them, and the ready event fires on every world entry. The claim is now spent by the first pass that wrote every family without throwing, whatever it could not re-key: a tally the catalogue cannot yet place stays under its saved key, and a sweep at every login moves it onto the criterion's own key the moment the pack that ships it is installed. On an affected server each player gets one last copy at their first login after this update, the way the very first login after 1.6.0 was meant to go, and never again. If you cleaned a player's file by hand on the shared side only, that last copy would bring the old state back once: remove the legacy mmoskilltree:quests section (and mmoskilltree:achievements) from the player's file as well before they log in again; that is safe for any player who has logged in on 1.6.0 or later, since the shared record already holds everything those sections carried.
• A bounty taken before the update can be collected. A contract carried across from a 1.5.x save was refused at every board. The shared engine binds a contract to the board it was taken from, recorded in the contract's own progress the moment it is accepted, and a contract carried across from the old record had no board recorded, so it matched nowhere and could not be taken again while it was still held. The carry now stamps each contract with the board that posts it (the first board it is listed on), so it collects there like one taken today. A contract the pack no longer posts on any board is dropped from the player's quest log, its completion record kept, with one server-log line naming the player and the contract.
• A quest collected at one character is collected there, and nowhere else. The stations pack's "A Word with Marn" authors "TurnInAt": "Mmo_Sawyer", and it still sat under "Ready to collect" at the mastery trainer with a working Collect button and the reward marker floating over their head. The shared quest asset decoded the leaf into Quest.turnInAt(), but this mod re-projected every folded quest through a quest model of its own and back into the engine, and neither hop carried the site, so every folded quest reached the engine with no site, which QuestEngine.canCompleteAt reads as "anywhere"; bounties kept theirs only because they never passed through that model. That model is gone (the Technical section below): the engine runs the one shared Quest the library folds, the site rides it by construction, and canCompleteAt refuses the trainer, so the stations quest is collected from the sawyer alone. The same leaf is readable on the older quest format (a Server/MMOSkillTree/Quests/ pack file, and an owner mods/mmoskilltree/quests/*.json file on the boot that converts it): turnInAt (or TurnInAt) takes exactly what the shared schema takes, true or "giver" for the quest's own npcViewId, an npc id, "@accept" for wherever the player took it, an empty string or false for anywhere; migrate/LegacyQuestConverter carries it into the shared body verbatim and Ziggfreed Common's one QuestAsset.resolveTurnInAt parser reads both, so the two formats cannot drift. ShippedQuestContractTest, QuestTurnInSiteTest, migrate/LegacyQuestConverterTest and SharedLayoutExportTest pin it.
• The last XP of a run shows the moment it lands, not the next time you happen to gain. SkillService.addXpByName batched XP notices through NotificationThrottle.accumulate, which returns nothing while its window is open and only hands the total over on the NEXT call after the window elapses, so the final chunk of every run of gains sat in the accumulator, unseen, until a further gain arrived that might never come. The layer is gone from the XP path and NotificationThrottle.XP_GAIN with it: every gain reports to the progress-bar panel, whose own repaint window (an authored RepaintMs on the panel asset, 250ms by default, leading edge plus a trailing flush) coalesces a burst and paints the last one on its own. Every other throttle type (crit, block, lifesteal, fall, combo, luck, the rewards-waiting reminder) is untouched, and so is the world-luck notice.
• Earning an achievement lists the rewards it earned. Every one of the 153 achievements this mod ships pays through Rewards.Claim, and Ziggfreed Common's earn moment carried the receipt of the immediate grant alone, so the notice read "+10 achievement points" and nothing else while the achievement's own page listed the XP waiting to be collected. The library's Achievement_Unlocked now carries what the earn is worth (the immediate receipt, then what waits), the shape Quest_Parked has always had, and the shipped Achievement_Unlocked.json lists it as rows under its headline. The reading itself was never at fault: ShippedRewardChipsTest drives every reward kind the family ships (Item, Lootable, Droplist, Effect, Stamped_Item, Command in its three shapes, Mmo_Xp for a skill, ALL, every category token and a skill nothing ships a key for, Mmo_Boost_Token, Mmo_Ability_Mod, Currency) through the SHIPPED kind files and the SHIPPED English catalogue and proves each one reads as a real line, the all-skills XP line included - so a kind file pointing at nothing or a lang line dropped fails the build, never a player.
• A reward toast raised after a payout lists what was actually handed over. A quest, achievement, shop or boss payout that rolled a loot table painted one generic "Loot Bundle" row on every toast that followed it, so the player never learned what they got. Ziggfreed Common's grant pass now answers a receipt (RewardGrants.GrantOutcome.receipt(), a Lootable reported as the items it rolled and an empty roll as nothing), and this mod reads it wherever its own toast follows the grant: QuestService.complete answers the outcome of the engine's force-complete and the onboarding page's completion toast paints that receipt through the new QuestToasts.completed(quest, skills, rewards) form; QuestService.tryCompleteQuest answers the outcome of the settle it runs (the engine's new trySettle), so a quest that finishes the instant it is accepted at a conversation or from the book toasts what it paid through the new QuestFeedback.accepted(..., settled) form (the book hands the outcome over on Ziggfreed Common's widened ActionFeedback.accepted); the character screen's hand-in lists the roll through the library's own toast; and the objective book's points-milestone Collect lists its receipt through AchievementService.tryClaimMilestoneRewards (a ClaimReceipt: the result plus what was handed over, over the engine's new tryClaimMilestone), filled into the book's widened MilestoneClaim.tryClaim. A toast lists ONLY what was actually handed over: a quest that parks (a full bag, or it collects somewhere else) has paid nothing, so its completion toast carries the gold headline and no rows, never the authored list (which would show a player items they were not given) - the one rule is Ziggfreed Common's RewardGrants.GrantOutcome.receiptOf, read by QuestFeedback.completionToast (pinned in QuestFeedbackTest) and the onboarding page alike, and the QuestToasts.completed forms that painted the authored list are deleted (only the three-argument completed(quest, skills, rewards) remains). The mod's three shipped FeedbackMoments files (Quest_Claimed, Achievement_Unlocked, Achievement_Claimed) describe their rows as what was paid. The library-side moments (Quest_Completed, Quest_Claimed, Achievement_Unlocked, Achievement_Claimed, Encounter_Defeated), the objective book's and the character screen's Collect toasts, the bounty board's Collect and hand-in toasts and the storefront's bought toast are Ziggfreed Common's own change and list the receipt with no work here. Needs Ziggfreed's CommonLib 2.1.0.
• quest/QuestTitleUtil is deleted: naming a quest is the library's job, whole. This mod kept a second title ladder beside Ziggfreed Common's (titleKey, the quest..title convention, the authored displayName, then the first objective's sentence), and the library's ended one rung short, at the written key, so a key-less, name-less quest - a bounty contract with no Text block, any pack quest shipped without a title - read quest..title on every library surface (the objective book, a character's offer list, the board's "Untitled", a /zigprogress listing) while this mod's own toasts, onboarding preview, map marker and /mmoquestadmin list called it by its first step; a now-deleted toast fill was papering over exactly that gap. The missing rung moved INTO the library (ContentText.title() reads the first step's line the fold already stamps, before the explicit key as written; flavor() gained nothing, it already had every rung this mod's had, and the library's extra "paint the convention key" rung is gone for both), so every surface on the server names a quest the same way and this mod resolves nothing itself: QuestToasts, OnboardingPage, QuestWaypointService, QuestCommand and the book's prerequisite line read ProgressionTexts.titleOrUntitled / title, DefaultContentLocalizationTest reads the fold's own runtime().text() over LangCatalog.overrideForTests fed with this mod's English, and the four-rung precedence QuestTitleUtilTest pinned is pinned in the library's ContentTextLadderTest instead. The @amount / @skill template arguments already rode the runtime object (MmoQuestEngine.textOf), so no key lost its blanks. The one member that was not title resolution, the quest-tag label (ui.quest.tag., else the skill the tag spells), is i18n/Messages.questTagLabelMsg, answering null for a tag this mod has no word for so the book's own tidied fallback applies (the library's ObjectiveBookDeps.TagLabelSource is nullable for that); ObjectiveTextRenderer's qualifier label reads it too and drops its duplicate key probe. With the ladders agreeing, MmoNpcQuestDeps.CompletionToasts and the .completionToast(...) fill are deleted along with the quest-id twin of QuestToasts.completed that only it called; MmoNpcQuestDeps fills the theme and nothing else. The fills that remain each carry something the library cannot know: the theme retint, the menu rail, the statistics column, bounty presentation (the objective book cannot see zc-commerce's board catalogue), the total-level / skill-level / achievement requirement wording, the server-first store, the points-milestone ladder, the feedback.json accept/abandon sound channels, the room pre-check's wording (the engine's tryClaim refuses with null, no reason to word), and the HUD layout file. Ziggfreed Common's hand-in toast also stops painting gold over nothing: a hand-in that parks the quest reads the green "Handed in." line, the gold "Quest complete" line is for a payout.
• A quest that is out of reach says WHY, and one that comes back says WHEN. LockReasons mapped four of the nine QuestGates refusal tokens and dropped the rest onto lock.other, "Not available yet", so a daily finished today, a quest already carried, a spent lifetime cap and a switched-off quest system all read as the same non-answer - and period_spent is the daily case, which makes it the most common repeat refusal in the game. Each token now has its own line in all nine languages (lock.period_spent, lock.max_completions, lock.already_started, lock.system_disabled), and the two clock tokens quote the wait: the come-back instant was already computed by QuestLifecycle.RepeatCheck inside QuestEngine.canAccept, which kept the token and threw the record away, so AcceptCheck carries it as waitMs (the 2-arg constructor kept, QuestEngine.offerableInMs added) and LockReasons gains wait-taking lines/bestLine/line forms beside the token-only ones, which still answer the no-clock twins for a caller with no record behind the token (CommerceRefusals, MasteryPage, ZigBoardPage). The wait is its own translatable wait.days/hours/minutes/under_minute family binding whole numbers as typed {N, number} params, nested into the lock line as its {0}, so each client writes its own digits; LockReasons holds no clock, the wait is always passed in. A repeatable waiting out its window classifies into a new NpcQuestSections.Section.COOLDOWN ("Comes back", between PARKED and LOCKED), leaving Locked to mean what a player already reads it as, a requirement refusing them. The objective book's row readout quotes offerableInMs at both sites instead of cooldownRemainingMs, which reads the ROLLING clock only and showed "Cooldown: 0m" for a daily held by its calendar window. Needs Ziggfreed's CommonLib 2.1.0.
• /mmoability reload hung the server for good, and the same fault waited in ordinary combat and on three admin pages. Every engine asset-store mutator (loadAssets, loadBuffersWithKeys, loadAssetsFromPaths, loadAssetsWithReferences) funnels into AssetStore.loadAssets0, which takes the process-wide AssetRegistry.ASSET_LOCK WRITE lock (AssetStore.java:774, one ReentrantReadWriteLock shared by every store in the JVM) and dispatches LoadedAssetsEvent inside it. World.tick holds that lock's READ side around the whole tick body, both consumeTaskQueue() drains included (World.java:462-485), so every world.execute task, every AbstractPlayerCommand body and every custom page handler runs holding it. A ReentrantReadWriteLock never upgrades: the reader asking for the write lock waits for every reader to release, itself included, and the world thread wedges forever (the engine flags exactly this with a TODO at AssetStore.java:773). Boot was safe only because the asset-load pass runs before any world ticks, and the ~109 writes that take a second there hung the same thread from a command. Six write sites in the jar could reach that state: ImplicitAnchorWrappers.registerWrapper (one synthesized RootInteraction per wrapped ability, ~86 of 97, the reported hang) and OnHitRootBridge.register (~23 OnHit wrapper roots) on the /mmoability reload fold; OnHitRootBridge.ensure, the in-cast lazy fallback for an OnHit child no fold walked, fired from MmoArmNextHit / MmoBeam / MmoDash / MmoProjectile mid-tick; ResistEffectRegistrar.loadEffects from the skill-tree admin pages' revalidateOnlinePlayers AND from SchoolResistReconciler's per-equip bucket generation, which is a world-thread path on every first equip of a new school-resist bucket; StatSubstrateBootstrap's two EntityStatType batches, reached from the config-preset import page through MasteryConfig.load; and SchoolCauseGenerator's leaf-cause batch, boot-only today. All six now write through ziggfreed-common's new asset/AssetStoreWriter (the same shape as the engine's own PathWatcher hot-reload thread, which holds no read lock and is why it can write): inline and synchronous when the caller holds no read hold, so boot ordering is byte-for-byte what it was, and queued on the ziggfreed-asset-writer daemon thread without waiting when it does. /mmoability reload runs its whole re-fold + owner re-read + validation pass on that thread via AssetStoreWriter.offThread and answers the player on their world thread when done (a new cmd.ability.reload.failed line in all nine languages covers a pass that throws); typing it again queues a second pass behind the first. A hit whose OnHit child is not yet registered skips that one hit's payload, queues the root, and the next hit fires it, with one WARN naming the child; a school-resist bucket written off-thread re-runs the player's reconcile on the tick it lands, so the effect arrives without waiting for their next gear change; a stat batch queued from a page exists from the next tick. ImplicitAnchorWrappers publishes a wrapper id only once its root has landed, so the fire path never names a root the store lacks. Durable guard: RepoHygieneTest rule 7 fails the build on any of the five mutators called outside AssetStoreWriter.java, family-wide (// STORE-WRITE-OK: is the escape hatch, zero today), and zc's AssetStoreWriterTest proves inline-versus-deferred against the real ASSET_LOCK. Engine evidence in [[world-thread-asset-store-write-deadlock]]. Needs Ziggfreed's CommonLib 2.1.0.
• Building XP was paid for placements the world refused, once per click. The engine dispatches PlaceBlockEvent and only afterwards decides whether the placement is allowed at all: BlockPlaceUtils.tryPlaceBlock reads the world gameplay config's AllowBlockPlacement (false in the shipped ForgottenTemple and CreativeHub configs) and then, for a non-creative placer, the covering Environment's BlockModificationAllowed (false in the goblin-lair dungeons), returning false WITHOUT cancelling the event and handing the item straight back through onPlaceBlockFailure. Nothing tells the event's listeners, so ziggfreed-common's PLACE_BLOCK producer fired for a block that was never placed: MmoMomentReactions.onPlaceBlock paid BUILDING XP, StatisticsService counted a block placed, any PLACE_BLOCK objective advanced, and the placed-block ledger marked a position the player had not built on, which would then have refused them credit for breaking whatever genuinely stood there. A player in the Forgotten Temple could hold a stack of dirt and train Building forever without a single block going down. The library's PlacedBlockRecorder.placementCounts - the ONE predicate the producer and the ledger writer share - now asks the engine's own two build permissions through the new world/BuildPermission before either counts a placement. Whether the block can PHYSICALLY go in the cell is deliberately still not asked: that is the engine's placement validation, and mirroring it wrong would silently deny credit for ordinary building. Needs Ziggfreed's CommonLib 2.1.0.
• The first quest can be finished at the temple guide, not only the one at spawn. Mmo_Hub_Intro's three temple beats sit in the Start ladder's First band, which outranks the Quests band entirely, so at the temple guide the walk fell to temple_greet / temple_meet / temple_talk and never reached greet - the one node carrying the welcome screen and the Skip line that complete getting_started. A player who found the temple before meeting the guide at spawn had no way to finish it from there. First gains a greet rung at the very top, gated Not QuestState getting_started COMPLETED, so the welcome outranks the temple beats until the first quest is done and is gone afterwards. It changes nothing at spawn, where the Quests band routed to the same node.
• A notice drawn into an open screen kept only its second line. FeedbackEngine sends a moment's toast to the HUD when no page is open and INTO the page when one is, and the in-page build put the moment's Secondary in the panel's one headline slot and its Title in ToastSpec.withTitle - a field ToastRenderer never painted and nothing else read, so the sentence naming what happened was built, handed over and dropped. Finishing the first quest inside the guide's conversation therefore read as +5 achievement points and nothing else. ToastSpec carries ONE headline and a stack of rows: inPageToast keeps the title there, as the corner notice reads it, and puts the secondary in a text-only ToastLine ahead of the reward rows, budgeting the panel for its row and for the RewardToastLines overflow line so nothing lands past the last pre-baked row. ToastSpec.title()/withTitle are deleted with the bug.
• The in-page toast draws the moment's picture. inPageToast passed .withIcon(icon(args)) into the same unpainted-field trap, so an achievement's trophy showed on the corner notice and vanished on the in-page one. ZigToast.ui gains #ZigToastHead, a Left-laid headline row whose #ZigToastIcon cell and gap collapse to zero width for a moment carrying no picture (the centered label then takes the full panel width back, exactly as before), and ToastRenderer.setHeadIcon fills it. ToastSpec.iconPath is renamed iconItemId, which is what it always held.
• A quest's notices are illustrated by the quest. QuestEngine carried no icon on Quest_Completed, Quest_Parked or Quest_Claimed, so only achievements could ever have a picture on a moment; all three carry Quest.icon() under the fixed icon name the feedback engine reads. All fourteen jar quests author a Listing.Icon to go with it (Deco_Scroll for the guide's first errand, Bench_WorkBench for the tool-crafting one, Ingredient_Bar_Copper for the temple's copper, and so on), as do the stations pack's eight. Needs Ziggfreed Common 2.1.0.
• A parked quest no longer tells you which page to open. notify.quest_ready_to_claim ended with "Open the Quests page to claim your rewards." in all nine languages; the rewards waiting list themselves as rows under that headline, so the instruction was restating the panel it was drawn on. The sentence is dropped in every locale, leaving the completion line; notify.quest_inventory_full and notify.contract_ready_to_claim keep their own second sentences, which say WHY a reward parked rather than where to go.

• "Return to the Adventurer's Guide" no longer sits under "Craft a Workbench" as though both were open. The report-back step is one order after the work, and the engine already called it locked; the two screens that list every step simply did not ask. They read QuestEngine.listedObjectives in Ziggfreed Common 2.1.0, which honours the HideLockedSteps the twelve jar quests above author.
• A finished quest waiting to be collected is on the list of the character it is collected from, and nobody else's. A quest that names no collection site may be collected anywhere, which is what most content wants, but it also means a parked one sits under "Ready to collect" at every character in the game: the mastery pack's meet-the-trainer quest was offering itself at Sawyer Marn. Content says where a reward belongs with the quest asset's TurnInAt leaf, and the two quests that are an introduction to somebody now name that somebody, so each is listed at the character it sends the player to. Migration: a quest of your own that parks a reward and belongs at one character wants "TurnInAt": "" (or "giver"); leaving it out keeps the collect-anywhere behaviour.
• A finished quest waiting to be collected is on the list of the character it is collected from. The mastery pack's meet-the-trainer quest is given by the guide and credited by the trainer's own MarkTalked beat, so at the trainer it was neither taken here nor an outstanding hand-in and vanished from "Quests here" at the very character its own comment says to collect it from. The library's NPC quest page asks a fourth question of every carried quest (finished and collectable here); the pack is untouched.
• Picking a conversation line that finishes a quest takes the player to that quest, Collect button in front of them, instead of dropping them back into a menu with no sign anything happened. Only a quest that parked something for collection routes (an on-the-spot payout does not), the route wins over the option's own Goto / Close / Open, and it opens the quest list, never the quest's CompletionDialogue.
• Pressing Collect plays the quest's completion conversation, which is what that authored beat is for: the guide's Mmo_Hub_Intro follow-up plays when the reward lands in the player's hands at the guide, and stays silent from the objective book or out in a field by the shared routing's own rule.
• Reset to Defaults puts the rested-XP flat rate back to 250/hr, the rate the mod ships. The 1.6.0 rebalance from 1500 moved the live field only, leaving resetToDefaults() and the Data DTO default the loader falls back on both at 1500, so pressing Reset to Defaults on the admin page (or loading a skill-config.json with the key deleted) quietly ran rested accrual at six times the intended rate. All three read 250.
• A dialogue Gate condition can answer a Quests prerequisite. MmoDialogueConditions evaluated one against GateSubject.ofSkills(...), a subject carrying the skill component alone; the shared completion probe reads a player's status off the progress record the subject hands over (ZigQuestStore.componentOf, via GateSubject.facet), so a null record read as "cannot tell" and the clause refused for everybody, always. A line gated on a finished quest was therefore invisible whatever the player had done, with nothing logged - the live case being the guide's two temple pointers, at the mastery trainer and at Sawyer Marn, both of which name meet_at_the_temple. The condition builds the whole subject the payload already fetched for this render (skills AND progress, plus the live player and its ref), so a conversation decides a requirement the same way every other gated surface in this mod does.
• A disabled meta achievement naming a disabled child is a note, not a warning. The meta check logged Meta 'X' references disabled child 'Y' - disabling meta at WARN for every meta whose child was off, which shouted about a family an author had deliberately switched off together (the zone-quests pack's orbis_campaigner over howling_sands_campaign, both disabled on purpose). The warning stays for an ENABLED meta naming a disabled child, the contradiction it was written for; a meta that is itself disabled logs the same line at INFO.
• The per-player quest-notification setting decides again which step toasts a player sees. all / milestones / objectives / quests all behaved as all: the grading compared the shared engine's moment id against a name that was close but not the one it fires, so every level except none fell into the "some other quest toast" branch and saw every single tick of every step. The authored quarter marks a milestones player is meant to see, and nothing else, were bypassed with it. The id is the one the engine announces, matched case-insensitively, and QuestNotificationLevelTest pins it against the moment file the shared jar ships so a rename cannot quietly kill the grading a second time.
• The shipped NPC roles' environmental immunity applies. Template_Mmo_Hub and Template_Mmo_QuestGiver asked for Immunity_Environmental under CombatConfig.EntityEffect, a key the engine's role codec does not read (it reads EntityEffects, a list, the spelling the base game's own passive NPCs use), so the immunity never applied and every boot logged an unused-key warning per role. Both templates author the list now, as do the bounty pack's six brokers, the Mastery Trainer, the Kweebec roles and the council example roles.
• Two hub dialogue lines ship whole in every language. The guide's temple brief and mastery brief had wrapped onto a second physical line in the shipped .lang files of nine locales; the engine skips a line with no = as malformed, so each of those sentences was cut in half in game (the English mastery brief included). The second half is joined back with the line break the rich-text renderer understands, and LangFileIntegrityTest fails the build on any non-comment line without = from now on (it only ever checked lines that had one).
• "Server First lost" is said when the race is lost, not every time the player walks through a door. A player who had met the criteria for server-first achievements somebody else already holds was told about every one of them again on each login and on each world or instance entry, and again whenever they opened an achievement screen: six masters claimed by other players read as six lines of bad news about races settled days ago. The loss fires from the shared engine's earn gate, which is asked afresh by the self-heal sweep behind every one of those moments, because a lost claim deliberately leaves the criteria met so the decision can be revisited. The sweep still asks - an admin clearing a claim is how a player wins one back, and the sweep is where they find that out - and the announcement is kept for the occasion the criteria are actually completed on. Needs Ziggfreed Common 2.1.0.

• A claim card says what the ability does, and its CLAIM button stays on the card. An ability-unlock card in the skill tree and a mastery node card read out ChainDescriptionRenderer's walk of the ability's body, qualifier trails and all, in a 280x280 card whose chrome leaves it about seven lines; Vortex Lunge needed ten, so the description pushed the status line and the CLAIM button past the card's bottom edge and the claim was unreachable. Two halves, one per cause: the description region takes the space left after the fixed rows have taken theirs (#RewardDescArea in SkillTreeChoiceCard.ui, #NodeBody in MasteryNodeCard.ui), so no description length can push a card's button off the card, and short text renders exactly as before; and an ability that authors its own description (Identity.DescriptionKey, the ability..desc all 98 shipped abilities carry) has THAT be the card text, the sentence written for a player weighing a permanent tier pick, with the walked summary standing in only for an ability that authors none, rendered without its qualifier trails there so two steps differing only in qualifiers collapse to one counted line. The cooldown/cost line still closes the card either way, and the icon-hover tooltip is unchanged: flavor plus the full numbered sequence.
• The Archmage passive stops whiting out the caster's screen. Staff_Passive_Archmage played MMO_Arcane_Pulse through the native Effects.Particles block, which attaches the system to the caster, and that system composed vanilla Memory_ImplosionEnd with vanilla Memory_Projectile_Core. The second carries InitialAnimationFrame.Scale.X of 60 under ScaleRatioConstraint: OneToOne plus CameraOffset: -0.2, and vanilla references it from exactly one place, Memory_Projectile_Sparks, on a flying projectile - where a 60-unit blue billboard is what keeps the bolt legible at range. Sitting on the camera it is the whole screen, and the passive triggers on HitDealt with Filter: any, so it fired on every staff swing. The ability names its own MMO_Archmage_Arm (vanilla Sword_Signature_Status_Glow plus Potion_Signature_Sparks, then Sword_Signature_Status_Lines 0.08s behind them, all at Y +1.25, LifeSpan 0.8 - the glow-and-rays wreath MMO_Vampiric_Aura already pairs, shortened to read per hit), and MMO_Arcane_Pulse drops the projectile spawner, which fixes the same flash on Magic_Capstone_Arcane_Resonance, whose damage zone plays that system as its 500ms tick.

• The Archmage cue reaches the caster, and it makes a sound. Two things kept the replacement above from reading at all. Effects.Particles is THIRD PERSON only (the engine's own wording: "particles to play when triggering this interaction", against FirstPersonParticles' "while in first person"), so a caster saw nothing whatever the cue's size - the 60-unit billboard only reached them because a billboard that big engulfs the camera from any anchor. And the first replacement was a potion sparkle, a dozen specks a tenth of a block wide for a fifth of a second, which is imperceptible mid-fight; vanilla's own Potion_Signature_Burst is that spawner at the same LifeSpan and offset shape, so it rendered exactly as authored and simply could not be seen. The system is the wreath above, the ability lists it under BOTH particle keys (vanilla Status/Poison.json does the same, one system named twice), and its Effects gains LocalSoundEventId: SFX_Staff_Flame_Consume_Charge_1_Local - a staff charge, caster-only, four random source files so a per-hit cue does not fatigue, and no music-ducking rules, matching the shape the sibling armed-hit passive Arty_Passive_Sniper already authors. BodyMigrationFidelityTest caught both passes against the frozen digest as designed; each was leaf-diffed against its baseline first (the id change was one SystemId string, this pass two ADDED leaves, and no existing value, node or chain edge moved either time) and re-captured in post-wave-fidelity.json, recorded in the fixture's javadoc beside the two prior partial re-baselines. dx-pass-fidelity.json stays byte-identical.

• An objective target is named by the item asset, not by a guessed convention key. TargetNameResolver.itemNameMsg - what a TURN_IN, CRAFT_ITEM, PICKUP_ITEM, BREAK_BLOCK, PLACE_BLOCK, CATCH_FISH or STATION_OUTPUT step reads its target through - probed server.items..name, then items..name, then prettified the id. The engine already answers this authoritatively: Item.getTranslationKey() returns the item's own TranslationProperties.Name and falls back to the server.items..name convention ONLY where that field is unset, and Item.getTranslationMessage() carries the item's NameArguments across with it. The guess is right for a vanilla item precisely because vanilla leaves Name unset, and wrong for any item naming a key of its own, which then read as a prettified id in a step while every other surface in the game showed it correctly. The fix is ziggfreed-common's, per the lift paradigm: NativeNames.itemNameMsg and NativeNames.targetNameMsg ask the asset store first (guarded, so a unit JVM or a pre-registry lookup reads as "no item" and falls through), each gaining a probe-injectable overload, and this mod's itemNameMsg delegates to it while still supplying LocalizationConfig::hasFullKey as the probe so the answer is decided against the same catalog view as every other name on these surfaces. NativeNamesTest gains six ladder cases over the injected probe. Needs Ziggfreed Common 2.1.0, the floor this version pins.

• A mob is named by its NPC ROLE everywhere a server owner names one. Every mob-keyed surface in this mod matched against ziggfreed-common's EntityIdentifierUtil.getMobId, which read the MODEL asset id: mob-kill-xp.json, the combat-XP deny list, kill XP, bonus drops, mob-drop commands and a KILL_ENTITY objective's target were all keyed on a costume rather than on the mob. That passes unnoticed because the vanilla assets mostly name a role after the model it wears, but the two are not the same thing, and where they differ a rule governs mobs nobody aimed it at. The reported case: a server owner wanting a training dummy to train combat skills added the dummy to mob-kill-xp.json by the name the game shows, and nothing happened, twice over - the dummies are roles (Test_Dummy, Test_Dummy_Stationary, Test_Dummy_Damage) wearing the Mannequin model, so the entry matched no mob, and the shipped "Mannequin": 0 row they could not see matched every one of them. getMobId answers the role name now (library change; the model is read only for an entity no role drives), so naming a role in mob-kill-xp.json is what it always looked like it was, and a non-hostile mob given a positive value there awards per-hit combat XP exactly as a hostile one does. Needs Ziggfreed Common 2.1.0.

• An XP award no longer rebuilds the whole leaderboard row. SkillService.awardXp called LeaderboardDataStore.updatePlayer on EVERY award - once per block broken, per craft, per kill, per pickup, per combat hit - and that rebuild reads a level for every skill twice over (getSummedTotalLevel, then the per-skill loop), so roughly 42 calculateLevel calls at ~21 skills. Each of those binary-searched levels 1..200 calling an UNCACHED getXpForLevel, whose hybrid branch loops level-1 times with a Math.pow inside: about 34,000 transcendental calls per award, some twenty times the cost of the award itself, spent entirely to keep a display cache warm. Three changes, none of which moves a number: the hybrid curve is precomputed into a long[201] at the first read and rebuilt only when a curve setting changes (SkillComponent.LevelCurve), so getXpForLevel is an array index and calculateLevel a binary search over it; the leaderboard refresh is throttled per player (refreshIfDue, 10s) with a level-up taking the unthrottled path and finalizePlayer writing the last row on disconnect, which is where the final seconds of a session now land (nothing wrote one on disconnect before, despite the javadoc saying so); and leaderboard-cache.json is written compact rather than pretty-printed. SkillComponentLevelCurveTableTest pins the table against the formula it replaces at every level, bit for bit, plus the band edges, monotonicity, the past-the-table fallback and rebuild-on-setting-change.
• SkillRegistry.allSkillIds() is derived once per change, not per call. It allocated a fresh ArrayList and re-ran insertCustomSkills every call, and isActiveSkill LINEAR-SCANNED another fresh one per ask - so listableSkillIds() was O(n squared) over n+1 throwaway lists, and an XP award triggered it twice. A cached Roster record (ordered list plus an upper-case set) is invalidated by the four mutators that can change it (registerCustomSkill, clear, clearAll, applyPackLayer); isActiveSkill is a set probe, listableSkillIds walks the cached order once, and allSkillIds still hands back a mutable copy because callers sort and filter it in place.
• A server stop no longer logs two SEVEREs from the generated tooltip-label pack. Plugin shutdown unregistered MMOSkillTreeGeneratedLang through the engine, and AssetModule.unregisterPack closes the pack's zip file system BEFORE it dispatches AssetPackUnregisterEvent, so the engine's own listeners (CommonAssetModule, NPCPlugin) answered every stop with a ClosedFileSystemException each. On a server stop the engine closes every pack itself, so the unregister is skipped there (HytaleServer.isShuttingDown() decides, read through the new util/ServerLifecycle); a plugin unload or reload that leaves the server running still releases the zip handle the way it did, since that is the path a stranded handle would fail the next boot's rebuild on Windows.
• A step naming one of this mod's own characters draws that character. A TALK_TO_NPC step is pictured by the shared reading, which points an AssetImage at Icons/ModelsGenerated/.png - a folder keyed by MODEL, where the step's target is a ROLE. Vanilla names most roles after the model they wear, so the gap only opens on a character a mod authored: Mmo_Hub_Temple wears Kweebec_Rootling, and the guide's own id has no still, so "Speak with Adventurer's Guide" drew the missing-icon fallback. Fixed in Ziggfreed Common 2.1.0 (Portraits asks a registered RoleArt for what the role actually wears before falling back to the id); every quest giver, trainer and broker this mod and its packs ship is pictured by it.
• A hand-in that delivers nothing is drawn with the character it reports back to. Turn_In's target is the thing being DELIVERED, so the shared reading pictures a delivery by its item and leaves a bare "return to" step - the one Ziggfreed Common's quest fold (QuestAsset.toDefinition) appends for a quest-level Npc.TurnInId - to whoever hosts the hand-in. That is this mod, so MmoObjectiveIcons answers a targetless TURN_IN with the portrait of the character named on the step's own turnInLockId, the same id its sentence renders; an unresolved giver sentinel and a step naming nobody both keep the text-only row rather than painting the missing-picture fallback. It is the one step with no target this seam answers.
• A step's item picture draws. Ziggfreed Common's icon seam, which every step, criterion and detail line in this mod's screens is painted through, drove an ItemIcon widget the client does not have, so a craft or gather step naming an item - on the giver's screen, in both tabs of the objective book, on a board's contract detail - laid out its icon's width and drew nothing in it, while a creature's portrait drew as intended. The seam paints a one-slot ItemGrid now, the widget every price chip and reward row here already uses. Fixed in Ziggfreed Common 2.1.0; nothing in this jar changes.
• Hookshot Arrow launched a player instead of pulling them. The pull writes the target's Velocity component directly, and the horizontal component was pre-scaled by 25 to cancel a discount the engine applies on its way to the ground. That discount is not applied to every target. Three separate systems drain a Velocity instruction, and only one of them touches the number: an NPC's goes through Role.processSetVelocityInstruction, which zeroes its motion controller and re-adds the vector through MotionControllerBase.addVelocity, cutting X and Z to about 0.044 of what was written, so the 25 brought a mob back to the speed the ability asked for. A player's instruction is forwarded to their own client as a ChangeVelocity packet with no scale, no drag and no cap anywhere in the pipeline, and a generic entity's is written into the component as-is. Both took the 25 literally, so the ceiling that caps the pull at 18 blocks per second delivered up to 450 and threw the player clean off the map. The pre-scale is now resolved per target: a target carrying NPCEntity gets it, everything else gets the clamped speed the ability authored. Mob pulls are unchanged.
• A Crafting XP reward paid Enchanting the same amount. /mmoawardxp, the command every Mmo_Xp reward runs, read its skill token against the four SkillCategory names before the skill roster, and CRAFTING is both a skill of its own and the category Enchanting is filed under - so a quest, achievement, shop offer or loot roll asking for 750 Crafting XP paid 750 into Crafting AND 750 into Enchanting, while the reward line the player read named Crafting alone. Sixteen reward blocks author CRAFTING across the jar (six crafting achievements, two onboarding side quests) and the stations pack; none of the family's content asks for a category, and no other name collides, GATHERING, COMBAT and MISC being categories only. A skill id is read FIRST now, so an exact skill always wins and a category still fans an award out where nothing shares its name; all is untouched, and /setxp and /bulksetxp never carried the branch. The behaviour dates to 1.0.1. Migration: a profile that collected the extra Enchanting XP keeps it, and /setxp enchanting trims one back if you want it exact.

• A targetless step and a total-level step read whole. The seven kept objective-kind files named a Presentation.TextKey, the very convention key the renderer already resolves, and because that rung fired first with only an amount and a target it hid the targetless and total-level sentences on shipped content: "Cast 10 times" for "Cast abilities 10 times", "Reach level 100 in Total" for "Reach total level 100". The leaf is gone from every shipped kind file (pages/render/ShippedObjectiveSentencesTest refuses it), the renderer's kind-file rung gains the .any twin, a new rung falls through to ziggfreedcommon.progress.objective.* once this mod has nothing of its own to say, and two targetless sentences the mod's own kinds lacked are added in nine locales (the same commit as "This mod stops re-wording what the shared library already says", below).

Changed

• Feature ids and statistic counter ids are spelled Is_Like_This, and either casing still resolves. The feature ids this mod declares read Mastery, Abilities, Currency, Xp_Tokens, Command_Rewards, Bounty, Shop, Item_Requirements, Action_Requirements, Taming, Npc_Placements and Stations (their aliases likewise: Active_Abilities, Token_Shop, Hub_Npc, ...), each a constant on MmoFeatures that every Java call site reads; the lifetime statistics read Mob_Kills, Blocks_Broken, Damage_Dealt, Playtime_Seconds, Encounters_Defeated and so on. The jar's own content (Mmo_Hub_Intro, the Spender chain), the Mmo_Counter factor overlay's comment and CONTENT_PACKS.md spell them the same way. A feature id was already matched through the library's one normalization, so a pack that wrote mastery keeps resolving; a counter key is matched without regard to case by Ziggfreed Common 2.1.0's CounterMap, so a save written under mob_kills reads as Mob_Kills, takes that spelling the next time the tally moves, and is otherwise left exactly as it was: no migration, and nothing refused for its casing. The statistics drill-down page and the objective book's stat cards route on the counter constants rather than on copies of the strings. Tests: StatisticsCounterSeamTest (the entity codec reads a lower-case save and re-spells the one key it writes), StatisticsBlobCompatTest (the DB blob captured before the rename still decodes, is pinned to its old spelling, and re-encodes a written key canonical beside untouched ones), MmoFeatureFactorTest (a feature answers under either casing).
• A notice that repeats itself keeps to one line of the seven. The corner feed shows seven entries, an eighth pushes the oldest out of sight, and the engine gives a server nothing to retire one early (the packet carries no duration and nothing in the interface family removes an entry), so the only say this mod has over what a player can still read is how many lines it asks for, and it was asking for a new one every time: a lucky streak while gathering plus a "rewards are waiting" note per level filled the feed and buried the rest. Which line a notice lands on is the CATEGORY's business rather than the call site's: NotificationCategory.feedTag walks to the category's umbrella, so everything one umbrella covers speaks on one rewriting line, and the two "rewards are waiting" popups, which have shared REWARDS since 1.1.7, now share its line too; a currency gain files under its own, so earning coin never wipes a standing note; the rewards-waiting reminder itself is one gate at one a minute, shared by both systems that raise one. MmoNotify's illustrated shapes are withIcon and withItem, matching the names Ziggfreed Common's Notify gives the same shapes, which also settles a real ambiguity between an icon path and a tag.
• A step the quest tracker is already drawing says nothing in the corner feed, and a repeat merges on a tag. The native Notification packet carries a Tag the client merges toasts on, and nothing in the family passed one, so every objective tick and every per-cycle station pickup landed as a fresh entry and buried the feed. A feedback moment authors Toast.Merge (Ziggfreed Common's FeedbackMomentAsset), the station item gains tag per item and per luck row, and a step counting up on the tracker panel is claimed off the feed by that surface (FeedbackSurfaces), so a long sawmill run leaves the feed to the pickups and the finds; the tick that finishes a step still announces. Both are ziggfreed-common 2.1.0 changes this mod consumes.
• No XP notice reaches the corner feed any more. The feed holds seven entries, the engine gives a server no way to retire one, and an entry only expires while nothing new arrives, so one XP notice per second per skill kept the whole feed pinned behind XP for as long as a player kept working. Both XP feed paths in SkillService.notifyXpGain are removed (the station-session coalescing Notify.itemKeyed form and the plain icon-path banner); the method is now the one call onto the shared panel, and the notify.xp_gain / notify.xp_gain.stacked lang keys are retired with it in all nine locales. feedback/XpNotificationStacking (which existed only to choose between those two forms), its "stations" provider registration in RpgStationsBridge, and integration/stations/StationSessionActivity (which existed only to feed that provider) are deleted rather than left as a dead seam; the StationSessionStarted listener stays, because which panel a skill's bar lands on follows whether the player is working a station (see the progress-bar feature above), and the live record it keeps is one map inside StationBridgeListeners.
• The onboarding previews' objective and reward lines are ziggfreed-common's shared detail line. Pages/RewardRow.ui and Pages/QuestObjectiveRow.ui are deleted; RewardListRenderer.ROW_TEMPLATE and OnboardingPage.LINE_TEMPLATE both name the library's Pages/ZigDetailLine.ui (loaded before this jar and merged into the one client UI tree, the way the hub already appends its ZigSelectRow.ui), so a reward on a getting-started preview is the size of a reward on the NPC quest page and a size change is that one file's edit. The selectors move with it (#RewardName and #ObjText are #LineText; the icon shows through IconRenderer.applyItemSlot, tooltip kept, into the line's #LineIconSlot / #IcoItem, and the fallback icon through applyIcon), and the compact variant's font follows the new base (13, three below the line's 16).
• The ability bind page's search is the shared search row. Its field, Search and Clear are Ziggfreed Common's @ZigSearchRow (Common/ZigSearchRow.ui), wired through ZigSearchRow.wire, so the two button words come from the library's own nine-locale ziggfreedcommon.ui.lang instead of English baked into the .ui file; the ability.bind_page.search and ability.bind_page.search_clear keys are gone with them. Nothing binds per keystroke any more: Search submits, Clear appears once there is a query to drop, and every filter, sort and skill-dropdown click carries the field's live text along (ZigSearchRow.carry), so what was typed but not yet searched survives the rebuild exactly as the per-keystroke stash used to keep it. UIUtil.bindTextField and bindSearchDropdown route their key through SettingsUiUtil.directive, which refuses a key without the @ the client needs to resolve the value as an element path; UIUtil.bindDropdown gains an EventData overload for a dropdown whose binding carries more than its action.
• Every admin screen the hub opens is a card. The twelve editor buttons crammed into the Actions block (XP values, rewards, the skill tree, tokens, mob kill XP, mob drop commands, item and tool requirements, custom skills, world rules, power level, plus the two entitlement-gated ones) sit in a second card grid under their own Editors heading, each carrying the icon, title, one-line description and accent bar the section tiles already had, described in all nine languages. Actions keeps only what acts in place: the two reloads, Award Boost and the Danger Zone below it. The page grows to 950x800, the tallest in the admin family, and both grids are SIZED from the tiles they actually draw rather than a hand-counted height, so a card added later cannot spill over the block beneath it and an entitlement-gated card takes its own box with it when it goes.

• This mod stops re-wording what the shared library already says. Three feedback moments (Quest_Completed, Quest_Objective_Progressed, Achievement_Server_First_Lost) shipped a file whose every leaf restated the library's own default, so each was one more copy of a sentence to keep in step across nine languages for no gain; all three are removed and the library's default answers. A step ticking reads exactly as it did, and a quest finishing keeps its wording bar the exclamation mark the library's line does without; a server-first race lost to somebody else is the one that changes wording, to the library's shorter line. Fifty-three lang keys go with them: the objective sentences the shared vocabulary already carries at the same slot (Break {0} {1}, Defeat {0} enemies and the rest of that family), the two glue keys that duplicated the shared one, and sixteen keys nothing reads any more - thirteen that had gone unread for releases, and three the dropped files were the last readers of. ObjectiveTextRenderer falls through to ziggfreedcommon.progress.objective.* once this mod has nothing of its own to say. Nineteen of those sentences are word for word what they were; the rest take the library's phrasing instead ("Consume" where this mod said "Eat or drink", "Hand in" for "Turn in", "Speak with" for "Talk to", "Reach" for "Raise", "Complete quest:" for "Complete", and "Play" for a minigame round this mod called finished, "rounds of" for the parenthesised name it put after); and five kinds that had been dropping their target on the floor name it, so a damage step reads "Deal 500 damage to Zombies" and the breed, feed, harvest and companion steps read the same way. What stays authored here is what only this mod can say - the level channels, the break verb a block's own skill picks (mine / chop / dig / harvest), the report-back hand-in line, and its own step kinds. What a moment file has to earn its place with is unchanged: an argument only this mod supplies, a surface only it has, a chime it wants where the library draws a toast.
• A calendar daily counts as a daily. QuestService.classifyQuestType, the NORMAL / REPEATABLE / DAILY / WEEKLY bucket a "finish N dailies" achievement qualifier matches on, delegates to ziggfreed-common's one cadence rule (QuestCadence, read off the quest's runtime repeat rule): the LONGER of a quest's rolling wait and its calendar window is what a player experiences as "how often", so a quest that resets once a day with no rolling cooldown at all is DAILY (it read REPEATABLE before, because only the rolling cooldown was bucketed), a two-week Every window is WEEKLY, and a legacy flag-plus-seconds quest buckets exactly as before. The twenty-hour and six-day thresholds live on the enum, spelled once for every surface that buckets. A folded shared-schema quest's legacy cooldownSeconds scalar is filled with the same longer-of-the-two reading.
• The stations bridge no longer fires WORK_STATION; RPG Stations produces both station kinds itself. The station engine fires WORK_STATION once per real attended cycle and STATION_OUTPUT once per stack it hands a worker, straight into the shared progression runtime, and ships both kind files and their text templates - so a quest or achievement authored against either advances on a server with no MMO at all. This mod REACTS to those moments in event/MmoMomentReactions (the two station statistics) exactly as it reacts to a craft; its own Work_Station.json kind file is deleted (RPG Stations' is the one that ships), and a second fire from the bridge would have counted every cycle twice. The WORK_STATION and STATION_OUTPUT enum constants stay as fold mirrors, and MmoQuestEngine.register() now skips an id the shared registry already holds, so a kind another mod registered is never re-registered over.
• /mmostation flair grant|revoke|list is an alias over ziggfreed-common's flair write path. Same command name, same --player / --flairId shape, same admin gate, the sender's answers keyed as they always were; every write goes through the library's FlairUnlocks (the /zigflair family's), which announces each real change as a native ZigFlairChangedEvent and draws the Flair_Unlocked notice itself. This mod no longer writes the flair record, no longer marks its player-data seam from the verb (a listener on that event does, for every path at once, see Technical) and no longer sends a toast of its own: the ui.station.flair_unlocked key is retired from all nine languages, and ui.station.flair_refused is added for an id the save format cannot hold. The verb still needs the player online; a reward authored as a reward uses the library's Flair kind, which rides the pending-reward queue for an offline player.
• The shipped mob-kill-XP defaults are re-keyed off model names. Of the 128 patterns, an audit against the shared source's role files found four that match no role: Boss and Elite are deliberate catch-alls and stay; Mannequin becomes Dummy, which covers every training-dummy role whatever it looks like and preserves the row's intent (a dummy is worth nothing until an owner says otherwise); and Scarab is renamed Scarak, the creature's own name. Scarak is already keyed further down the same file at 65 with Scarak_Broodmother at 85, and the later row wins, so Scarak XP is unchanged at 65 and the renamed row does not decide anything. Every other pattern, and every shipped KILL_ENTITY target (Trork, Skeleton, Bear, Boar) and fish pattern, already resolves against a real role name and is untouched.
• A per-target statistic or objective progress recorded before the update keeps its old key for the handful of mobs whose role and model names differ. Nothing is migrated: the two names agree for effectively every mob a player fights, and the ones that differ are dummies and test fixtures.

• A placed block is remembered on its own chunk, not in a file. PlacedBlockLedger kept every placement the server had ever seen in one mods/ziggfreedcommon/placed-blocks.json, and every block break drove its beat: a full scan of every player's every row on the 60s cleanup (plus a second, redundant one from the 30s flush), a full deep copy of the state on the world thread, and a pretty-printed rewrite of the entire file - all proportional to the file, not to what changed, and unbounded because placedBlockExpireMinutes defaulted to never. It is now ziggfreed-common's PlacedBlockSection, a plugin-registered Component holding one bit per block on the block's own chunk section, laid out like the engine's own BlockPhysics (lazily allocated byte array behind a versioned single Codec.BYTE_ARRAY key, leading flag byte so an unmarked section costs one byte). The engine's chunk save carries it, only loaded chunks cost memory, a read is an array index, and no file, scan, snapshot, timer or boot parse remains. Spending a mark still records the position for READ_GRACE_MS so every reader of ONE break is told the same thing - without it the second reader would pay out on exactly the exploit the first refused.
• A builder can be exempted from the guard. PlacedBlockLedger.Policy.guardsPlacementsBy(PlayerRef) decides whether a player's placements are recorded at all; the MMO answers it from PermissionUtil.isPlacedBlockGuardExempt (OP, or mmoskilltree.placedblocks.exempt when permissions are on). This is the case the guard got backwards - somebody standing up an ore vein FOR players to mine - and it is settled at record time, so an exempt placement is indistinguishable from a natural block afterwards. It decides only whether the block is REMEMBERED: the placer still earns whatever placing is worth. Creative placements were already exempt.
• This mod no longer registers a stamper; per-instance item enhancement is ZC-driven. item/MmoStackStamper replaced ziggfreed-common's StackStatsStamper to get the enhancement tooltip, which made the item FORMAT this mod's rather than the library's: a server without the MMO stamped items nothing could read, and two consumers stamping one item would have meant two formats with every budget check reading half the history. The library owns the write, the tooltip (loot.stamp.StampTooltip, the lifted descriptionFor/baseDescriptionKey/hasMarkup with its markup gate) and the equip bridge; this mod registers item/MmoStampPresentation's successor item/MmoStatNames, a loot.stamp.StatNamer answering only for MMO_-prefixed ids and declining everything else, so a stamped Health still reads correctly here. ItemEnhanceDisplay keeps statLineMsg alone. EquipStatBridge.install and its three trigger-system registrations move to the library's EntityBootstrap (a second set would recompute the same stacks twice); MMOSkillTreePlugin reads the installed instance through EntityBootstrap.equipStatBridge() to hang SchoolResistReconciler. ItemEnhanceDisplayTest keeps its composition cases against StampTooltip with the real vocabulary registered; its pure gate cases move to zc's StampTooltipGateTest.
• A weapon keeps its own move on a key an ability is bound to. Binding a slot to an input the held item already uses writes a claim on the player's own Interactions component, and the engine reads that component BEFORE the held item and returns at once (InteractionContext#getRootInteractionId), so the claim did not merely win the contest, it swallowed the key: every signature weapon lost its Ability1 move and the crossbow its Ability3 reload, for as long as the binding existed. Worse where the claim is WIDER than the binding behind it - a claim can only name Ability1/2/3, while a binding distinguishes crouch on top of each, so a slot on ABILITY_3_CROUCH claimed Ability3 whole and an uncrouched A3 press reached a branch with nothing to cast and died silently. The trigger roots now author NativeInput: {Defer, Fallback} on their cast branches and MmoCastAbilityInteraction routes the press: the item wins whenever ziggfreed-common's new interaction.NativeInputGate reads its own chain as opening with a stat cost it can currently pay (a full signature bar, a magazine with room to reload), and the item gets the press anyway whenever the cast does not happen at all, so its own no-ammo or empty-bar feedback plays instead of nothing. A chain that spends no resource - gated only on durability, or on nothing - never counts as ready, since it would win every press forever.
• An NPC placed by any route other than the placement sweep answers press F. The stamp binding an NPC to its placement is attached only by that sweep, so one spawned by a command, an egg, a prefab or another mod carried none: ZigPlacementInteract rendered its interact prompt and then returned false, logging at fine, which reads in game as a broken character rather than an unconfigured one. A base role may now author its own Dialogue or Open on that action as a FALLBACK - a placement standing the NPC still decides - and with no placement the identity comes from NpcIdentities.npcIdOfEntity, so @self and a MarkTalked beat still resolve. Template_Mmo_Hub declares a sixth parameter, Dialogue, defaulting to the hub conversation and bindable per variant; Template_Mmo_QuestGiver answers the same case with a literal Open of Quests.
• Where governs placement and nothing else. The interact path never consulted it; the codec documentation and the shipped Mmo_Hub comment now say so, so widening a selector is only needed to have one PLACED in another world.
• Twelve ability-validation warnings were the audit's own drift, not content. checkDescriberCoverage re-derived the renderer's suppress rules from a hand-synced copy that had fallen behind: it was missing the four condition nodes and the unnamed-cosmetic ApplyEffect case ChainDescriptionRenderer.isPresentationOnlyNode suppresses, and it decided filler by probing for a static ability.summary.native. key even where the renderer describes the node from its own resolved fields instead. So a boot reported NATIVE_NODE_NO_DESCRIBER twelve times over ApplyEffectInteraction nodes the renderer either never prints or prints a named, timed line for. The audit now asks the renderer directly (ChainDescriptionRenderer.rendersOnlyFiller, over the Described.filler flag every describe path already returns), so it reports what the tooltip would actually say; the copies and the parallel key probes are deleted. What stays here is the wording, which still names the exact key an author is missing.
• PRESENTATION_ANIMATION_IMPLICIT_SET is a note. An animation authored with no explicit item-animation set resolves against whatever the caster is holding, which is a supported authoring choice and usually the intended one: Guard Stance, Parry Riposte and Javelin Toss all want the animation for the weapon actually in hand, and naming a set would pin each to one weapon. It cannot be fixed without changing behavior, so it reports what is actually true - the clip cannot be checked at boot, so that standing goes untested until it is played in game.
• An optional mod this server does not run is not a warning. Every adapter for an absent mod answers false from initialize(), which is the ordinary case, and it was logged at warn level twice a boot (setup, then the deferred re-resolution on first connect): a server with two of the nine optional integrations installed took fourteen warnings for working exactly as intended. It logs at fine now. The adapter still names the absent mod at info, the domain's own no-active-integration line closes the trail, and the resolution summary repeats the whole chain. An adapter that THROWS still warns, since that is a real failure.
• The gate vocabulary no longer warns that it overwrote itself. GateFactors seeds the portable Hytale vocabulary into its registry and then deliberately answers five of those ids off saved records, which the ledger reported as 'hytale:stat' was registered by 'MMOSkillTree' and is now overwritten by 'MMOSkillTree'. Those five use ziggfreed-common's new FactorRegistry.registerOverride; an id this registry does not already hold still warns.
• Legacy_Quest_Fishing's icon is an item. It named Fish, which is a resource TYPE and not an item id, so the audit reported ICON_UNKNOWN_ITEM on every boot. It is Fish_Bluegill_Item, the icon the fishing reward kinds already use.
• The guide points a temple visitor at the sawyer, and five of his lines are reworded. The temple's steady-state screen of Mmo_Hub_Intro carries one more question beside the mastery pointer, about the character with the hatchet across the landing. It shows only when the shared quest catalogue holds a quest called timber_rights at all (the library's ziggfreedcommon:quest_known factor, never a pack name, so a server without the stations pack never sees the line), the station engine is running (mmoskilltree:feature / stations, so the guide never points at a character who is not standing there), the temple meeting is claimed and that quest is untaken; picking it says who Sawyer Marn is and where he stands, and its own accept takes on the pack's introduction to him, meet_the_sawyer, so the player walks down with an errand to say hello rather than a timber run they have not been asked for; the second line simply goes back, and his own chain, Timber Rights first, he offers himself once the player has stood in front of him. The gate reads meet_the_sawyer throughout, so a server whose stations pack predates the introduction never sees the line at all. Five hub lines are reworded in the guide's own register, each saying what it said before (combat_to_ranks, ranks_brief, menu, bounty_intro and the starter-tools quest flavor).

Technical

• player/ProgressStateMigration claims on the first pass whose leaf families all wrote. Result is MIGRATED / ALREADY / UNFINISHED / NOTHING, with wrote() saying whether the record changed; UNRESOLVED is gone, because a claim withheld for an unanswerable achievement was a claim withheld forever on a server missing that pack, and PlayerReadyEvent fires on every world entry. The unanswerable ids are named once (unresolvedNotice) and left under their saved keys. New player/AchievementKeySweep runs from PlayerReadyFlow right after the move, every ready, over the shared record alone: any # (or bare ) key the catalogue can now answer for moves onto #, first writer wins where the target already holds a tally, the positional key is removed through Ziggfreed Common's new ZigProgressComponent.clearAchievementProgress, and a key it cannot answer for (or whose index the definition no longer has) is left alone, so a ready with nothing positional costs one pass over the keys and no write. Both share ProgressStateMigration.rekeyed, which now tests a numeric suffix with a digit scan instead of a parseInt and a caught exception per named key. The move gains a ContractBoards seam beside CriterionKeys (Posting: not a contract, posted at a site, or a contract no board posts), answered live by MmoBounties.isBounty and the new MmoBounties.postingSiteOf (the first DECLARED board a contract is posted on, spelled as BoardAssetSpec.boardId() spells it, which is what BoardEngine.accept records); a posted contract's payload is re-packed through QuestProgressPayload.serialize(deserialize(legacy), site) with a site the payload already records kept, and a retired contract skips the status, payload, cooldown and pin leaves while its completion record is carried (the survivor ZigProgressComponent.clearQuest keeps), named once by droppedNotice. PlayerReadyFlow marks PROGRESS dirty when the move wrote or the sweep moved anything. PlayerConnectFlow drops its Citizens branch: it called QuestConfig.load() whenever daily_npc_greeting was absent, a quest the deleted Java defaults used to generate and nothing ships now, and load() is a full republish of the shared catalogue, so on a server with the Citizens integration on it would have re-resolved every quest at every connect for a quest that never appeared; a quest that wants an integration present says so in its own Requires block. Ziggfreed Common's progress record reads a quest id under any casing and re-spells it on the next write (its own changelog), so a pre-1.6 owner quest authored My_Quest keeps its saved states after the converter keys the file my_quest. Tests: ProgressStateMigrationTest (the claim-once rule replaces the claim-withholding case, the throwing pass, the three contract answers, the stamp), new AchievementKeySweepTest, and new ProgressionUnclaimedMoveTest over fixtures/progression-unclaimed-move-1-6-0.json, the three progression components of the player file attached to the September owner report, decoded through the real codecs: one pass spends the claim and an administrator's reset survives the next, the contracts collect at their board and nowhere else through the real QuestEngine.canCompleteAt over ZigQuestStore, a retired contract is dropped and named, the positional taming keys re-key once the catalogue answers, and a throwing pass still does not claim. Needs Ziggfreed Common rebuilt.
• Adds migrate/LegacyQuestConverter, the ONE reader of the older quest format, and deletes quest/SharedQuestWriter. A legacy quest body in (an owner-file entry or a LegacyQuestAsset payload, camelCase or PascalCase, every polymorphic shape QuestConfig.normalizeQuestBody accepted, which moved here whole as normalize), the extends/params/objectiveOverrides/extraObjectives DSL resolved first through config/template/QuestTemplateResolver (a missing template is a Refused outcome naming it and the loaded templates, never a skipped entry), ONE QuestAsset body out plus per-quest Notes (dropped, warnings, preserved), every body proven by decoding it through QuestAsset.CODEC before it is handed back, and a refused body reported, never written. It closes the gaps the writer never did: Indicator at quest and step scope, TurnInAt, HideLockedSteps, a structured requires block merged with the flat leaves (flat factors first, quests deduped case-insensitively, the permission carried), requiredAchievements, the report-back rule (emit Npc.TurnInId verbatim and never a turn_in step, since the fold adds the step), autoClaimRewards selecting the Auto / Claim bucket, repeatable + cooldownSeconds + resetsOnComplete as the Repeat group, tags as Listing.Tags, category / sortOrder on Listing, the convention keys quest..title / .flavor as the Text defaults with titleArgs / flavorArgs as TextArgs, npcRequiredToAccept as Meta.mmoskilltree.NpcOnly, an authored boolean carried as authored (false included, since the owner folder merges leaf by leaf), and visibility mapped to the shared knobs (RequirePrerequisites, a ShowWhen from the level floors or the permission node, never Listing.Hidden). Rewards are read by the live RewardJson reader with RewardSpecs' dialect, objectives by ObjectiveSpec.CODEC, gates by GateJson.parse, and the shared spellings are written by content/SharedSchemaJson (whose reward Params keys carry the documented spelling, Skill / Amount / CurrencyId). An unknown key rides through verbatim and is named, never dropped in silence.
• QuestConfig reads no file and models no quest. load() is ProgressionDefaults.republishAssetContent(), a republish of the shared store; loadUserQuests, loadFile, parseQuest, normalizeQuestBody, setQuestsDir, mergeCommonQuestLayer, the pack-layer merge, the template plumbing and the consumer-rank publish are gone, and every method left is a projection over ProgressionDefaults.questPool() (getQuest / getAllQuests / getDefinition / getQuestsByNpcId / getQuestsWithTurnInAt, categoryOf defaulting to misc, isNpcOnly decoding MmoQuestMeta once per published pool). asset/LegacyQuestLayer owns the retired pack store: AssetMergeHandlers.onQuestTemplateAssetsLoaded / onQuestAssetsLoaded hand it the live layers, it converts each payload, calls QuestAssetStore.mergeContributed and then ProgressionDefaults.republishAssetContent(); reapplyQuestPackLayers (the /mmoquestadmin reload path) does the same. config/LegacyQuestOwnerMigration runs from OwnerConfigBootstrap beside the other Legacy*Migrations, before the runtime builds, per file all or nothing (LegacyOwnerFile.renameInPlace is extracted for its .legacy rename), and also retires the _defaults/default-quests.json echo that QuestConfig.load() used to; its target folder is QuestOwnerLayers.folder(), so a test points both ends at temp directories.
• The MMO's quest model is deleted; the engine's Quest is the one object every surface holds. quest/QuestDefinition, quest/CommonQuestFold, quest/QuestVisibility, content/objective/Objective and content/objective/ObjectiveLevelSugar are gone, with MmoQuestEngine.publish / toRuntime and their helpers (effectiveRequires, textOf, repeatOf, composedLine, def). Every reader (PlayerQuestCommand, QuestCommand, ConfigPresetService, the dialogue actions and quest reader, MmoPlacementValidator, OnboardingPage, MmoObjectiveBookDeps, ObjectiveTextRenderer, QuestFeedback, QuestToasts, MmoBounties, MmoQuestListeners, QuestService, QuestValidator, QuestWaypointService) holds ziggfreed-common's runtime Quest, its ObjectiveDef or its folded quest/asset/QuestDefinition record, reached through QuestConfig's projections; a step's sentence and picture read the AUTHORED pair (ObjectiveDef.authoredKind() / authoredTarget()) while the engine dispatches on the run pair. MmoQuestEngine.register() registers REACH_LEVEL (value-based, not producible) as an alias of STAT_THRESHOLD with SkillLevelChannels::channelFor rewriting the target onto its level channel, registers the two MMO axes into ProgressionRuntime.questAxes() (MmoQuestAxes.registry() returns that one registry) and publishes NO quest layer; Server/ZiggfreedCommon/ObjectiveKinds/MMOSkillTree/Reach_Level.json is the kind's file. QuestService keeps policy only: isQuestVisible is the NPC-only-not-started rule and then QuestEngine.isVisible (the shared listing rule over available(), Listing.Hidden, ShowWhen and RequirePrerequisites), canAcceptQuest the NPC-only rule and then QuestEngine.canAccept; passesContentGates, passesPrerequisitesWithoutState and findObjective are gone. MmoQuestMeta keeps NpcOnly alone and names the Requires.Factors replacement for a Feature key. QuestValidator audits the shared pool (QuestPoolValidator with this mod's npc-declares probe, QuestIndicatorValidator, the library's questLoadFindings(), and UNKNOWN_FEATURE over the lifted feature list); VISIBILITY_NOOP / VISIBILITY_GIVER_GATED are gone with the leaves they judged (the converter's notes name a legacy visibility node that gated nothing). AchievementDefinition.toRuntime applies the same shared alias, CommonAchievementFold.addCriterion reads the authored pair, MmoBounties answers by quest id only, and ZoneScopeIndex recomputes off the engine's index. Tests: ShippedQuestContractTest, ReachLevelAliasTest, SkillLevelChannelsTest and a package-private quest/QuestFixtures are new, CommonQuestFoldTest and ObjectiveLevelSugarTest are deleted with their subjects, and the rest are re-expressed over the shared model. The headless boot publishes every quest from ziggfreedcommon alone, with no "both publish the quest" line and an audit of zero errors. The ACHIEVEMENT side still runs its own fold and twin (achievement/CommonAchievementFold, the MMO AchievementDefinition), so the boot log's "both publish the achievement" and milestone warnings are real and stay as the honest signal until that fold is retired the same way.
• /mmomigrate and the web converter agree on the new rows. BootHandled gains a FOLDER rule (isOwnerQuestFile, OWNER_QUEST_FILE_DETAIL, OWNER_QUEST_RESIDUE_DETAIL mirrored by families/progression.ts and pinned from both suites; canonicalNameOfResidue answers quests/x.json for the renamed file), MigrationClassifier files an owner quests/**.json as boot-handled, its .legacy residue and a pack Server/MMOSkillTree/Quests/ file as jar-handles-it (LEGACY_PACK_QUEST_DETAIL), and BootHandledCoverageTest learns renameInPlace call sites and folder tokens. The web convertQuestBody performs the same mapping (visibility, Lore, Indicator, TurnInAt, HideLockedSteps, a structured requires block, authored booleans, the disable stub as {"Enabled": false}), routes every mods-folder quest to mods/ziggfreedcommon/quests/.json, moves a shared-shape owner file across as it is, and reports a quests/.json.legacy as boot's own leftover; pack zip quests are unchanged, and the converter page says so.
• Tests: quest/QuestCodecDecodeTest is re-targeted as migrate/LegacyQuestConverterTest (every case kept, asserted on the converted body and on the shared QuestDefinition it decodes to, plus the new gaps); adds migrate/LegacyQuestCorpusTest (every legacy quest fixture in the migration corpus converts, decodes and folds) and config/LegacyQuestOwnerMigrationTest (temp folders through QuestOwnerLayers.setDirectory: the ordinary move read back by the shared store, the idempotent second run, a sub-folder, a refused file left whole, an existing target never overwritten, an unreadable file named, a shared-shape file moved byte for byte, the echo retired); SharedLayoutExportTest's quest fixtures ride the converter and buildPackEntries takes the owner bodies by id; QuestNpcAliasTest builds its legacy quests through the converter. The in-game help page's quest card (ui.help.quests.how, nine locales) names the new folder.
• Mmo_Hub_Intro's temple pointers find their screens by tag, and its footer includes its tail. The temple_pointers group carries "On": {"Tags": ["Temple_Landing"]} and the three landing screens (temple_talk, mastery_brief, sawyer_brief) carry that tag, so none of them names the group any more and a landing screen added later gets both pointers by carrying the tag; hub_footer writes its two quest lines and "Include": ["open_menu"] instead of restating the temple line, so that twelve-line option exists once in the file. What a player sees is unchanged: the pointers still sit above the footer on every landing screen (Ziggfreed Common 2.1.0 splices a placed group after a screen's own lines and before the groups it names), pinned label by label in Ziggfreed Common's DialogueAuthoredFixtureTest over a mirror of this file. Needs Ziggfreed Common 2.1.0.
• pages/render/MmoChipReading keeps only what no kind file can say. The all-skills XP branch is gone (the kind file's own template lands Skill: ALL and the four category tokens on the shipped reward.xp.all / reward.xp. family, so reward.line.xp_all retires from all nine locales), the /give branch is gone (Ziggfreed Common's item form now reads a Command reward's give line through the same CommandRunner.readGive the fit probe uses), and the ability-mod icon is read off the Mmo_Ability_Mod kind file instead of a Java twin (ABILITY_MOD_ICON is deleted). What stays each carries its reason: a custom skill's XP line off the skill REGISTRY, the boost sentence (a key family of differing arity), an ability-mod title out of AbilityModCatalog, and the /mmoboost give line plus the neutral label for a command nothing parses (this mod's policy over the library's drop rule). The /mmoboost give reader moves off the command class into boost/BoostGiveLine (a RewardPreviewBuilder, MmoChipReading and ValidationChecks share), so a chip, a preview and the audit read a line with no server, and the RewardSpec command reading is a live test instead of a code-inspection note. ShopEntryIconResolver derives an offer card's icon from the shared chip reading rather than a per-kind ladder of its own, so an all-skills XP offer with no explicit icon now shows the crystal every other surface draws it with.
• The RPG Stations api pin moves to 0.8.0 (contract 8 fires StationOutputProducedEvent once more per grant pass, for the paid stacks; the stations bridge does not listen to that event, since the engine's own dispatch already carries the moment into the runtime the MMO reacts on). The manifest's Ziggfreed:RpgStations bound is unchanged; RPG Stations 1.0.0 ships beside this version, so the bridge is live from the first boot on a server that installs it.
• Adds player/FlairPersistence, the flair twin of ProgressPersistence: one listener on ziggfreed-common's ZigFlairChangedEvent, registered once from quest/ProgressionBootstrap, that marks the STATIONS domain dirty and flushes it for the player the event names. PlayerDataRepository gains a markDirtyAndFlush(PlayerId, domain) overload (the PlayerRef one delegates to it), the shape a listener holding a uuid picks. FlairPersistenceTest drives it against FakePlayerDataRepository, whose sessions now remember the domains their last flush() committed.
• SharedSchemaJson.durationGroup decomposes a duration into Weeks before Days, so a fortnight is {"Weeks": 2} wherever one is written (a legacy cooldownSeconds becomes the Repeat group's Cooldown that way). The two runtime-Period test sites move to Reset.daily() / periodMs() with their assertions kept.
• MmoMomentReactions gains one station reaction for both kinds, gated on a payload being present (the station payload types are RPG Stations' own and are not linked); StatisticsService maps STATION_OUTPUT to station_items; TargetNameResolver and ObjectiveTextRenderer know the new kind.
• Tests: i18n/LangFileChecks is the one set of .lang rules, extracted from LangFileIntegrityTest (which keeps its cases and adds balanced / pairs on the dialogue.* family) and shared with the new PackLangFileIntegrityTest, which walks every checked-out pack's Server/Languages//*.lang against that pack's OWN en-US (skipped when no pack is checked out; the deprecated translations pack is excluded). DialogueContentResolutionTest discovers every pack's Server/ZiggfreedCommon/Dialogues/** (the unreleased/ folder and the translations pack excluded; the quartermaster shape test stays pinned to zone-quests-pack). ObjectiveKindVocabularyTest pins that every producible kind has an objective.text. template in en-US and that each RPG Stations kind file agrees with the enum's flags (skipped when the sibling is absent). QuestServiceClassifyTest covers both authoring shapes and every threshold edge, ShippedQuestContractTest folds a calendar daily and an Every {Weeks 2} window through the shared fold to their classification, and StatisticsBlobCompatTest asserts the fourteenth field decodes empty off the untouched golden blob.
• Adds dev-server.ps1, a headless boot-check of the built family on the installed server: it stages every built jar and pack zip (plus the live Mods folder's third-party companions) into an isolated run/mods/, boots with no client, waits for the Hytale Server Booted! banner, confirms every staged plugin and pack loaded, sorts SEVERE / WARN / stack traces into family and engine, can type console commands, stops cleanly and exits 0 or 1 (run/last-check.json keeps the verdict; -ValidateAssets runs the engine's own validate-and-exit pass; -Jdwp opens a debugger port). Adds doctor.ps1, a one-screen environment diagnosis (JDK, install and version pin, HYTALE_MODS_DIR duplicates, submodules, shared source, pinned jars, built artifacts), and tools/dev-env.ps1, the resolver both share. The first boot found the two split dialogue lines above, a third-party mod broken by server 0.6.3, and an engine ordering bug on pack unregister at shutdown.
• build.gradle and api/build.gradle fall back to com.hypixel.hytale:Server: from the public maven.hytale.com when no launcher install exists at hytaleHome (the published jar is byte-identical to the installed one), so a fresh clone or a CI runner compiles; the installed jar keeps precedence, and the doctor warns when the pin drifts from it.
• MMOSkillTreePlugin.setup() is an ordered call list, not a 2,000-line body. Splits the plugin's boot wiring into per-domain bootstraps on the existing AbilityModBootstrap / DbBackendBootstrap / StatSubstrateBootstrap precedent - config/OwnerConfigBootstrap (the two owner-config phases), content/reward/CommerceBootstrap, dialogue/DialogueBootstrap, quest/ProgressionBootstrap, asset/AssetTypeBootstrap, boost/BoostBootstrap, integration/IntegrationBootstrap, ability/AbilityBootstrap, interaction/InteractionBootstrap, command/CommandBootstrap and event/SystemBootstrap (component types + systems) - and the four inline player/world lifecycle handlers into player/PlayerConnectFlow, player/PlayerReadyFlow, player/WorldLifecycleFlow and player/PlayerDisconnectFlow. The anonymous placed-block policy and the granted-ability-mod producer lambda become the named world/MmoPlacedBlockPolicy and ability/GrantedAbilityModProducer, and the debug asset dump moves to util/AssetDebugDump. Every moved body is verbatim and the boot order is unchanged; the in-method ordering constraints are restated at the setup() call sites, so a leg that adds a config, command, page or system edits the owning bootstrap instead of the plugin file (2,799 lines down to under 500, 270 imports down to 49).
• RepoHygieneTest now guards the plugin file's shape as well as its content. Two new rules hold MMOSkillTreePlugin.java to the wiring-root discipline the split above established: the whole file stays under a 700-line ceiling (roughly 1.5x its post-split size, stating the current size when it trips), and setup()'s own body stays free of decision control flow - the same for/while/do/switch/else/non-guard-if/non-null-default-ternary lexicon ziggfreed-common's RootRegistrationOnlyTest uses over its own wiring root, try/catch and guard-if carved out the same way, escaped by a // ROOT-LOGIC-OK: marker (reason mandatory) rather than silently. Nothing else stopped a later leg from inlining straight back in.
• SkillComponent stops growing at 2,692 counted lines (BUILD-ENFORCED). RepoHygieneTest holds data/SkillComponent.java to that ceiling, so a new bit of per-player state is a codec-persisted component of its own in its domain package (ziggfreed-common's HudPreferenceComponent and ZigFlairComponent are the shape: one component, one PlayerDataDomain, one persistence listener); a member that genuinely cannot live anywhere else is headed by // SKILL-COMPONENT-OK: , which exempts that one member from the count. Moving fields OUT needs no marker.
• The build and the boot check both read the .ui files the server never will. A malformed Custom UI document reaches a client because nothing in the pipeline looks at one: the server treats a .ui as an opaque path and ships it, the engine's validate-and-exit pass walks only the registered codec asset types, and the failure lands on the first player to join (the client refuses to load and the server logs a cancelled join). RepoHygieneTest sweeps every .ui in this jar and in every sibling mod for illegal element ids (a letter followed by letters and digits; an underscore ends the parse and fails the whole document) and unbalanced braces, and dev-server.ps1 reads the archives it staged under run/mods and refuses to launch on the same two faults, which catches what a source-level test cannot: a third-party companion, a reused -Stage:$false directory, a build output that drifted from what produced it. The test task declares the sibling mods' sources as inputs, so editing a sibling and building here no longer leaves :test UP-TO-DATE with every family-wide sweep silently skipped.
• hytaleServerVersion reads 0.6.4, the version the installed jar reports (the pin had said 0.6.3, so a machine with no install compiled against a different server than this one runs, and doctor.ps1 had been warning about the drift); the shared-source checkout moves to the 2026-09-07 sync. Verified on the fresh-clone path: compileJava against com.hypixel.hytale:Server:0.6.4 from maven.hytale.com builds with no install found.
• The displaced root is read off the item's own interaction map rather than through the context, which answers with the player's claim; the injected trigger roots are recognised and skipped so a press can never route back into the node that fired it, and a carried block is skipped because the engine reads a separate carry map there. WaitForDataFrom is deliberately unchanged - the node has no Next for an outcome to gate, and the item root it may fire arrives as its own synced chain, so waiting would stall every ability press for nothing.
• RepoHygieneTest's number rule caught the coordinate readback in /mmonpc place; it carries a // NUMBER-OK marker as an all-English operator console line, which is the case the escape hatch exists for.
• MmoRoleTemplateParameterTest asserted one parameter set across both role templates, which is no longer true of either. The expectation is per-template rather than loosened, so each stays exact.
• ObjectiveKindVocabularyTest guards the other direction too: every built-in kind the shared registry seeds must have an ObjectiveType row here, named by id when one is missing, because the folds drop a step of a kind this enum lacks with nothing but a boot line. StatisticsComponent gains a PerEncounterDefeated breakdown field beside the twelve; an older blob decodes with it empty, and the golden-fixture test is untouched.
• The placed-block move needs ziggfreed-common rebuilt and reinstalled alongside the jar: the Policy interface drops strict()/blockExpireMinutes() and gains guardsPlacementsBy, and PlacedBlockSection must register on the chunk-store registry BEFORE any world loads (PlacedBlockBootstrap.setupPlacedBlockLedger, ahead of the recorder). A registration failure leaves the type unset and every read answers "not placed" - the wrong answer, but the safe one, since the alternative refuses every break on the server.
• PlacedBlockLedgerTest is replaced by PlacedBlockSectionTest (11 cases: bit-per-block including both ends of a section, spend-clears, lazy allocate and release, clone isolation, and the serialize/deserialize round trip a chunk save and load puts it through). The ledger's BLOCK path now needs a live world and a loaded chunk, so it lands in in-game smoke like the rest of the ECS plumbing; PlacedGuardProducerTest keeps its item half fully asserted and its two block cases are gone. A bare unit JVM cannot drive the engine's chunk save and load, so that round trip is an in-game check rather than a test here.
• Twelve pieces of provably dead code are gone, each re-verified by grep at delete time: integration/JarClassIntrospector, integration/PluginDetector, integration/PluginIdDump (zero-caller private-ctor classes), pages/render/PinIconRenderer, config/AbstractPackLayeredOverrideConfig (zero subclasses; its one javadoc mention in content/gate/GateFactors now names MasteryConfig#applyPackLayer, where a track id is actually folded to lower case), reward/effects/ComboFinisherEffect and its unused import in reward/RewardEffectRegistry, four unreferenced .ui files (AbilityPickerRow, CombatStatRow, RewardItem, RewardTierRow), and MMOSkillTreePlugin's runSync(Runnable) and equipStatBridge() getter (the equipStatBridge field stays; the getter's javadoc claim that CombatDamageEventSystem's DOT branch reads it was false).
• Four names line up with the rest of the tree: command/MMOConfigCommand is MmoConfigCommand (the /mmoconfig command name and every subcommand are unchanged), io/AbilityInteractionInjector moves into ability/ and the emptied io/ package is gone, util/MmoFactorContributions moves beside content/gate/GateFactors, the vocabulary it is the other half of, and pages/render/SkillDisplayUtils is SkillDisplayUtil.
• ability/ is seven subpackages, not 76 files at one level. Pure package moves - no class renames, no behaviour change: cast/ (the activation and dispatch pipeline), input/ (which key, slot and item fires what), modifier/ (the per-cast modifier framework, its sources and its read side), effect/ (stateful runtime an ability spawns), damage/ (schools, causes, damage sources, attribution), catalog/ (everything that reads the whole authored catalogue) and util/ (stateless helpers), beside the pre-existing event/; the package root keeps only AbilityBootstrap. Six members widen to public, each javadoc naming its cross-package caller (ChainDescriptionRenderer.composeLine, HitDamageBonus.DISPLAY_CATEGORIES plus its fixture family, SchoolCauseGenerator.ABILITIES_DIR and installForTest, and the AbilityJsonFixtures test helper, which stays at the test-package root); the 49-test package moves with its subjects, and AbilityModifierService.classifyProducerClass keeps its mastery./skilltree.-only FQN match, pinned by ModifierSourceAttributionTest.
• ToolStatDescriptionGeneratorTest is replaced by item/StatLineFormatTest (the composition and Utility-map-resolution cases go with the deleted path; the parser, formatter and color cases are kept as they were). StatTooltipLangGenerator.labelFor, whose only caller was the deleted generator, is gone too. ziggfreed-common's StampTooltip drops its .description.base branch, so a stamped item always nests its own description key when the catalogue has it and it carries no markup; that jar needs rebuilding alongside this one (no separate version bump: it rides the 2.1.0 this cycle pins, and the public apply signature is unchanged).
• The hyDungeons bridge is deleted. integration/dungeon/{DungeonIntegration,ProvingGroundsRegistrar,ReflectiveDungeonBuilder} and command/ProvingCommand (/proving, /pg) are gone with their boot wiring: they reached a separate, never-shipped dungeon engine over reflection and registered one ungated, empty arena nothing could enter. Instanced content builds on Hytale's own Instances builtin through ziggfreed-common's instance layer instead, and bosses on the Update 6 EncounterManager.

[1.6.0] - 2026-08-31

Held. The 1.6.0 work is landed and gradle.properties reads 1.6.0, but nothing ships until the combined in-game smoke pass clears. Landing is not releasing.

Breaking changes

• 1.6.0 requires a Hytale Update 6 (0.6.x) server, with updated content packs to match. The jar's manifest targets >=0.6.0-pre.13 <0.7.0, so it does not load on an Update 5 server. Every pack this project ships is already rebuilt for Update 6; an older pack zip still carrying the retired usable-block flag still loads, with one harmless per-asset warning in the server log (/mmomigrate and the web Migration Converter both point at the exact line to delete).
• mods/mmoskilltree/abilities.json is retired (hard break). The legacy JSON-blob ability override format is not read at all. On first start after upgrading, LegacyAbilitiesFileMigration runs at plugin setup (before the asset pipeline exists), moves any file found at mods/mmoskilltree/abilities.json to a timestamped file under mods/mmoskilltree/backup/, and logs a warning naming the replacement. It never reads the file, never deletes it, and never overwrites an existing backup on a repeat restart. Re-author customizations as ability-overrides.json entries (a partial per-leaf overlay) or as a content-pack Server/MMOSkillTree/Abilities/*.json asset; the server-wide ability toggle plus dodge/counterattack timing moved verbatim to the new ability-settings.json. config/ActiveAbilitiesConfig.java is deleted.
• The shared progression schema hardens before its first release (hard breaks made inside the 1.6.0 surface before it shipped; no public content authored it yet). An achievement's Criteria is a MAP keyed by criterion id, exactly like a quest's Objectives: the key is what progress is stored under, a Parent child retunes one criterion by key and keeps the rest, and re-authoring a file can never silently re-point a player's tally (the old positional array made any insert or reorder a data migration). Every progression schema pays through ONE Rewards group with two buckets - Auto lands the instant the content settles, Claim waits to be collected - replacing an achievement's Rewards/ClaimRewards pair and a quest's Flow.AutoClaim switch: a quest with anything in Claim parks for the player, one paying only Auto settles on the spot, and the point milestones already speak exactly this shape. A quest's Visibility group folds into the shared Listing (Hidden, RequirePrerequisites, now on achievements too, where hidden-until-qualified is honored by the shared engine), quests gain Listing.Icon, and an NPC placement's Requires.Conditions is spelled Requires.Factors, matching the requirement block everywhere else. All 167 jar achievements, 10 jar quests, 5 milestones and the shipped pack content are rewritten in place, behavior-preserving; /mmomigrate's exporters emit the new shape (a converted legacy pack keeps its positional progress keys, so deploying an export starts nobody over).
• Objective matching is ONE forgiving rule for every kind of content (a deliberate reversal of the earlier both-dialects position, taken while nothing shipped depended on the strict one): targets compare case-insensitively, an empty target matches everything under every mode, and an empty qualifier matches only an unqualified event. Quest targets become strictly MORE permissive (no content can lose a match), the two jar quests that leaned on the contains-empty-string accident now mean match-all in so many words, and the per-engine MatchFlavor knob is deleted end to end.
• DEAL_DAMAGE counts damage, not hits, and both damage statistics record the same unit. The combat dispatch fires the real post-mitigation damage of each hit as the amount, so a criterion authored "50,000" means fifty thousand damage - the unit its numbers were always written in. damage_dealt and damage_taken are both recorded at the same pipeline stage with one rounding, each totalling the HP a health bar actually lost, so the two lifetime numbers can be compared. The five shipped criterion amounts (10k/50k/100k/250k/1M) stand as authored: the unit fix realizes them (retune factor 1).
• Scoring.CountsTowardTotal is the ONE does-not-count switch. A feat of strength no longer forces it silently: feat is a LISTING treatment (its own earned-only shelf, unpinnable, hidden until earned) and the 16 shipped feat files author CountsTowardTotal: false beside the flag. /mmomigrate writes the leaf out for a converted legacy feat, keeping the totals its pack was balanced around.
• A custom skill id may not contain | or : (refused at every registration point). The per-player save format packs the custom-skill maps with exactly those delimiters and no escaping, so such an id would corrupt every later entry of a player's custom-skill data on save; CustomSkillContentValidator reports it as an error and SkillRegistry refuses the fold with a WARN naming the fix. The mod-side reserved set gains # too, aligning with the shared stores' five so the two authorities can never disagree.
• Every offline queue and cache is keyed by UUID, because a username is not an identity. The leaderboard cache re-keys itself at load (legacy name rows resolve through the player directory; what cannot resolve is dropped with one INFO and refills on that player's next login - a renamed player keeps their totals, a reused name no longer inherits a stranger's position), and pending-xp-resets.json follows the pending-rewards doctrine verbatim: /bulksetxp resolves an offline target at queue time and refuses OUT LOUD a name no player has ever connected under, delivery drains by the connecting player's own UUID, and a legacy name-keyed file carries across once with a WARN per unresolvable name. The reset spool also writes itself under a version envelope now ({"version": 1, "players": {...}}): a bare 1.5.x map still reads as version 1, and a file declaring a NEWER version than this build reads is left unread with one warning naming the file and both numbers, instead of being half-parsed and clobbered on the next save.
• The player-database schema is version 2, and it refuses orphaned pre-1.6.0 rows. The never-read player_leaderboard table and players.online_instance column leave the DDL (disconnect stamps last_seen_at, which a staleness read can build on), and a database still holding rows under the retired QUESTS/ACHIEVEMENTS domains refuses to start, naming the count - starting anyway would burn each player's one-time progression-migration claim against empty legacy components and strand the real data forever. No such database is known to exist (the backend shipped dormant in 1.5.x), so the guard is the whole story: no automatic carry.
• Boot loads the player directory before the leaderboard cache and the pending XP resets, so a 1.5.x name-keyed leaderboard-cache.json / pending-xp-resets.json carries across on the first start instead of being emptied; a pending reset whose name nobody resolves is preserved in a timestamped backup/ copy with one notice. Every offline name resolves through the player-data seam (resolveUuid), so a database backend answers from its own players table; the leaderboard page keys its lines by UUID.
• Casting.HeldWeaponCategory is replaced by Casting.HeldWeaponCategories (hard break, no shim). The singular field is gone; the array-only ANY-of field replaces it, swept across all 27 authoring sites in one pass with no dual-support alias, matching this cycle's schema-rework posture. A pack or override still authoring the singular key fails to decode that leaf.
• An Effects key inside an ability-overrides.json entry is a load-time error naming the replacement field, Body - abilities compose their whole cast chain as one native interaction chain referenced by a single Body id. A cooldown/cost/presentation-only override needs no change.
• Mastery tracks are a structured asset, and the mastery template DSL is removed. One PascalCase file per track at Server/MMOSkillTree/Masteries/.json decoded by the one MasteryAsset codec: the shared Cost price group, the shared Requires gate grammar, a Nodes map merged per node id, and native Parent reuse against Abstract bases. A whole family is one Server/MMOSkillTree/MasteryGenerators/.json file expanded over the shared generator core (token substitution reaches node-id keys, gate Params and typed values; an authored file of a member's id always wins). The extends/params mastery template DSL, the MasteryTemplates store and the hand parser are removed; a pack still shipping template files gets a boot warning naming the replacement.
• mastery.json schema v3 (hard break). A track override is now a partial body in the pack schema, merged per leaf over the loaded track of its id ({"Enabled": false} switches one off); a pre-v3 file still carrying old-format tracks is moved to a timestamped backup/ copy with one boot notice naming the replacement. The owner-export serializer writes the authored schema and is lossless for every modifier field, the TRIGGER payload and ADD_STEP splice fields included.
• The interactive work-station engine does not live in this jar. It ships as the standalone RPG Stations mod (its own first public release; see its own docs and changelog). The MMO jar keeps only the soft integration/stations/ bridge (XP, luck, mastery, statistics, summary-panel enrichment); the per-player unlocked-flair set is ziggfreed-common's ZigFlairComponent, persisted by the library so a server running RPG Stations without the MMO still remembers what a player unlocked. Neither mod hard-depends on the other. Stations stay fully dormant without RPG Stations plus the skill-stations-pack content pack installed.
• SMITHING is no longer a built-in skill. It is removed from SkillRegistry.BUILTIN_SKILL_NAMES/BUILTIN_SKILL_DATA and ships as a pack-authored CustomSkillAsset in the MMO Skill Stations Pack (skill-stations-pack) instead. A one-way, idempotent legacy read path in SkillComponent preserves any Smithing XP a player already earned; data/SkillType keeps its SMITHING constant so the frozen MMOSkillTreeAPI.getSkillTypes() signature is unchanged.
• mods/mmoskilltree/spawn-hub.json and quest-givers.json are retired (hard break). Both shipped in the 1.5.x public line, so they exist on live servers. config/LegacyNpcPlacementMigration runs at plugin setup() (pure java.nio.file, before the asset pipeline exists, never throws), renames each present file IN PLACE to .legacy (disambiguated with a numeric suffix so a repeat boot never overwrites an earlier copy), and logs ONE warning naming the replacement. It never reads and never deletes them. The internal spawn-hub-placements.json spawn/idempotency registry is retired the same way. Migration: an NPC's position, the worlds it stands in, what pressing F on it does, and whether it appears at all are now ONE asset, Server/ZiggfreedCommon/NpcPlacements/.json; owner on/off overrides live in mods/ziggfreedcommon/npc-placements.json ({"": {"enabled": false}}, "*" for all) and /mmonpc list [--arg1=placements|structures|markers|channels] | enable | disable | reconcile manages them live (one listing verb, four nouns, defaulting to placements). Server/MMOSkillTree/QuestGivers/*.json keeps a WARN-only stub store for one cycle (asset/type/LegacyQuestGiverAsset), because an unregistered store logs NOTHING at all and a third-party pack still shipping them would fail in total silence. See CONTENT_PACKS.md's NPC placement authoring section.
• The conversation screen is the library's, and there is no per-mod dialogue bundle any more (hard break for a mod that registered one). NpcDialogueDepsRegistry, DialoguePageDeps and DialogueContextFactory are deleted, along with the DepsKey field on ZigOpenDialogue and ZigPlacementInteract. They existed so each mod could hand the page its own engine, resolver, namespace and providers; on a server running two talking mods the un-keyed default slot was a genuine collision, the later mod to start won it, and every conversation on the server - including the other mod's own - was then painted through the winner's namespace, so every authored key missed and every line read as a raw key. The page composes from process-wide state instead: the one DialogueEngine.shared(), the one conversation store, payloads resolved by class through DialoguePayloads, the character's name from its role's NameTranslationKey, and authored keys resolved through ContentKeys in the namespace of whichever mod ships them. Nothing is registered to make a conversation work, so nothing can be registered wrongly. Migration: a consumer deletes its DialoguePageDeps construction and its setDefault call and keeps only its DialogueEngine.registerShared / DialoguePayloads.register contributions, which were already additive.
• mods/mmoskilltree/dialogues.json is retired (hard break). Conversations are authored in one folder every mod on the server reads back, so the owner layer over them belongs beside it: mods/ziggfreedcommon/dialogues.json, a bare map keyed by conversation id whose entries merge LEAF BY LEAF over the stored conversation (restate only the nodes you change, exactly the way its four sibling owner files and mastery.json overlay), with $-prefixed keys reserved ($SchemaVersion, absent means 1). config/LegacyDialoguesFileMigration renames the old file in place to .legacy at setup() with ONE boot WARN naming the replacement, and never reads it. Nothing is carried automatically: the two files hold the same bodies in the same shape, so moving them is a copy an owner can check rather than a server's conversations quietly changing hands. config/DialogueConfig and dialogue/CommonDialogueFold are deleted; /mmomigrate and the docs-site Migration Converter both know the retirement, and the converter carries an uploaded file's entries across as shared-store pack assets.
• A conversation says what note it shows and what its own exit row reads. Two new authored leaves on a dialogue asset. "Header": ["ActiveObjective"] names the sources for the one-line note under the speaker's name, in order, first one with something to say wins; naming none - the default - shows no note at all, so a character who should never mention quests does not. ActiveObjective is the library's own, computed from the shared quest engine and worded exactly the way the quest tracker words it, so dialogue/MmoDialogueHint is deleted and no mod ships a hint provider. "Chrome": {"FarewellKey": ..., "MissingKey": ...} gives a character its own words for the exit row and the nothing-to-say line; unauthored takes the library's, which now ships in all nine locales as ziggfreedcommon.dialogue.*. The MMO's three ui.dialogue.* keys are removed from all nine .lang files, since the library carries the same wording.
• WorldRulesAsset's flat Match string is retired (hard break). A rule targets a Where group instead: "Where": {"Match": ["*Dungeon_*"]} for a world-name pattern (a BARE word being an exact name) or "Where": {"GameplayConfig": ["ForgottenTemple"]} for the world's own stable config key. Both jar rules and any owner world-rules.json are rewritten. A file still carrying the retired key is decoded solely so it can be reported: ONE boot WARN per rule id quotes the old value, prints the replacement to paste, and states plainly that until it is rewritten the rule matches no world. WorldRulesMatcher keeps its precedence ladder verbatim and sources each rank from WorldSelector.match, so the winner is unchanged for every pattern kind and for every subset of a mixed rule set (asserted by a subset sweep in WorldRulesMatcherTest).
• A pre-release naming sweep straightens three internal vocabularies (all inside the 1.6.0 surface before it shipped, or invisible to saved data). The /mmohud reply keys move from cmd.mmohud.* to cmd.hud.* in all nine locales (the command name and its permission node are unchanged). The two mastery stat-mirror modifier keys spell their segment with an underscore - mmoskilltree:mastery_loot / mmoskilltree:mastery_damage - and both sit in the reserved-segment registry; these keys live only on runtime entity-stat maps that are rebuilt idempotently every boot, so nothing persisted carries the old spelling. HudKey moves from the frozen-residue data/ package to feedback/ beside NotificationCategory, the descriptor family it parallels (a compile-time move; the string-keyed MMOSkillTreeAPI.isHudVisible seam is untouched). And the jar's optional-dependency range on Ziggfreed:RpgStations narrows from <1.0.0 to >=0.1.0 <0.3.0, the range the compiled api contract actually supports.
• A second pre-release sweep settles the ability-family schema spellings (every one inside the 1.6.0 surface before it shipped; the 1.5.x formats these fields descend from retire wholesale above, so no shipped file authors them). An ability's display keys are Identity.TitleKey / Identity.DescriptionKey, the same pair an AbilityMods/*.json asset carries, and an ABILITY_MOD reward names its display key with the titleKey param (the 1.5.x nameKey reward-param spelling still converts on the sanctioned legacy read); XP routing filters held-weapon resolution with XpRouting.ExcludeSkills; a passive trigger's On values are PascalCase (HitDealt, Kill, Finisher, DodgeArmed) and its weapon gate is the ANY-of array WeaponSkills; a cast node's per-chain cooldown leaf is Cooldown.LocalMs, milliseconds like every other duration; the cast event carries castAtMs; and the Cost group is exactly {Stat, Amount} (no side list of secondary costs). A class's Grants nests one {Allow, Deny} group per governed surface (Abilities, Mastery, SkillRewards) instead of six flat whitelist/blacklist leaves, so a pack overlays one list per leaf. The xpGain modifier paramKey retires from the canonical vocabulary (XP routing owns that job; the mastery XP mirror goes with it), and three validate-report domains spell themselves like their siblings: item_stats, damage_school, station_bridge.
• A world rule's gameplay knobs move into one nested Rules group. A WorldRules/*.json file (and an owner world-rules.json body) now reads WHERE / WHETHER / WHAT: Where and Enabled stay top-level, and the six gameplay knobs (XpMultiplier, AbilitiesEnabled, CombatBonusesEnabled, StatBonusesEnabled, DisabledSkills, EnabledSkills) sit together under "Rules": { ... }. Both jar rules and the World Rules admin page write the nested shape. A file still authoring a knob flat at the top level KEEPS WORKING this release: the flat leaf is honored (a nested leaf wins over its flat twin), with one boot WARN per rule naming the group to move it into - the nested spelling is the one a future release will read.
• Authored dialogue FLAGS are retired (hard break). SetFlag, Flag, and NotFlag left the dialogue engine's pre-seeded generic types. Migration: a first-visit greeting (a NotFlag guard plus a matching SetFlag) becomes one Once knob on the Start entry; an option guarded by a hand-composed reward::: key becomes "Once": true on the option; any other named state becomes a declared Memories entry read by bare name. The flag STORE and its q:/w: key composition survive as internal plumbing only, so /mmoquest reset clears exactly what it cleared before and no author ever sees a composed key again. The MMO reward sugar's own once-guard is re-keyed RewardOnce so it sits beside the engine's option-level Once; a bare "Reward" still defaults to once. The per-consumer engine builder means this is not a ban: a consumer that genuinely wants raw flags registers its own types.
• A placement with no Identity.NpcId IS its role now, not its file name (hard break). The id content binds a character by used to default to the PLACEMENT id, so two standings of one character had to be tied together by hand with an alias. The default is the Identity.Role the placement names, which says the true thing: two placements of one role are two standings of ONE character, and a quest bound to it is offered, credited and handed in at either with nothing authored twice. Authoring an NpcId still opts out and makes a standing a character of its own. Migration: a placement whose authored NpcId differed from its role id keeps working untouched; one that merely restated its file id should drop the leaf, and any content binding that file id re-points at the role id. The jar's own placements did exactly that - only Mmo_Hub_Forgotten_Temple still authors an id, because it is the only one that has to be a character of its own. A placement naming neither an id nor a role now answers to nothing rather than to a character that was never in the world.
• Character ids and the npcs..name keys built from them are PascalCase (hard break). Authored ids spell the Hytale way, matching the file they come from: Mmo_Hub, Mmo_Hub_Temple, Mmo_Mastery_Trainer, Guide_Wilds. The jar's base role files spell their Mmo_ prefix Pascal too (Mmo_Hub.json, Mmo_QuestGiver.json, Mmo_Mastery_Trainer.json, and the trainer's Server/Models/Mmo_Mastery_Trainer.json model), one spelling with the Template_Mmo_* files, the placement ids and every alias; role lookup is case-insensitive, so a placement or pack still naming the old MMO_* spelling keeps standing its NPC up. Looking a character up ignores case everywhere (the giver index compares ids case-insensitively now, where it used to demand an exact match), but the DISPLAY key read from an id does not, so the jar's npcs.mmo_hub.name / npcs.mmo_hub_temple.name / npcs.mmo_mastery_trainer.name / .hint keys are renamed to match, in all nine locales. Migration: a pack overriding one of those keys renames its own copy; a pack shipping a giver renames its npcs..name key to match the id, and a TALK_TO_NPC objective target must spell the character id exactly as the placement does, since objective targets are compared case-sensitively like every other asset id.
• An unregistered Requires factor now fails a bounds-less placement condition. A placement condition naming a factor nobody registered used to resolve 0.0 and therefore PASS a condition with no Min/Max, so a typo'd factor id silently gated nothing. Every factor site now fails closed on an unresolvable value, which makes a bounds-less condition a genuine presence check ("only where that mod is installed"). A condition that already carried a Min behaves exactly as before.
• The achievement listener registry is DELETED, not deprecated (api_version 1.6.0). MMOSkillTreeAPI.addAchievementListener(Consumer), removeAchievementListener(Consumer), fireAchievementEvent(PlayerAchievementEvent) and the api-module type com.ziggfreed.mmoskilltree.api.events.PlayerAchievementEvent are gone; a call to any of them does not compile against 1.6.0. Migration: achievement moments are ordinary Hytale events now, dispatched on the world tick thread through the engine event bus, so a subscriber registers them exactly the way it registers any other server event and needs nothing from MMOSkillTreeAPI at all. The three replacements live in ziggfreed-common's com.ziggfreed.common.achievement.event package, which every server running this mod already loads: AchievementProgressedEvent (achievement id, criterion id, current and required amounts, whether that criterion just finished), AchievementUnlockedEvent (achievement id, its points, whether rewards are still waiting to be collected), and AchievementClaimedEvent (how many rewards were granted, queued for a later attempt, and failed). All three name the player by UUID rather than a PlayerRef, and all three carry the achievement's authored tags() - its category, its subcategory, and the two flags server_first and feat_of_strength - so a listener can branch on what KIND of achievement moved without asking this mod for its catalogue. Before: MMOSkillTreeAPI.addAchievementListener(event -> { if (event.getPointsAwarded() >= 100) announce(event.getAchievementId()); }); After: getEventRegistry().registerGlobal(AchievementUnlockedEvent.class, event -> { if (event.points() >= 100) announce(event.achievementId()); });. The old payload's running-total field has no direct replacement on the event, because it was only ever a convenience: read it when you need it with MMOSkillTreeAPI.getAchievementPoints(store, ref), which is unchanged. Every achievement READ on the API is kept verbatim (getAchievementComponent, isAchievementUnlocked, getAchievementProgress, getAchievementPoints, pin/unpin/getPinnedAchievements, getServerFirstClaim), and PlayerGainXpEvent plus addXpListener are unaffected. The full recipe also ships in the jar's own sources at api/src/main/java/com/ziggfreed/mmoskilltree/api/events/package-info.java.
• A reward's type is an open kind id, not a fixed enum (behavior change). Any doc or content saying type must be one of COMMAND/XP/BOOST_TOKEN/CURRENCY/ABILITY_MOD is stale. An unrecognized kind is no longer silently dropped at parse: it parses and is reported by the startup audit and /mmoconfig validate as UNKNOWN_REWARD_KIND, because the mod that owns that kind may simply not be installed. A second new validator code, UNKNOWN_FACTOR_ID, reports an unresolvable factor id on a requirements.factors entry the same way (a blank factor id warns too, since it is skipped rather than enforced).
• mods/mmoskilltree/luck-loot.json and mods/mmoskilltree/mob-drops.json fold into ONE mods/mmoskilltree/bonus-drops.json (hard break, converted in place). What a broken block gives on top of its own drops and what a killed mob gives on top of its own were the same question asked in two vocabularies, so they are one table where every row names the moment it answers for. LegacyBonusDropsMigration runs at plugin setup() before the table is read (pure java.nio.file + JSON, never throws) and carries EVERY override across: a row that named a drop still names it, a row that stated its own odds still states them, and a pattern switched off is still switched off, including the pre-loot-form DropList / Drop / Lootable / Item / bare-string spellings and their Chance blocks. One INFO line per converted row names what it became; a luck pattern's minted id (and a mob row's own id) is re-filed under the shipped row's Mmo_* id when it names one (Ore_Copper lands on Mmo_Ore_Copper, Trork_Bonus on Mmo_Trork_Kill), so the per-leaf overlay keeps landing on the row it re-tunes, and every other id carries verbatim. A legacy key was a bare substring matched anywhere in a name, so each one is carried across as the anywhere-in-the-name pattern (Trork becomes *Trork*) to preserve exactly what it covered. A row already present in bonus-drops.json is never overwritten, "__DISABLED__" is accepted on both sides, and both old files are moved into a timestamped backup/ copy rather than deleted, along with the generated defaults-luck-loot.json reference echo. mob-drop-commands.json is untouched and remains the SIMPLE kill-only surface beside it: it stays a SEPARATE opinion consulted first for kills, so an owner who only wanted to add a command still gets the shipped table's drops beside it, and disabling a pattern there still silences both.
• mods/mmoskilltree/mob-drop-commands.json moves to schema version 4, and two fields retire. A pool's delay is no longer read: a pool's commands run immediately, in the order they are written, and a file still carrying the field gets ONE boot WARN naming it. requiredTier retires outright - it was dead schema that silently disabled any pool setting it, because the built-in elite-mob system it keyed on was removed in 1.5.0 and mob difficulty lives in the standalone MMO Mob Scaling mod. Existing overrides are converted in place, and the admin page drops both inputs.
• mods/mmoskilltree/pending-quest-rewards.json retires; the live spool is pending-rewards.json, keyed by player UUID only. On first start it is drained into the new spool and retired to a timestamped backup with one notice naming what moved and what did not. A queued reward filed under a player NAME cannot be carried across (a name is not an identity), so those entries stay in the backup copy and the notice names each one: hand them out yourself, or have the player join once and re-run the command that owed them. Going forward, an offline grant with no resolvable uuid REFUSES LOUDLY instead of queueing into the dark: /mmoquestadmin complete on a player who has never connected to this server answers with a red refusal and queues nothing, and a no-command context logs a SEVERE line naming the player, the source, and the command that would have run. A player who HAS connected but is offline still queues and still receives it on next login.
• /give positional quantities are honored wherever this mod runs the command (behavior change). An authored command reward written /give Bob Wood_Planks 32 now delivers 32 rather than 1, everywhere in the mod, because every console dispatch runs through one command primitive that normalizes the quantity. The POSITIONAL_GIVE_QUANTITY validator finding stays as a PORTABILITY warning (the engine's own /give still needs --quantity=N), not a data-loss one.
• mods/mmoskilltree/elite-mobs.json is retired. It has been inert since 1.5.0 (nothing parses it and nothing constructs the config it fed). It is now probed for at startup and retired with one notice; it is never read and never deleted.
• The three generated _defaults/ echo files retire (hard break for anyone who edited one). quests/_defaults/default-quests.json, achievements/_defaults/default-achievements.json, and achievements/_defaults/default-point-milestones.json were rewritten from Java on every boot and then read straight back in as the owner layer whenever no user file existed. The built-ins are overridable assets now, so each file is renamed in place to .legacy on first start, with ONE notice naming its replacement; it is never read and never deleted, and a repeat boot never overwrites an earlier copy. Migration: read the built-ins at Server/ZiggfreedCommon/Quests/MMOSkillTree/, Server/ZiggfreedCommon/Achievements/MMOSkillTree/, and Server/ZiggfreedCommon/AchievementMilestones/MMOSkillTree/ inside the jar, then override one by dropping a file carrying the same quest or achievement id into mods/mmoskilltree/quests/ or mods/mmoskilltree/achievements/ (a points milestone re-tunes by authoring the same Threshold, in a pack or in achievements/point-milestones.json). Keeping a leftover echo on disk would only shadow the current built-in with a stale copy, which is exactly why it retires.
• Authored dialogue Talk is retired (hard break). The no-op Talk action type and its Talk option sugar are gone, so a file still authoring "Talk" fails the read naming itself rather than silently doing nothing. Migration: credit a conversation explicitly with the new MarkTalked action ({"Type": "MarkTalked"} credits the NPC in front of you, alias set included; "Target": "@self" or an explicit npc id names one). There is no implicit talk credit left anywhere: the Citizens adapter's credit-on-interact hook is gone too, and an NPC with no dialogue at all credits through the new ZigTalkCredit NPC action ({"Type": "ZigTalkCredit", "Npc": ""} on the role's own interaction instruction).
• The default Trork kill bonus ships ENABLED. Server/MMOSkillTree/BonusDrops/Mmo_Trork_Kill.json is live default content, overridable like every other shipped asset: a server that wants it off writes {"drops": {"Mmo_Trork_Kill": {"Enabled": false}}} in mods/mmoskilltree/bonus-drops.json. Its odds are deliberately conservative and luck-scaled, and its $Comment doubles as the authoring tutorial for the kill half of the surface.
• The shipped Server/MMOSkillTree/BonusDrops/ rows are keyed under ONE Mmo_* convention (Mmo_Ore_Adamantite, Mmo_Vortex_Charm, Mmo_Trork_Kill, ...), since a row's id IS its owner-override key. LegacyBonusDropsMigration re-files a bonus-drops.json override still keyed by an old row id under the row's current id (one INFO per re-keyed row), and the web Migration Converter applies the same map; the native MMO_* stat and drop-list ids are unchanged, since gear and drop tables reference them.
• /mmoconfig trim's luck half is retired, and /mmoconfig diff's luck section is re-pointed (behavior change). Trimming existed to strip an owner row that merely restated a Java default, and there is no Java default luck table left to be redundant against; the owner layer is a per-leaf overlay by id rather than a full-row copy, so the concept no longer applies. XP trimming is untouched, and the same half of the XP overrides admin page's trim button goes with it. diff lists the bonus-drop owner bodies by id instead and answers to luck, drops or all. /mmoconfig export|import's config key follows the file: luck-loot becomes bonus-drops.
• StatisticsComponent's shape changed (its thirteen public per-breakdown maps are gone in favour of one flat counter bag; the persisted wire format is unchanged, including the empty-map "" round trip and long-width totals). The frozen API reads over it are untouched: MMOSkillTreeAPI.getStatistics is byte-identical and getStatTotal(store, ref, canonicalKey) remains the third-party read.
• Named world selectors are gone; a Where carries its own patterns (hard break). There is ONE world vocabulary: Where.Match takes a world-NAME pattern (Foo exact, Foo*, *Foo, *Foo*, *), Where.GameplayConfig takes the world's own authored config key, and Where.ExcludeMatch takes name patterns that reject a world even when a positive axis matched. The WorldSelectors asset type, its owner file, and every Where.Names reference retire with the indirection. Migration: rewrite "Names": [""] as the patterns that selector held - "Match": ["default"] for the ordinary world (a bare word is an EXACT name), "GameplayConfig": ["ForgottenTemple"] for an instance family, "Match": ["*KweebecNightmare_*"] for a name-token family. If your main world is not named default, override that file's own Where by id from a pack or through the asset type's owner layer - it is a handful of files, and each states what it targets on its own page. A Where matching no loaded world is reported as MATCHES_NO_LOADED_WORLD and one with no positive axis as EXCLUDE_ONLY, so a missed rename is a validator finding rather than content that silently never appears.
• A dialogue world scope authors Where, not a selector name (hard break). The scope leaf on Once, on a Memories declaration, and on a dialogue flag scope is the shared Where world-selector group (the same {Match, GameplayConfig, ExcludeMatch} group an NPC placement carries), not a named selector and not a bare string; the retired World string leaf refuses decode and names the replacement. Migration: replace {"WorldSelector": "forgotten_temple"} with {"Where": {"Match": ["*Forgotten_Temple*"]}}, using the pattern that names the world family rather than the selector that named it (an instance family is better keyed {"Where": {"GameplayConfig": ["ForgottenTemple"]}}, which carries no per-run uuid). A Match pattern keys state by its literal core, so the handle is stable across an instance world being rebuilt under a fresh uuid name, and a narrower core scopes tighter. A dialogue {"Type": "World"} CONDITION nests its axes under the same Where group ({"Type": "World", "Where": {"GameplayConfig": ["ForgottenTemple"]}}), matching every other world-targeting field; an omitted Where fails closed.
• Server/MMOSkillTree/LuckLoot/ and Server/MMOSkillTree/MobDrops/ are gone; a pack authors Server/MMOSkillTree/BonusDrops/ (hard break). Both stores, their asset types, their validators, their owner-override configs and their LuckLoot / MobDrops pack-control keys are deleted. One row per file, the filename is its id, and the body is {When: {Kind, Match}, Chance?, Loot, Notify?, Enabled?} - a structured codec decoded before the mod sees it, so an unknown key or a malformed Chance fails the read loudly rather than surviving as a table that quietly hands nothing over. Migration: a luck row {"": {"Loot": {...}, "Chance": {...}}} becomes a file whose body carries "When": {"Kind": "BreakBlock", "Match": "**"} alongside the same Loot and Chance; a mob entry {"Mob": "Trork", "Loot": {...}} becomes "When": {"Kind": "KillMob", "Match": "*Trork*"} alongside the same Loot. A pack still declaring "LuckLoot" or "MobDrops" in a Server/MMOSkillTree/Control/*.json file is declaring an unknown key: the new store merges natively, so a pack overrides a row by re-authoring its id and switches one off with {"Enabled": false}.
• mods/mmoskilltree/currencies.json, bounty-board.json and token-shop.json are retired (hard break). Wallets, storefronts, rotating shelves and boards of contracts are ziggfreed-common's economy (zc-commerce): the content is Server/ZiggfreedCommon/{Currencies,Shops,ShopPools,ShopEntries,Boards,Bounties} assets, the owner layer is mods/ziggfreedcommon/{currencies,shops,shop-pools,boards}.json (override BY ID, leaf by leaf, through the asset's own codec), and /zigcommerce reads and edits what a player holds. config/LegacyCommerceMigration runs at plugin setup() and renames each present file IN PLACE to .legacy with ONE boot WARN naming the replacement; it never reads and never deletes them. A player's balances, lifetime spends and per-offer purchase counts move onto the shared economy's own record ONCE, at their first ready after the update (player/CommerceStateMigration, claimed so it can never run twice; the reroll allowance is reset rather than carried, since the two sides number their periods differently). This mod keeps only what the library cannot know (pages/MmoCommerceDeps: theme, naming, reward chips) and thin /mmocurrency / /mmoshop / /mmobounty aliases over /zigcommerce; the TokenShopPage / BountyBoardPage screens, bounty/, shop/, currency/, rotation/ and content/cost/ are DELETED, and the Mmo_Currency reward kind is spelled Currency.
• mods/mmoskilltree/placed-blocks.json is retired (hard break, nothing migrated). The placed-block anti-exploit ledger is ziggfreed-common's world/placed/PlacedBlockLedger, kept at mods/ziggfreedcommon/placed-blocks.json and read by XP, statistics, quests and achievements alike; the old file is renamed in place to .legacy at boot with one notice, never read and never deleted. Blocks placed before the upgrade are forgotten once (one expiry window of exposure); the four knobs stay in skill-config.json.
• The legacy owner-file achievement leaf announcementCommand is retired. How an announced achievement's server-wide banner is drawn is authored ONCE, for every achievement, in Server/ZiggfreedCommon/FeedbackMoments/Achievement_Unlocked.json; a file still carrying announcementCommand gets one boot WARN naming the replacement (a Command group on that moment file, or a Variants entry scoped by When: {achievement: }) and the leaf is otherwise ignored.
• The optional database backend's QUESTS and ACHIEVEMENTS domains are replaced by ONE PROGRESS domain (hard break). Quest and achievement state now live on a single shared per-player record, so they persist as a single blob under a single domain name; the two old names are gone from PlayerDataDomain and nothing reads or writes a row filed under them again. A row a pre-release build left behind simply sits in the table, unread. This costs no player anything: the state itself lives in the world save and is carried across by the one-time migration below, whichever backend a server runs.

• The Mastery Trainer leaves the jar for the MMO Skill Mastery Pack (hard break for a server running the jar without it). That character is the pack's end to end now: their model, their role body, their nameplate and press-F hint keys, their Forgotten Temple placement and their conversation all ship there, and the jar's copies of all five are deleted. A server running the mastery pack sees no change at all, since the pack already carried its own placement and conversation and they simply stop being overrides; a server running the jar alone has no trainer standing in the temple, and reaches the Mastery screen from the hub menu as before. Migration: install the mastery pack to keep the trainer. A pack that overrode npcs.Mmo_Mastery_Trainer.name / .hint now overrides the mastery pack's keys rather than the jar's.
• Required companion jar: ZiggfreedCommon-2.0.0.jar (see that mod's own changelog for its scope). The optional RPG Stations bridge compiles against its api artifact 0.3.0 (the artifact semver tracks apiVersion(): version N ships as 0.N.0); and every content pack rewritten this cycle raises its MMO floor to ^1.6.0 and bumps its own version (bounty-contracts 1.2.0, skill-mastery 2.0.0, taming 1.2.0, and zone-quests with its first release, 1.0.0). Skill Capes keeps its 1.0.0 version; its manifest raises the same floor. Two packs are rewritten but not part of this release: skill-classes 2.0.0 rides the Class System's own Future status, and skill-stations 0.1.0 waits on the RPG Stations companion mod.

Features

• "Ready to hand in" waits until the errand is actually done, and a hand-in takes what you brought. A quest on a character's list reads as ready only when handing over what is in the bag would FINISH it, so a temple quest with 150 rocks still to break no longer greets the player as though the job were over; until then it sits under In progress, where its Hand in button is still there to take a part-load. The guide's "I have returned" line follows the same rule and waits for something to have returned WITH. One press of Hand in discharges every delivery that character or board is owed rather than the first of them, so a tribute asking for three separate offerings settles in one go. Behind all of it, the shared engine's hand-in offer asks for one of what a step still owes instead of the whole amount, so a large delivery can be carried down in loads. The settlesTurnInAt / hasSettleableTurnInAt reads this needs are forwarded explicitly through MmoDialogueQuests, never inherited, so a conversation asks the amount-aware runtime rather than the interface's looser default.
• The guide's lines read with emphasis. Every dialogue line in the mod's own catalogue that asks the player to do something marks what to act on, in all nine locales: the items to craft, gather, place, cook or hand over and the creatures to hunt read in bold, and the place and proper names to seek out (the Forgotten Temple, the Trork) carry the one dialogue accent colour (#ffd97a). A line that only congratulates stays plain, and so does every option label, because a button label is a String-only sink that prints tags literally. The vocabulary is those two elements and nothing else, no per-line colours and no whole-sentence bolds, and it is written down in the localization skill so a pack follows the same rule.
• A notice's tone paints the whole toast, and the toast lists its payout. Every shipped Server/ZiggfreedCommon/FeedbackMoments/ file authors a whole-toast Tone from the closed Info / Success / Reward / Warning / Error set instead of per-line Colors, so the in-page toast's frame and headline and the corner feed's native style always agree: a payout reads gold end to end on the page, frame and words alike, the progress tick is the neutral blue with a green "Objective complete" finish, a full bag reads red, and a lost server-first race reads amber. A moment that carries rewards - a quest completing, parking or paying out, an achievement earned or collected - lists them as rows under the headline of the in-page toast, one per reward through the same chip reading every reward panel uses; a Rows group on any moment file switches that off or caps it with a "+N more" line, and a server owner retunes any tone by overriding the file. (The Tone word, the Rows group and the engines carrying their payouts are ziggfreed-common 2.0.0's; this mod ships the authored files.)
• The Objective Book's claim toasts show what they paid, and a giver's quest is taken at the giver (ziggfreed-common 2.0.0 book fixes this mod picks up). Claiming a quest, an achievement or a points milestone toasts one gold row per reward beside the headline, through the shared chip reading. And a quest that names its giver (Npc.ViewId) is not acceptable from the quest log: its row swaps Accept for a hint naming that character (resolved from the placement and identity assets, so every pack's giver-bound quest reads right with nothing supplied), the accept verb refuses a stale binding, and the quest stays listed, trackable and abandonable; it is accepted on the character's own quest list, where its conversation lives.
• The Forgotten Temple opens on day one, and the guide says where to find them. Meet Me at the Forgotten Temple used to sit four quests deep, behind the first hunt; it now needs only the welcome finished, so it stands beside Craft Starter Tools rather than after it and a player who would rather explore than forge has somewhere to go straight away. The guide's crafting brief names the temple in the same breath, and a "Where do I find you?" line rides both shared footers, so the offer reaches every screen the guide shows except the very first greeting. It hides itself once the quest is taken, and again anywhere inside the temple. The starter chain's listing order follows the new shape: the temple meeting sorts third and everything after it shifts one place.

• A locked or unstarted contract on the bounty board explains itself. The board's detail panel reads every step through the same shared text walk the quest book and the NPC quest page use, so a contract's objectives render as real sentences (the library's neutral per-kind lines, or this mod's own composed wording where it names the content) instead of "Unnamed step"; a locked contract lists each unmet requirement - the prerequisite quest by title, a gated factor by the name its Server/ZiggfreedCommon/Factors/ naming asset gives it, with the bound it asks for - instead of one generic "You cannot do that yet." Both commerce screens word a gate refusal through the one shared lock-reason mapping, so a gate reads identically wherever it shuts. (The engine work is ziggfreed-common 2.0.0's; this mod's own factor names and its composer install land with its gate convergence.)
• One objective-sentence seam for the whole server. This mod's objective renderer installs into ziggfreed-common's progress.ObjectiveComposer (the per-mod quest/QuestObjectiveText / achievement/AchievementCriterionText seams are deleted), so every shared surface - the objective book, a board's contracts, a character's offer page, the tracked panel - reads the SAME composed wording this mod's own screens build, and a step the renderer cannot speak (another mod's kind, another mod's key) falls to the library's neutral per-kind family instead of an unnamed line. The composed line always reads the step's authored vocabulary: a REACH_LEVEL step still says "Reach level 30 in Mining", never the stat channel it dispatches on.
• The feature switches live in the library's generic feature factor. content/gate/MmoFeatures declares this mod's feature ids, aliases and live on/off suppliers into ziggfreed-common's FeatureFlags, whose first declaration contributes mmoskilltree:feature process-wide - existing content gating on that id answers exactly as before, the availability-provider seam (RpgStations, NPC placements) stays, and the old per-mod registry and fold-time lift (content/gate/FeatureRegistry, FeatureLift) are deleted in favour of the library's progress.gate.FeatureLift, called with this mod's factor id.
• The guide introduces the mastery trainer. Standing in the temple with the meeting behind them, the player gets one extra line asking who the other figure across the landing is; it opens a screen about her, and taking her up on it starts Meet the Mastery Trainer. The whole beat is held behind the mastery feature, so a server without the mastery pack never sees the line and never hears about a character who is not there. An option a switched-off feature holds shut is also no longer audited as this server's content, which is what lets a shipped conversation carry a beat for a pack that may not be installed without reporting that pack's quest ids as missing on every boot.
• The Forgotten Temple gets an arc of its own. Three main quests and a daily, all offered and handed in at the temple standing of the Adventurer's Guide and nowhere else, because an alias points one way: the temple answers to the spawn guide's id, never the reverse. What the Stones Remember clears the rubble and asks for worked copper, The Watch Below thins the Trork off the stair, and Keeper of the Deep waits on total level 150 before handing over the keeper's vestments. The Temple's Due is a calendar daily, refreshing at the day boundary rather than on a rolling timer. Its offering is three humble reagents (essence, plant fibre and a little light leather), none of which needs a bench or a smelter, and it pays a single loot-table roll whose four rolls resolve independently, so a good day pays several at once and the daily funds its own tribute.
• A loot table can celebrate its rare pull, and a rolled reward pays the whole table. Any roll or ladder floor in a Server/ZiggfreedCommon/Lootables table may carry a Cue beside its Grants: an opaque celebration id that fires only when those grants genuinely paid out, presented as the Server/ZiggfreedCommon/FeedbackMoments file of the same name. It reaches every table this mod rolls, whichever path rolled it: a table paid out as a reward, a mob's bonus-drop row and a block's lucky find alike. So the whole pipeline is authorable, and a pack invents a celebration of its own by shipping a new cue id plus the moment file that answers to it. The jar ships Rare_Find (a gold toast and the legendary-chest chime), authored on the temple daily's warden-blade roll and the mastery daily's adept-staff roll. A table granted as a Lootable reward (a quest payout, a shop offer, a dialogue) pays its FULL grants vocabulary - items, native drop lists, console commands and registered reward kinds alike - exactly as one rolled at a work station does, so the temple daily's boost-token roll and the mastery daily's mastery-point roll pay through the reward path. (The sink wiring, the cue seam and the cue-to-moment mapping are all ziggfreed-common 2.0.0's; this mod contributes only the moment file that says what Rare_Find looks like.)

• Five reward items, each a copy of a base-game one. A crude pickaxe, sword and longsword and a linen robe and hood, each inheriting everything from the vanilla item it names as its Parent and differing in four lines. Recipe is not among the fields a Parent hands down, so none of them can be crafted at a bench. The weapons and the tool carry small flat Health and Stamina; the robe and hood give LESS health than the plain linen they are cut from and carry an MMO channel instead, +1% luck on the robe and +1% experience on the hood, so the set is a trade rather than a straight upgrade. Held-weapon and tool stats ride Utility.StatModifiers, which the equip bridge applies because the engine reads that block only off an accessory-slot item; armor stats are the engine's own Armor.StatModifiers.

• The guide speaks to every side quest at both of its moments. Make Camp, Home Cooking, Prove Your Mettle and the temple meeting each get a line for the hand-in and a line for while the quest is still open, in all nine languages, where three of the four previously fell through to the standing menu whatever the player was carrying. Each hand-in line opens the quest list with that quest called out, so the player sees what they are collecting. The one-size line stays in the conversation as the default a server owner can point their own side quest at without writing a screen.
• The Asset Editor shows each field's real default and offers dropdowns on the closed vocabularies. Every jar asset schema declares the effective value of a leaf whose unauthored meaning is not the control's zero-state (an Enabled meaning true, IsParamKey meaning true, a bonus-drop row's gold notify colour) and exports each code-closed string vocabulary as an enum with a one-line meaning per value: a passive trigger's On hooks (HitDealt/Kill/Finisher/DodgeArmed), a mastery Scaling.Curve and Sacrifice.Mode, a bonus-drop row's When.Kind (BreakBlock/KillMob), the Power Level DefaultMode, a custom skill's Triggers, a pack control file's add/replace modes, a cast cost's Stat pool (MANA/HEALTH/STAMINA), and an ability body's Target/Overlap knobs. Decode is unchanged; a pack-extensible vocabulary (a paramKey, a damage school, an engine stat name) stays a plain string on purpose.

• Adds Poison as a seventh damage school beside Fire, Ice, Lightning, Water, Arcane and Void: the jar's Server/Entity/Damage/Poison.json layers the vanilla cause under Elemental with its own combat-text colour (#7CFC00), and the school ships its MMO_Bonus_Poison / MMO_BonusFlat_Poison / MMO_SchoolResist_Poison channels, tooltip labels and names in all nine languages. Poison, Thorn Patch, Paralyzing Dart and Forest Warden are Poison-school abilities.
• Adds an elemental-school pass over the default abilities: Molten Slam, Flame Totem, Pyromaniac and Explosive Shot deal Fire; Dragon Arcana deals Ice; Tempest, Tempest Vault, Wind Dancer and Concussive Reverb deal Lightning (the school's first abilities); the dagger shadow kit (Assassinate, Mark of Death, Shadow Dance, Shadow Pounce, Smoke Bomb) deals Void; Archmage's empowered casts read as Arcane. Plain weapon strikes stay physical. ArmNextHit nodes gain a Cause leaf, and a beam-only ability now shows its school on its card.
• Completes the damage-school roster at nine. Adds Life, the drain / lifesteal / holy school (its own authored cause, spring-green combat text, MMO_Bonus_Life / MMO_BonusFlat_Life / MMO_SchoolResist_Life channels and tooltip labels); Soul Drain, Vampiric Strike and Blood Pact deal Life damage. Makes Physical a genuine school with its own channels (MMO_Bonus_Physical / MMO_BonusFlat_Physical / MMO_SchoolResist_Physical): a hit whose cause reaches no school resolves to Physical, so every hit carries a damage type - mechanically and in the UI, where an untyped damage ability's card and tooltip read Physical. All the new channels ship empty like their siblings, so damage is unchanged until content grants them; Physical resistance is keyed on the vanilla weapon causes (Bludgeoning/Slashing/Projectile) too, since the game's resistance lookup matches a hit's exact cause. Gear enhancement can roll the new schools' bonus and resistance lines.
• Adds an Arcane Essence item (Ingredient_Arcane_Essence): every school now mirrors an essence ingredient - Fire/Ice/Lightning/Water/Void/Life map to their vanilla essences, and Arcane gets this jar-authored one (vanilla ships no arcane essence).
• Ability tooltips show the damage type: a "Damage type" line in every damage-dealing ability's hover tooltip, named and coloured per school with the same colour the school's floating combat text uses, matching the school tag on the ability card.
• Styled ability tooltips: the hover tooltip carries the composition's full styling - school-tinted damage numbers, the accent tint on key numbers (cooldown seconds and cost included), bold keywords and section headers, italic flavor text, and an amber level-requirement line while the ability is still locked. The tooltip flatten converts the structured message styles the in-page text renders into the literal markup the item-description channel parses, so one styled composition feeds both surfaces.
• Per-school resistance has one authority and one applier. Everything that grants school resistance (a weapon or tool's StatModifiers, an enhancement roll, a mastery node) adds up on the player's MMO_SchoolResist_ stat, and SchoolResistReconciler keeps one invisible infinite native effect per school on the player carrying that total, so the game's own armour mitigation applies it beside worn armour. The mod no longer folds that stat into its own defense reduction, so it is never applied twice. Armour pieces author native Armor.DamageResistance directly.
• Adds a school scope to mastery modifiers and a schoolResist modifier key: a mastery node's damage value can belong to a damage school ("school": "Fire") instead of a weapon skill or an ability and is mirrored onto MMO_Bonus_ / MMO_BonusFlat_, and schoolResist mirrors onto MMO_SchoolResist_, both under the mastery key segment so respec removes exactly what a purchase added. Node descriptions render the school by name in the player's language.
• Content can be gated on another mod being installed. A Requires factor condition {"Factor":"hytale:mod_installed","Param":"Ziggfreed:KweebecNightmare","Min":1} (a ziggfreed-common factor) works on quests, achievements, dialogues, loot, placements and shops, and the mod HIDES such content when that plugin is absent, the same way mmoskilltree:feature gates hide. "Max": 0 gates on the mod being absent.
• Adds the INSTANCE_ROUND_WON and INSTANCE_ROUND_ENDED objective kinds (a won round / any finished round of a minigame built on ziggfreed-common's instance layer; Target is : such as kweebec:chase, Qualifier the preset id, credit is per participant), with objective text templates. Kweebec Nightmare fires the shared moment, so its rounds count for quests and achievements with no MMO-side kweebec code.
• Adds a CozyTales Fishing integration (fishing adapter contributed by the mod's author, hexvane): a catch in CozyTales Fishing awards FISHING XP - the per-fish xp-map match plus a rarity payout plus a first-catch-of-a-species bonus, retunable under the reserved _Cozy_Rarity0.._Cozy_Rarity4 / _Cozy_NewSpecies keys of xp-maps.json's FISHING block - and counts toward CATCH_FISH quest and achievement objectives. Auto-detected at startup like every optional integration; inert without the mod. The shared fishing XP plumbing (xp-map lookup, bonus-key lookup, world-thread award) is extracted to one FishingXp helper all three fishing adapters use.
• Content packs (detail in each pack's own notes): the MMO Skill Quest Pack (first release, 1.0.0) ships the Emerald Wilds and Howling Sands campaigns, opened from the hub, plus the Kweebec Nightmares chain with three dailies and the Night Owl ladder awarding the Nightwarden set; the MMO Skill Stations Pack adds the Timber Rights quest that awards a Sawmill from the hub; the MMO Skill Mastery Pack adds seven damage-school mastery tracks.
• Every notice, banner, jingle and colour a quest or achievement produces is authored JSON, so a server owner can reword, recolour, resound or silence any of it without a jar. The mod ships one file per moment under Server/ZiggfreedCommon/FeedbackMoments/ (Quest_Objective_Progressed, Quest_Completed, Quest_Parked, Quest_Claimed, Achievement_Unlocked, Achievement_Claimed, Achievement_Server_First_Lost), reproducing the notices players already know: the progress tick and the green "Objective complete", the gold "Quest complete" and its jingle, the parked quest's three wordings (open the Quests page; make room, in red and silent; claim it at the Bounty Board), the legendary-chest chime on collecting a parked reward, the golden unlock toast with the achievement's own picture and the server-wide banner the announced achievements show, and the quiet amber note for a lost server-first race. Drop a same-named file in a pack that depends on this mod to replace any of them; the per-player quest-notification setting keeps deciding which of those toasts a player sees. See CONTENT_PACKS.md, "Feedback moments".
• The quest log and the achievements menu are the two tabs of ziggfreed-common's objective book, filled by this mod's deps. The page, the filters, the rows and every lifecycle verb are the library's; this mod registers one deps record (ObjectiveBookPages.deps) carrying only what the library cannot know: the themed frame, the MMO menu rail (branding, the skills header, and the cross-page navigation with its permission and feature gates, routed through the book's ext channel), the statistics column on the achievements tab with its drill-downs, bounty presentation (the Bounty pill, the board's own grade word, manage-at-the-board), the requirement vocabulary (total level, per-skill levels, achievement prerequisites), reward naming for this mod's own reward kinds, server-first claimants, the points-milestone ladder and its claim, the inventory-room pre-check in front of a quest claim, and the accept / abandon feedback moments. Achievement definitions thread their listing facts (category, subcategory, sort order, chains, feat-of-strength, legacy-since, icon) onto the shared runtime object so the book's browser reads this mod's catalogue exactly as its own pages did. Every achievements opener (/mmoachievements, the Mmo_Achievements destination, the menu rails, the tracked-achievement row, the stat drill-down's Back) lands on the book's achievements tab; the three MMO achievement pages (AchievementPage, AchievementDetailPage, AchievementSummaryPage) and their .ui templates are removed, and the achievement-menu and quest-menu wording moved to the library's own ziggfreedcommon.progression.lang keys (a translation pack overriding the old ui.achievements.* / ui.quests.* menu keys re-authors them under ziggfreedcommon.progression.book.*). Achievement criteria read on the book with this mod's own generated sentences too: the plugin installs ObjectiveTextRenderer.compose into ziggfreed-common's ONE progress.ObjectiveComposer seam, and both folds hand the shared text group a lazily-composed line per step beside its authored key, so a criterion with no TextKey reads as its sentence rather than an untitled line and one whose authored key takes arguments gets them bound.
• The quest and achievement admin commands are aliases of ziggfreed-common's /zigprogress family. /mmoquestadmin (give, reset, resetdialogues, complete, status), /quest (accept, claim, abandon, status) and /mmoachadmin reset keep their names, their argument shapes, their permission gates (mmoskilltree.admin / mmoskilltree.command.quest) and their wording, and each verb now speaks to the shared runtime the library owns - the one quest and achievement engine pair, the subject the registered store understands, the registered call scope around every mutating call - instead of to a component of this mod's own; the same verbs are reachable mod-agnostically as /zigprogress quest , /zigprogress achievement and /zigprogress memory forget under engine-derived nodes (ziggfreed.ziggfreedcommon.command.zigprogress...), documented on the library's side. What stays this mod's own: /mmoquestadmin reload (this mod's owner files and pack layers; the shared assets are /zigprogress reload's), /mmoquestadmin list (this mod's category-tagged view), the OFFLINE half of /mmoquestadmin complete (the reward spool needs the directory of everyone who has ever connected, which only this mod keeps; the shared verb needs the player online), /quest's conversation-only accept refusal and its inventory-room check before a claim, and the release of the server-first claims a player won on /mmoachadmin reset (they live in this mod's own claim table; the shared verb wipes state and says the claim is still recorded). Two behaviour changes: /mmoquestadmin give and /quest accept now settle a step the player already satisfies the moment the quest is taken on (a quest given to somebody past its finish line pays or parks at once), and /mmoquestadmin reset wipes an ORPHANED record (an id the catalogue no longer knows but the player still carries) instead of refusing it. /mmoquestadmin resetdialogues reads "Forgot everything every conversation remembers about X" now, which is what it does. The three page-openers keep their names and gates: /mmoquests opens the shared objective book on its quests tab, /mmoachievements opens it on its achievements tab, and /mmoquestui opens the shared NPC quest page.
• The admin configuration menu becomes a router hub over six focused section pages. /mmoadmin opens a compact hub that routes to General Settings, Command Integration, Leveling Parameters, Boost Stacking Limits, Rested XP and HUD & Abilities - each section a page of its own with its own status line and a Back that returns to the hub - beside the per-config editors, which all stay one click away. The hub keeps the Perfect Utils warning, the reload actions and the Danger Zone, gains an Edit Themes button (the theme picker was previously reachable only by command), and its own Back lands on the active top-level menu (the class hub on a class-pack server) instead of always the skills page.
• The quest and achievement system toggles move onto a shared Progression Systems admin page. The hub's new Progression Systems button opens ziggfreed-common's progression admin page, which lists every server-wide progression switch a mod registers; this mod registers its quests and achievements switches over skill-config.json's existing toggles (both apply immediately), each with a hint naming the staff bypass permission that keeps the system on for staff while the server-wide switch is off.
• Adds a World Rules editor to the admin hub. A new World Rules button opens a page listing every effective per-world rule - its id, what it targets (the Where summary), its key knobs and whether it is on - with a per-rule ON/OFF toggle, an edit card for the rule's XP multiplier, its three bonus switches and its two skill lists, and a per-rule Reset that drops the owner override. The page writes mods/mmoskilltree/world-rules.json rule bodies through the same codec the pack layer decodes and never writes the retired flat Match key; authoring a NEW rule and editing Where targeting stay file-authored, which the page says on its face. Alongside it, a world rule gains an optional Enabled leaf (absent = on): a disabled rule stays loaded and listed but matches no world, so a rule can be switched off and back on without re-authoring it.
• Adds a Power Level editor to the admin hub. A new Power Level button opens a page over mods/mmoskilltree/power-level.json: the Enabled switch and the DefaultMode preset up top, then every numeric leaf grouped the way the schema groups them (Clamp, the pillar factors, and the three mode weight maps over the six builtin pillars), each row showing its default beside its current value with a Default/Override tag, per-leaf editing and per-leaf reset-to-default. Every write is a partial overlay - an untouched leaf stays absent from the file and keeps inheriting defaults plus pack content - and the per-stat StatRewards factor map and custom pillar weights stay file-authored. Both new editor pages also surface their content validator's problem count.
• Adds a horizontal-align control to the ability cooldown HUD's admin section (the stored position always carried both axes; only the vertical half was editable), and corrects the ability-HUD note: position changes apply live to every online player, no reconnect needed.
• Localizes the whole admin hub family: every action status line, section header, field label and dropdown option (the leveling formula and boost stack mode included), the milestone XP preview, the reset warning and the previously untranslatable in-layout labels now resolve through lang keys, and the reward-type dropdowns in the skill-tree editors read the localized reward names instead of raw enum text. all nine languages ship in this release.
• Retires the admin page's "Default Server Language" dropdown: display text has been client-resolved since 1.4.0, so the control no longer changed anything a player sees (the defaultLanguage config leaf stays, read by the XP-boost command scope and a deprecated external-plugin shim).
• Fixes three admin-hub defects: an event carrying no action could crash the page handler, the Boost Templates editor opened without re-checking the entitlement that hides its button, and a flipped toggle kept its previous state's hover and press colours. Removes the page's dead, commented-out combat-XP blacklist remnants (the feature lives in /mmoconfig blacklist).
• The two requirements editors get the same treatment. The Item Requirements page gains an All category tab listing every default and every saved override unfiltered - an override outside the named item-id prefixes, or a disabled override with no default underneath, was previously invisible in the UI and could never be reset there; every override row now shows Reset. The permanently-empty Armor tab is dropped (no armor requirement defaults ship; an armor override still shows under All), the Add/Update validator now refuses a requirement on a display-only skill id no player can level (previously it accepted one and saved a gate no matching item could ever pass), and the format hint's example names live built-in skills (it still said SMITHING, which this release moves out of the built-in roster, so the page's own validator rejected the example it printed). Both requirement pages are fully localized - requirement summaries resolve skill names in the viewer's locale, and the Tool & Weapon page's category labels separate from the stable internal ids its state machine keys on - repaint their tabs and toggles across all three button states so a selected tab or an OFF toggle no longer flips colours on hover, replace every local sound-less button style with the shared sounded set, and the Mob Weapons tab's empty state now says what is true: no defaults ship, any weapon works until a pattern is added.
• The Item Rewards screen answers every click. Several button paths (clicking the tab already selected, prev/next with nowhere to go, a malformed claim event) sent no response and left the client stuck on the black loading screen; every path now responds. The page also drops its private /give parser and name/description resolvers for the shared reward-preview seams - the private copies had drifted: a currency-grant reward rendered no card at all while still being counted, so the "X/Y Claimed" header could never complete, and a /give missing its target argument titled the card with the flag text - so currency rewards show their cards, the header counts exactly the cards on screen, and stack quantities render grouped. The class moves to pages/skill/ beside the screen that opens it: it is the player-facing milestone claim screen, not an admin config editor.
• The boosts and XP admin quartet (Award Boost, Boost Templates, XP Overrides, XP Token Overrides) rebuilds on the shared admin styling: every button clicks audibly through the shared style set, the Award Boost page sits in the standard framed container like its siblings, tab / chip / toggle painting routes through the shared helpers, and the three overrides tables share one row look with the Reset button appearing only on rows that actually have something to reset.
• Fixes the Award Boost page's dead "Production" target: the button targets the real Crafting category now, so token awards, instant global activations and minted permission nodes for that column all work (nothing in the boost stack ever parsed "production", so every use of that button failed or granted a node that could never fire).
• Adds a Misc tab to the Boost Templates and XP Token Overrides admin pages, so MISC-category skills (Taming, Building) can be tuned and targeted like every other category - their default per-skill templates and boost-token items existed but were unreachable from the UI - and the Boost Templates page can mint category-wide Misc templates.
• Admin-awarded boost tokens for offline players queue by player UUID only, the same rule as the pending-rewards spool: an award for a name the server has never seen is refused loudly instead of waiting forever under a name, and a queue an older version filed by username still delivers when its owner connects. An online token award records the player-data dirty mark, so it survives under the database backend too.
• The Award Boost page says when permission boosts are entitlement-gated off: a warning under the permission preview and on the grant confirmation, instead of granting a node that silently never takes effect.
• The four pages' remaining hardcoded English is keyed and client-localized: statuses, row status labels, table headers, field labels, tab labels, empty-list notes, unit suffixes and the ON/OFF toggle all resolve in the viewer's own locale, and the category chips on the Boost Templates and XP Token pages render through the shared rich-button path so their labels and active tint actually show.
• The Mob Drop Commands editor tells the truth and stops crashing its admin. The status line painted a structured message onto a plain-text label, which disconnected the admin on every add, remove, disable or toggle; it now paints through the shared status seam. The pool table drops its DELAY and TIER columns (the per-pool stagger and elite-tier filter those columns described are retired schema) for a Form column naming whether each pool's chance is a flat number or a stat-driven formula, so every value sits under its own header again. The placeholder hint and the admin help pages describe {tier} honestly (it resolves only when a companion mod attributes a kill rarity; MMO Mob Scaling does) and stop advertising the retired delay. Adding a fallback pool (empty pattern) no longer raises a bogus error or paints its success line red, and a hint under the buttons says a disabled pattern also stops that mob's bonus-drop kill rows. Saving a pool no longer writes the retired requiredTier key back into mob-drop-commands.json or the generated reference file.
• The Mob Kill XP editor joins the shared admin chrome. The page moves onto the shared overlay and container with the standard title bar, every button gets the shared sounded styles (the whole page was silent on click), the weapon-scaling row is hidden for non-admins instead of shown dead, and the help button no longer strands a non-admin on an infinite loading screen.
• Editing a command reward preserves every authored field. Re-saving a reward from the admin page rebuilt it from the four form fields, silently dropping its description, description key, auto-claim flag and currency dependency and forcing it to run as console; the untouched fields now carry across (the auto-claim toggle carries all of them too). The level-jump button answers an empty level field with an error status instead of an infinite loading screen and is labelled Go instead of the misleading "Add Tier", the display-name cell renders its parameterized fallback correctly (it printed a literal {0} for key-less rewards), and the current-skill label resolves through the localized skill-name seam.
• Localizes the three drops/rewards admin editors (Mob Drop Commands, Mob Kill XP, Command Rewards) end to end - titles, table headers, field labels, buttons, empty states, row statuses and every status message resolve through lang keys (all nine languages ship in this release) - and routes their row striping, status painting, toggles, number formatting and event bindings through the shared render seams instead of per-page copies.
• Hardens the Custom Skills admin page. Fixes two client crashes (the CATEGORY column of both tables pushed a client-resolved name into a String-only sink), lists pack-provided custom skills in their own toggle-only section so the disable-by-id switch can actually reach them, keeps a skill's authored descriptionKey and requiresFeatures when saving from the admin pages (previously silently deleted from custom-skills.json), makes the per-skill cap grid honest about the three-layer max-level resolution (a typed cap equal to the shared default now still overrides a pack-authored cap, instead of silently snapping back to the pack value; the hint says so), and locks the Skill ID field while editing so a rename can no longer create a duplicate skill.
• Hardens the Custom Skill Wizard's edit mode. Skill-tree tiers are keyed by their data tier (a sparse or standalone-tier tree previously round-tripped corrupted, mislabelling claimed rewards), opening the wizard on a sparse tree no longer crashes before the page responds, the Skill ID is locked while editing (a changed id previously saved a SECOND skill and orphaned the original's XP map, command rewards and tree), and Skip on the skill-tree step leaves existing tiers alone instead of wiping them. The step-4 reward form gains a Target field, so a wizard-authored reward can target a skill or combat type just like one authored on the overrides page, and the permission-denied view hides the whole form.
• Fixes a Skill Tree Overrides reset bug. Reset to Default on an added tier no longer makes the tiers above it unreachable (the config re-index now rebuilds each shifted node at its new tier, covered by a regression test); the page opens on the first selectable skill instead of always Mining, and its skill selector no longer offers owner-disabled skills.
• Localizes the three skill-editor pages' remaining English: every status line, empty state, tier and reward status word, the delete-confirm and Remove labels and the TYPE column now resolve through lang keys, and the row buttons on those pages click audibly through the shared admin button styles. all nine languages ship in this release.
• The White Label master switch now actually governs the menu accent recolor. The accent tint used to keep painting every themed menu while the admin page's Enable White Label toggle was OFF (the recolor checked only the Pro entitlement); it now applies only while white label is enabled, the same gate every other branding surface already honors. /mmoconfig reload also re-reads a hand-edited white-label.json, which previously was only read at startup.
• The White Label admin page is rebuilt on the shared menu family. It wears the shared decorated frame and the server's own active theme and accent, its buttons use the shared styles (every click audible), and every label and status line resolves through lang keys. The accent tint strength, the live white-label.json knob deciding how far the accent is softened before it recolors the menu, becomes editable beside the accent color, and the color preview swatch shows the softened color the menu actually paints instead of the raw hex (and hides when the accent is empty, which means no tint at all). The Server Description and Branding Position help texts now describe what the branding really does (left mode brands the side panel and keeps page titles; right mode replaces the page title with the server name), and a flipped position choice repaints all three button states so hover never flashes the stale selection.
• The theme picker reports the honest paint state. A premium theme selected without Pro used to show as Active while the menu actually painted the free default; that row now reads an amber "Selected (needs Pro)". The active row's indicator is a labeled Active tag instead of an unlabeled square, a theme without an authored display name shows its id instead of a raw lang key, and the footer upgrade hint points at /mmofingerprint (the entitlement-registration command) instead of a command that does not exist.
• The in-game Configuration Guide catches up with the whole 1.6.0 admin surface. Eleven new cards - Quests, Achievements, Abilities, Ability Mastery, World Rules, Power Level, HUD Layout, Menu Themes, NPC Placements, Config Presets and Content Packs - each with the full overview / how / examples / tips treatment and a settings button that opens the matching page (the two new editor pages, the HUD section, the theme picker, the shared Progression Systems page, and the presets page, which stays entitlement-gated like its hub button). Two topics that had drifted from the mod are rewritten truthfully: Mob Drop Commands no longer teaches the retired per-pool delay and elite-tier fields, and Boost Templates now documents the real structured permission node (mmoskilltree.xpboosts.....) and the player-activated flow instead of an invented mmoskilltree.boost. always-on model. The XP Maps tip now gives the --args= command form the parser actually binds, the dead Elite Mobs guide topic and the rest of the orphaned elite-mob admin keys are gone from all nine languages, and the guide's card buttons are audible and drawn from the one shared button style set.
• Config presets cover the whole 1.6.0 config surface. The export list grows from 12 to 25 entries: mob-drop-commands, world-rules, power-level, mastery, ability-settings, ability-overrides, hud-layout, feedback, combat-text, reward-icons, integrations, white-label, and the achievements/ directory (achievement files plus point milestones) join the original set. Applying a preset reloads every covered config in boot order - boost templates re-arm the boost service, integrations re-resolve their adapters, and ability overrides re-fold onto the live catalog - and an achievements apply never touches the server-first claim ledger.
• The presets page is fully localized and hardened. Config names, counts, fallbacks and every status line resolve through lang keys in the player's own locale (the import result is structured data the page renders, never a pre-composed English sentence); a config key read from a preset FILE is rendered through a safe template instead of being interpolated into UI markup; an event carrying no action no longer leaves the client loading; and the presets and help page family draws its buttons, section cards and toggles from the shared style sets with click sounds throughout.
• Adds /mmomigrate, an in-game admin/console command for the 1.6.0 content migration. scan (the default) walks mods/mmoskilltree/ (including the .legacy renames and timestamped backup/ copies earlier boots left behind) plus every installed content pack, and writes one Markdown report (mods/mmoskilltree/migration/report-.md) classifying every file the same four ways the docs-site Migration Converter does: converted, needs hands (with the target shape quoted), handled by the mod at boot, or dropped with the reason. --action=owner --confirm=yes applies the safe owner-file conversions in place: the world-rules Where rewrite, the retired ability-body-key fold in ability-overrides.json, and the four server settings still sitting unread in a retired abilities.json, lifted into ability-settings.json and hud-layout.json. Every file is backed up first, written atomically, decoded back through its own codec, and rolled back if that decode fails. --action=pack reports each pack's stale content and points at the web converter; packs are never rewritten in game. Everything boot already migrates is reported and left alone: one file, one writer.
• /mmomigrate and the docs-site Migration Converter learn the progression wave's retirements together, one vocabulary, corpus-proven from both sides. Both know placed-blocks.json (renamed to .legacy at boot, never read; the row names the shared ledger mods/ziggfreedcommon/placed-blocks.json and the four skill-config.json knobs), the three commerce owner files currencies.json / bounty-board.json / token-shop.json (renamed to .legacy at boot; their residue is work for the web converter), database.json (unchanged, no per-domain knob; a file selecting a database backend is told once that rows filed under the retired QUESTS / ACHIEVEMENTS domains are never read again), the retired achievement announcementCommand (REPORTED with the exact replacement in the boot warning's words: a Command group or a When {achievement: } Variants entry on Achievement_Unlocked.json; never converted), the written-out Meta.mmoskilltree.Announce.Title / Body (the converter renames them onto TitleKey / BodyKey; /mmomigrate names the leaf), a pack Server/MMOSkillTree/WorldRules/ file still spelling the flat Match string, and a Where naming a retired world selector. Both closed boot-rename tables list the same eleven names; a current shared-store file is no longer flagged merely for carrying a Meta.mmoskilltree block. Seven corpus cases join src/test/resources/migration-corpus/, none edited.
• Both migration tools cover the ability schema's in-cycle respellings through ONE declarative table (ability/AbilityTopLevelRenames, mirrored in the converter's abilities.ts): Identity.NameKey/DescKey to TitleKey/DescriptionKey, XpRouting.HeldExclude to ExcludeSkills, PassiveTrigger.RequiresWeaponSkill (scalar) to WeaponSkills (array), the PascalCase PassiveTrigger.On vocabulary, and the deleted Cost.Costs stripped with a named report; RetiredAbilityKeySweep warns on all of them at boot and --action=owner converts them in ability-overrides.json. The retired pack-control key list gains the six commerce keys (MobDrops is dropped from it - git history shows it was never a control-key leaf), an unrecognised backup/ leftover is now reported as "read it before deleting" instead of "safe to delete", and the XP-reset spool's live file and its backup (which holds resets queued under names no player resolves - re-run the command once they connect) are both classified truthfully. A coverage test now asserts every LegacyOwnerFile call site has a BootHandled row, and a real corpus case pins the respelling wave fixture-to-fixture on both sides.
• /mmopacks --action=export now writes the shared layout. Exporting a server's custom quests and achievements emits one file per entry in the shared schema the engines read (Server/ZiggfreedCommon/Quests//.json and Achievements//.json, manifest at the zip root), converting the owner files' older authoring shape on the way out: the flat requirement fields fold into one Requires block, repeatable/cooldownSeconds become the structured Repeat group, historical reward kind spellings become the registered ids, and an objective array becomes the id-keyed map. An exported pack loads on any server running this version and scans clean by /mmomigrate; a leaf the shared schema has no home for (a raw description, variables, the markdown fields) is named in the server log rather than dropped silently. Each emitted file is proven in the build by decoding it back through the same shared codecs the server folds at boot.
• An existing save's quests and achievements move across by themselves. The first time each player connects after the update, everything they had - active quests and their objective progress, completed quests and their cooldowns, tracked pins, how many times they have finished a repeatable, earned and claimed achievements, criterion progress, points milestones, pinned achievements and unlock dates - is copied onto the record the shared engines read, once, and never again. Nothing is asked of a server owner, and nothing is lost.
• Adds a Quest Book item: a non-consuming companion to the Skills Menu Scroll that opens the quest log directly. Granted the same way, as a second reward on the getting_started and forgot_something tutorial quests.
• Adds native-asset ability authoring: every active ability and triggered passive is now a Server/MMOSkillTree/Abilities/.json asset (Pattern A, PascalCase keys, the codec IS the schema), and 97 defaults ship at that path in the jar (63 active abilities plus 34 triggered passives). Content packs can author and override abilities for the first time (defaults < pack < owner precedence, same as every other custom asset type); a sibling variant reuses a base ability via native Parent inheritance instead of duplicating the whole body.
• Adds ability-overrides.json, a lightweight owner tuning layer (mods/mmoskilltree/ability-overrides.json) for retuning one ability's cooldown, cost, damage, or any other field without authoring a full content pack. A partial body overlays per leaf onto the already-folded ability (defaults + pack), so overriding just a cooldown never nulls out that ability's cost, effects, or presentation.
• Adds a hard break of the legacy abilities.json override format: on first start after upgrading, any file found at mods/mmoskilltree/abilities.json is moved (never read, never silently deleted) to a timestamped file under mods/mmoskilltree/backup/, with a startup warning explaining that it is not read and pointing at the new format. Re-author any customizations as ability-overrides.json entries or a pack asset; see CONTENT_PACKS.md.
• Adds AbilityValidator, a content audit over every authored ability (identity and cooldown/cost sanity, ABILITY_UNLOCK placement in the skill tree, every authored mastery/reward modifier resolving to a real ability field, and sound/particle/effect asset references), surfaced by the startup content audit and /mmoconfig validate.
• Adds /mmoability reload (admin), which re-folds the ability catalog from the current pack state plus a fresh disk read of ability-overrides.json and re-validates it, so a pack author or server owner sees an ability edit take effect without a server restart (a brand-new zipped pack drop still needs one).
• Adds /mmoability unlockall [--arg1=all|actives|passives] and /mmoability lockall (admin), a self-only test pair for trying the ability roster without levelling into it. unlockall grants every catalog ability (or just the bindable actives, or just the triggered passives) to the sender; lockall runs the existing ability-state reconciliation, so unlocks backed by a currently-claimed ABILITY_UNLOCK skill-tree reward survive and only the test grants are stripped, along with their cooldowns and slot bindings.
• Adds a two-level ability presentation: the ability-level cast moment (launch sound, cast animation, camera shake, one feedback moment) plays once per cast, while every step in an ability's effect chain carries its own presentation moment (and a step's own intrinsic second moment, like a projectile's impact), so a multi-beat ability tells its whole story instead of one flat cue.
• Adds per-step ability description fragments: an ability's tooltip composes from its actual effect-step chain (damage, cooldown, cost, on-hit effects, and so on) instead of one hand-written description string. An ability you've unlocked folds in your own current gear and mastery bonuses, so the tooltip's numbers match what you would actually cast right now; a preview of an ability you don't have yet (a reward or shop card) still shows its authored base value.
• Adds a VFX and SFX pass across the whole ability roster (65 abilities at the time of the pass; later additions in this cycle ship their own): a cast-moment sound and particle burst (plus, on the heaviest hits, a camera shake) plays once per cast, every effect step in a multi-beat ability carries its own particle treatment (impacts, damage-over-time ticks, buff auras), and a new Teleport "Arrive" moment plays a sound and particles at the destination of a blink instead of only the departure. Projectiles that only played a sound on impact now also burst with particles, several previously-silent capstone zones (Cataclysm's aftermath crater, Concussive Reverb, Skewer, and others) gain a tick or telegraph treatment, previously-invisible party buffs (like Phalanx Master's formation aura) render a visible aura, and damage-over-time stacks (Burn, Bleed, the icy Slow stack) show a consistent visual wherever they apply. Ships as 18 new MMO_* particle, entity-effect, and (the mod's first) model-VFX assets, each composed from verified vanilla particle spawners rather than new art.
• Adds a void-purple dissolve feel upgrade to Vanish and Shadowstep: both now carry a shared MMO_Dissolve_Void effect (the model-hide shroud, replacing an off-theme cyan placeholder) instead of two different treatments. Shadowstep adds server-enforced invulnerability for the length of the blink, an origin dissolve burst, and a destination arrival flash and sound; Vanish gains a matching void shroud sound.
• Adds registry-backed particle, camera, and feedback validation to AbilityValidator: a Presentation.Particles/Camera id is now checked against the real particle-system and camera-effect registries (previously particles were shape-only and camera was unchecked), and a Presentation.Feedback value is checked against the FeedbackEvent vocabulary. Two new warnings enforce the two-level presentation model: an ability-level Presentation authored on a passive ability (dead - a passive never plays a cast moment) and a Camera/Feedback leaf authored on a step-level Presentation (reserved - nothing below the ability level plays it).
• Adds 8 default abilities back onto the new step-engine asset schema as Server/MMOSkillTree/Abilities/*.json files: Blood_Pact, Challenging_Shout, Forest_Warden, Iron_Bulwark, Prospectors_Focus, Smoke_Bomb, and Soul_Drain (active abilities), plus Wind_Dancer (an ACROBATICS triggered passive). The jar-bundled default roster grows from 65 to 73. Each ships with a matching cast VFX/SFX pass, including roughly 8 new MMO_* particle and entity-effect assets, composed from verified vanilla particle spawners the same way the rest of the ability roster was; a couple of the eight reuse an already-shipped, previously orphaned effect verbatim instead of authoring new art.
• Adds 10 new active abilities built on native Hytale weapon-chain and movement mechanics: Acrobatics gains Skyward Leap and Backflip Disengage (pure mobility, no damage), Blunt gains Bull Rush and Ground Slam, Axes gains Tempest, Swords gains Vortex Lunge, Polearms gains Javelin Toss, Archery gains Hookshot Arrow and Explosive Shot, and Magic gains Arcane Lash.
• Adds two new deployable abilities and a new summon: Archery's Sentry Turret and Magic's Flame Totem each plant a structure that fights nearby hostiles on your behalf for a limited time, and Archery's Summoned Wolf calls a temporary wolf ally that hunts hostile mobs and never targets a player. Kills and per-hit XP from all three credit the summoning player. Together with the 10 abilities above, the default roster grows from 73 to 87.
• Adds the ability for a non-player mob to cast from the same ability catalog players use, complete with that ability's real cast presentation and effect chain, through a new MMOSkillTreeAPI.castNpcAbility entry point. Inert on its own; a fourteenth new ability, the NPC-only Dragon Arcana, ships as a demonstration caster ability, and the standalone MMO Mob Scaling companion mod (1.1.0) is the first real consumer, giving certain mobs a per-role caster roster and wind-up animations before they cast.
• Adds the ability-improvement platform: a mastery node, quest, dialogue, or shop entry can now grant a standalone, player-facing improvement to an EXISTING ability instead of only a full replacement ability. A new AbilityMod content type (pack-authored under Server/MMOSkillTree/AbilityMods/*.json) names a target ability and a list of modifiers, including a new splice-a-whole-effect-step modifier kind that inserts an authored effect (a bonus on-hit proc, an extra beat at the start or end of the cast) into the target ability's own effect chain rather than only tuning an existing number. A granted improvement is delivered through the same unified reward pipeline every other reward uses (quests, dialogues, shop entries), persists per player, and can be granted or revoked by admins via /mmoability grantmod/revokemod for testing or manual awards. See CONTENT_PACKS.md's "Ability improvements (AbilityMods)" section for the authoring shape.
• Adds a load-time check that catches an ability improvement or mastery bonus landing twice on the same hit (once as an ability-cast bonus, once again as a weapon-swing bonus); content authoring now gets a loud error instead of a silent double-counted number. Caught and fixed one such case already present in the shipped mastery content (Piercing Shot's pierce/damage mastery line).
• Adds the first seven of the damage schools a hit's damage type can carry: Fire, Ice, Lightning, Water, Arcane, Void, and Poison (Life and Physical complete the roster at nine in the completion pass above, and the Arcane Essence entry beside it settles every school's essence mapping). Fire, Ice, and Poison ride vanilla causes (Poison as an overlay filed under Elemental); Lightning, Water, Void, and Arcane are MMOSkillTree-authored sub-types of the vanilla Elemental cause. A full roster pass retags frost-identity abilities onto Ice, arcane-identity abilities onto Arcane, Tide Caller onto Water, and moves Riftblade onto Void (several of these previously fell back to untyped Physical damage silently, a pre-existing bug this pass also fixes; the drain kit around Soul Drain lands on the Life school added by the completion pass above); ability tooltips now name the school on every damage/dot/zone line.
• Adds a SCHOOL_RESIST skill-tree reward type: a tree node can grant permanent resistance to one of the damage schools, stacking across every claimed node, surviving relog and world hop, and removed on respec or a full skill reset.
• Adds a full stat substrate so gear, potions, content packs, and sibling mods can grant any of the mod's combat/utility scalars (defense, crit chance, crit multiplier, lifesteal, combo damage, fall damage reduction, effect duration, cooldown reduction, luck, bonus XP), a per-skill damage bonus for any active skill, or a per-school damage bonus, through an ordinary item or effect StatModifiers block, with zero plugin code.
• Adds six ability-specific stat channels (ability range, radius, duration, cost reduction, i-frame duration, and pierce count) that gear and mastery can grant bonuses to directly, each named on an item's tooltip and each capped by a server-tunable clamp so a stack of ability-boosting gear can't push a single ability's number past a sane bound.
• Adds a second way to grant an ability improvement: a piece of gear can now grant an AbilityMod just by being worn, held, or carried in the offhand (a new ItemAbilityGrant pack asset, matched by exact item or by the item's own tag group), on top of the existing mastery/quest/shop grant path. A rolled or hand-authored item stack can also carry a pre-stamped ability mod directly in its own metadata, the same per-stack blob item enhancement already uses, so a piece of loot can arrive already boosting a specific ability with no separate reward step. Ships with six example gear ability mods and three example grant items (a battlemage armor set, a crystal flame staff, and a Stormbound Charm offhand trinket), plus a live drop-table example: mining a Zephyr gem block has a chance to drop a charm pre-stamped with a Vortex Pull range bonus.
• Adds two Defense ability stubs, Guard Stance and Parry Riposte, over Hytale's native weapon block/parry hold mechanic (primes brief stamina-break immunity while holding a block or parry window); no default weapon wires the hold yet, so both are an unexercised code path pending a weapon or content-pack hookup.
• Adds native crowd-control diminishing returns: a stun or stagger from an ability (Shield Bash, Shield Slam, Paralyzing Dart, Berserker Charge) also builds the target's native Immunity toward a temporary CC-immune window, so repeated stuns in quick succession taper off instead of chaining indefinitely.
• Adds a specific reason message when a cast is refused (on cooldown, not enough of the required resource, the ability isn't unlocked, your class can't use it, or its own conditions aren't met), shown for the exact check that blocked it instead of one generic failure.
• Adds Frost Stream, a Staves ability unlocked in the staff skill tree: a staff-gated channeled ice beam that damages and slows everything it holds, refreshing the slow's duration on every tick instead of stacking it.
• Adds Void Slam, a Staves ability unlocked in the staff skill tree: a staff leap-slam that deals void damage, knocks nearby enemies upward, and leaves behind a void damage-over-time field where it lands.
• Adds an authorable Channel presentation group to the MmoBeam step (a per-ability channel-loop sound and particle effect for a held beam; an ability that authors none keeps the previous flamethrower-loop default, so every already-shipped beam ability is byte-identical) and an Overlap knob to MmoApplyEffect controlling how a reapply of the same effect while an instance is still active is resolved: Extend (still the default when unauthored, so every ability shipped before this knob existed attaches byte-identically to before) adds the new attach's duration onto the active instance, the right call for a one-shot proc meant to stack; Overwrite and Ignore are newly authorable, letting a repeat-tick channel refresh its effect to a flat duration on every tick instead of climbing without bound. Frost Stream is the first ability to author both: its own ice-wind channel loop, and Overlap: Overwrite on its per-tick slow so the slow refreshes to a flat 1.5 seconds instead of piling up additively across its 50-tick channel, which would otherwise have let the slow climb to roughly 70 seconds of stacked duration.
• Fixes Wind Dancer's chained Shadow Pounce riposte bonus never applying after a perfect dodge; the damage multiplier now actually lands on the follow-up strike.
• Reworks Flame Stream onto the native Crystal Flame staff's stream presentation: the ability composes the vanilla staff's own flame-stream chain for its visual and audio beat while keeping every MMO-side concern intact (gear folding, per-cast modifiers, school-tagged damage, and XP attribution), so the sprayed cone the player sees is the cone that actually burns.
• Adds a shared slam presentation treatment derived from Ground Slam (weapon-trail arc on the wind-up plus a matching impact particle and sound beat) to Concussive Dive, Molten Slam, Rending Slam, and Crippling Slam, so the whole slam family telegraphs and lands consistently. Crippling Slam's slow radius is matched to the radius its own ground impact draws, closing a see-one-thing/get-another mismatch.
• Fixes ability-sourced damage-over-time and ground-zone ticks (Molten Slam's fire pool, Rending Slam's bleed, and every other ability-created DOT or zone) awarding XP to Magic regardless of which skill cast the ability; a tick now credits the casting ability's own declared XP skill(s), matching how that ability's direct damage already attributed.
• Fixes Explosive Shot only ever detonating on a direct entity hit: it now looses a real projectile that resolves and detonates on terrain impact and on a clean miss as well, so the shot always produces its blast where it lands.
• Fixes the held-weapon cast gate refusing with a genericized message: the refusal names the required weapon category (or categories) again, localized, restoring the specific feedback the singular-field gate used to give before the HeldWeaponCategories sweep.
• Fixes ability descriptions falling back to a generic "does something" line: every effect-chain node kind now contributes a real, number-bearing description fragment, so an ability's tooltip and its skill-tree card describe the actual numbers everywhere instead of a placeholder for the uncovered kinds.
• Fixes Vortex Lunge's opening spin dealing no damage: the phase-one spin lands its authored damage before the lunge follows through.
• Fixes Hookshot Arrow's pull continuing to read as a light shove even with its distance scaling already correct: the pull previously routed through the engine's shared knockback pipeline, which multiplies a pending knockback's horizontal components by an internal 25x scale factor tuned for an ordinary hit's small nudge, crushing the hookshot's single larger pull down to almost nothing. The pull now writes the target's native Velocity component directly in one bounded Set instruction instead, the same sink the vanilla LaunchPadInteraction uses, mirroring that same 25x horizontal pre-scale by hand so the delivered impulse still matches vanilla feel; the vertical lift stays unscaled, matching how vanilla knockback treats it too.
• Fixes Shield Bash's impact flash rendering on the caster instead of the target it struck: a landed bash now chains a victim-anchored, standalone 0.4-second impact-flash effect targeted at the struck entity, on top of its existing impact sound; a whiff never reaches that branch and stays silent.
• Fixes Flame Stream's fire jet spawning from a disconnected point when cast bare-handed: the bare-hand jet now anchors to the player skeleton's own attachment socket using the same emitter pose the held-staff beat already used; casting with a staff in hand is unchanged.
• Fixes drinking a Shadowstep potion sometimes consuming the item and applying its cooldown without the teleport ever firing: the consume chain's step order is restored to payload-then-debounce with a fail-on-blocked guard, and the sickness marker moves onto the cast node's success path, so the potion's cast completes reliably every time.
• Adds rich markup to ability tooltips: bold stat keywords, damage numbers tinted by that hit's damage school via the DamageSchools color palette, and italic flavor text and conditions, all authored as markup directly in the lang values themselves (the only place the tooltip's flattened text sink can parse it). Every tooltip number now renders through a typed Message parameter ({N, number} for an integer slot, a typed double elsewhere) instead of a bare interpolated string, and every server-formatted number pins Locale.ROOT, closing off a class of locale-dependent number-formatting bug.
• Extends the "With your bonuses" tooltip breakdown: a gear cooldown-reduction bonus now folds in as its own gear term using the same formula the cast pipeline applies at cast time, and any on-hit school or weapon damage bonus your gear grants renders as its own labeled section instead of disappearing into the base number.
• Adds a trigger-condition lead line to every triggered passive's tooltip and claim card (previously invisible on 34 abilities), and reorders the description walk to match the ability's real execution order. Zones, deployables, marks, heals, and buff auras each describe their own real knobs instead of a generic line (a crippling effect reads its slow field, a buff aura names its next-strike damage bonus), repeat-hit counts render, and a cast's own gating conditions (a required weapon class, a resource threshold) now render as an informational tooltip line rather than surfacing only as a refusal message when you fail to meet them. The native ApplyForce description fragment is direction- and magnitude-aware (a vertical recoil kick, Explosive Shot, reads as a kickback rather than a leap; a genuine leap, Skyward Leap, reads its own drift direction), and a duplicate area line is suppressed when a scope qualifier resolves to the same number as its own child radius (Frost Nova, Blood Pact) or when a selector's scope note would otherwise repeat across every surviving hit line (Arcane Lash); two genuinely different numbers still both render.
• Fixes an ability's authored SummaryHidden flag, meant to suppress a purely cosmetic effect-chain line from its tooltip, silently doing nothing: the description walk now resolves it through a getter-first reflective lookup implemented across all 21 step Types, and the content validator delegates to that same lookup instead of carrying its own copy. Shadowstep and Vanish, whose own teleport-effect line had no way to hide until now, suppress that line as authored; the ability-body fidelity digest treats SummaryHidden as presentation-only, the same as $Comment, so an edit to it alone no longer fails the build.
• Adds a cooldown/cost envelope line to an ability's claim card (a skill-tree, quest, or shop reward preview) and a content-aware line cap in place of a flat three lines. Extends reward-chip formatting to cover every reward type: a negative value now renders with the correct sign instead of +-8%, and a summon-count reward pluralizes correctly through a client-side ICU token instead of always reading like Summons 1 allies. Fixes a claimed reward's HP-range gate silently disappearing across a RewardData override round-trip, a mechanic loss with no visible symptom until the gate simply stopped applying.
• Adds named status-effect icons to armed and triggered abilities: while a next-hit buff or a triggered passive is active, a named icon now joins your other active effects instead of the ability going unrepresented, backed by 40 aura assets (19 newly authored for this pass). Several shared cosmetics that previously mislabeled multiple unrelated abilities now split into their own per-ability badge (Vengeance, Challenging Shout, Blood Pact, Clean Kill, Iron Bulwark), and the ability-less dodge counterattack, a damage-system reaction rather than a cast, now badges itself too through a new CommandBuffer.tryAttach overload since it has no cast path of its own to hang a badge on. Every ability's Identity.Icon is unique across the roster (13 duplicate-icon groups resolved, including a five-way shield-icon collision and an unarmed-pickaxe misfit now reading as claw and gauntlet icons), so two abilities are never mistaken for each other at a glance.
• Adds a cosmetic-only ability feel pass: an empowered strike (Vampiric Strike, Wind Dancer's riposte, Paralyzing Dart, Smoke Bomb's opener, Assassinate) now plays its own consume cue instead of landing silently, Smoke Bomb visibly throws its bomb with a camera kick, and Shadowstep's teleport plays a matching sound and particle burst at its destination as well as its departure. A buff now plays a distinct removal cue when it expires instead of dropping off silently, bleeding and marked targets carry a visible victim tint, seven buff auras gain a body glow, Prospector's Focus gains a first-person-only sparkle so its bearer can see their own buff, a cleanse effect gains tick cues and a screen overlay, and the frostbite capstone's proc now bursts a victim-anchored frost mist and ice crack instead of firing invisibly.
• Fixes ability names, status-effect badges, and tooltip text shipping English-only on non-English servers for this cycle's new content: all 8 non-English locales are now key-complete against en-US for every ability, status-icon, and tooltip key this cycle added.
• Fixes the mastery cape names (reward.cape.*, all 20) and the short HUD stat codes (reward.short.*) shipping as untranslated English copies in most non-English locales: every one of the 8 non-English locales now carries real translations, with each locale keeping an English code only where it is the natural short form there.
• Adds interactive work stations: pressing use on a station block pulls the camera to a third-person work view (or seats the worker on the block, camera free, body locked), plays a work animation timed to each swing, and converts materials one cycle at a time for small, steady XP. The first station, the Sawmill, converts a wood family's logs into that family's planks for split Woodcutting and Crafting XP per cycle. The station engine itself ships in a new standalone companion mod, RPG Stations (additional-mods/rpg-stations; own docs at its CLAUDE.md), which runs a full rich station loop (conditional loot rolls, command rewards) entirely on its own; the MMO jar adds a soft bridge that turns a work session into skill XP, aggregated luck, and mastery bonuses. Station content (the Sawmill block, loot tables, and the MMO bridge JSON) ships in the standalone content pack skill-stations-pack, which depends on BOTH mods - stations stay dormant without RPG Stations installed, and grant no skill XP without the MMO jar also installed. See CONTENT_PACKS.md's Station authoring section for authoring a new one.
• Adds station luck rewards: each work cycle can roll a bonus copy of its output on a per-skill luck chance (the same luck math gathering and mob kills already use), plus an optional ladder of native loot-table rolls at rising luck floors (50%, 100%, 150%, and beyond) for a rarer bonus drop the higher a player's combined luck climbs.
• Adds tool-power XP scaling to stations: working with a better tool for the station's gather type (a sharper hatchet, for example) earns more XP per cycle, on a curve the station's own content defines; a station that authors no scaling keeps the flat rate.
• Adds an optional face-the-station camera lock and a configurable per-swing cadence that re-fires the work animation as a one-shot alongside its own sound/particle beat (an axe whoosh and wood chips, on the Sawmill), so the swing motion lines up 1:1 with the cue, on top of its per-cycle presentation.
• Adds a general-purpose flair-unlock system for stations: any reward path that already runs a console command (quest rewards, achievements, mastery, mob-drop commands, command rewards) can unlock a named cosmetic flair, a per-station sound/particle overlay, for a player, persisted per player; admins can also grant, revoke, or list a player's unlocked flairs directly with /mmostation flair grant|revoke|list.
• Adds an optional no-material practice mode for a station: when a station opts in, working it with no materials on hand grants a small, extra-delayed trickle of XP (no items, no luck, no quest or achievement progress) instead of ending the session; off by default.
• Adds a center-screen session-summary panel for stations: a unified ledger lists every item consumed and produced (icon and name, luck bonuses flagged) alongside XP earned per skill, each row carrying the skill's own icon and a named breakdown of what produced it (base rate, tool bonus, and any class, world, gear, boost, or rested modifier that applied), when a work session ends; configurable to fall back to the classic corner notification instead.
• Adds a session-completion flourish to stations: finishing a work session with at least one completed cycle plays a distinct sound and particle beat on the player, grander than a single cycle's cue and smaller than a rare-find jackpot; a silent stop with no completed cycles stays quiet.
• Adds optional held-tool durability drain to stations: a station's content can wear down the tool in your hands per swing and/or per completed cycle (off by default); a tool that breaks mid-session ends the work loop.
• Adds a distinct sound and particle flourish per rare-find loot tier at a station, so a luckier roll feels luckier; the Sawmill's higher tiers play a grander flourish than its lower ones.
• Tunes the Sawmill's work cycle to land exactly on the fifth swing beat instead of mid-swing, for a cleaner-feeling work rhythm.
• Adds Smithing as a content-pack custom skill (not a built-in): the MMO Skill Stations Pack ships it as a Server/MMOSkillTree/CustomSkills/*.json asset, feature-gated on the RPG Stations integration, and it earns XP from a station's work cycles and completed enhancement rituals - dormant unless RPG Stations plus the pack are installed. Any Smithing XP a player earned earlier in this cycle is preserved across the change. The same pack ships a second custom skill, Cooking, bridged onto RPG Stations' own jar-shipped fish-preparation station. See skill-stations-pack's own docs for the station content that trains each one.
• Adds content-pack custom skills: a pack can add a whole new skill to the skill tree as a Server/MMOSkillTree/CustomSkills/.json asset (a Pattern A structured type, PascalCase keys), with the same defaults < pack < owner precedence as every other pack asset and its own additive .lang layer for the skill's name and description. See CONTENT_PACKS.md's Custom skill authoring section.
• Fixes an enhanced item's tooltip showing a raw server.items.*.description localization key as its first line when the base item had no description of its own (a descriptionless vanilla weapon run through the Anvil or /mmoitemenhance); the enhancement header and stat lines render with no phantom key line. An enhanced item otherwise keeps nesting its own native per-locale description like any other item, except when that description carries rich-text markup: the tooltip surface that renders an enhanced item's description cannot parse markup, so in that one case the tooltip shows only the Enhancement stat lines instead of literal text.
• Adds /mmoitemenhance refresh (admin): re-derives the held stack's tooltip from its existing rolled stats with no re-roll and no stat change, the sanctioned fix for a stack whose displayed tooltip has gone stale.
• Fixes a skill fed by a service bridge or by commands (one with no XP-trigger map, such as Smithing) being hidden from the skill pages, the leaderboard, and the admin boost target list, and its earned XP being left out of a player's total XP, summed total level, and "reach level N in any skill" progress.
• Adds coalescing XP notifications while working a station: during a work session, a skill's rapid XP toasts collapse into one updating entry per skill (carrying that skill's icon and the award amount in the icon's count badge) instead of a stack of separate banners, riding the same client path native item pickups stack on. Outside a station session, XP notifications behave exactly as before, and level-up banners are unchanged.
• Adds an enhancement summary to the anvil: a completed Enhance ritual's session summary now lists each stat the stamp rolled, with the same colored label and value the item's own tooltip shows, plus a durability line - so the summary and the tooltip can never disagree about what the enhancement did.
• Adds an authorable header balance strip to both storefronts and bounty boards: a Currencies list on a Server/ZiggfreedCommon/Shops/.json / Server/ZiggfreedCommon/Boards/.json asset names which currency balances show in that page's header, rendered as a chip row (icon plus amount) through the shared cost-chip vocabulary rather than a fixed single icon-and-label pair. A storefront that omits the field shows bounty_token, and a bounty board that omits it shows that board's own reward currency, so every existing pack keeps its current header with no edit. The hub's bounty preview panel renders the same row, capped at two chips with a +N overflow. Both lists are cross-checked against the currency registry by /mmoshop validate and /mmobounty validate.
• Adds authorable shop category ordering: a storefront's catalog categories previously sorted alphabetically, which put rare ahead of uncommon with no way to correct it (an entry's own order only ever sorted within one category). A CategoryOrder list on a Server/ZiggfreedCommon/Shops/.json storefront fixes the sequence (a server owner writes the same leaf by id in mods/ziggfreedcommon/shops.json); a category left off the list follows the named ones alphabetically, so an unset order is exactly the previous behavior.
• Adds one-shot station find XP: a station loot roll can grant a fixed XP bonus on a lucky find (RPG Stations' Roll.Grants.Contributions), awarded at full value regardless of held-tool tier and never reduced on idle practice cycles, and counted into the session summary's XP totals.
• Adds asset-driven NPC placement: where an NPC stands, which worlds it stands in, whether it appears at all, and what pressing F on it does are ONE pack-authorable asset (Server/ZiggfreedCommon/NpcPlacements/.json, Pattern A, every leaf wired for native Parent), resolved by one engine that ships in ZiggfreedCommon. It replaces seven parallel mechanisms in the MMO jar (the hub config, the hub placement store, the quest-giver asset/definition/config, the giver spawn service and role generator, and the structure- and zone-discovery spawn systems) and the role-name special case that made the hub privileged. Five INDEPENDENT anchor groups (world spawn, fixed coords, a worldgen structure marker, a discovered zone, a registered custom provider) produce the union of their positions rather than a placement-mode enum; Limits and Lifecycle (keep-alive, respawn, fortify) are opt-in knobs beside them. The Adventurer's Guide and every quest giver are now ordinary placements. See CONTENT_PACKS.md's NPC placement authoring section.
• Adds NPC placement into instance worlds, which the old exact-name world lists could not reach at all (an instance world is named instance--). A placement targets its worlds with a Where selector: a named selector from the shared vocabulary, an inline name pattern, or the world's own stable GameplayConfig key. The jar ships the Adventurer's Guide standing in the vanilla Forgotten Temple as a short Parent child of the spawn placement (it overrides only Where and its identity bindings, and inherits the role, anchor, and lifecycle), plus the quest that sends you there.
• Adds NPC identity aliases: a placement may list further npc ids it ALSO answers to (mmoskilltree:npc_aliases, a Values array with one id per entry) beside its primary mmoskilltree:npc_id. Every quest bound to the primary id of one placement is offered, credited, and turned in at any placement listing that id as an alias, with no quest-file edit, now or in future; an objective aimed at a placement's own PRIMARY id stays scoped to that placement. A tracked quest bound to an aliased id marks every answering placement on the map, which is the intent - either one serves it.
• Adds the Once dialogue knob: keyless seen-ness on a Start entry or an option, "Once": true for once per character or "Once": {"Where": {"Match": [""]}} for once per world family (Where is the shared world-selector group, so a GameplayConfig key covers an instance family). A Match pattern speaks the same grammar every world-targeting field uses (Foo, Foo*, *Foo, *Foo*), so the pattern itself is the exact-versus-fuzzy knob; state keys by the literal name or the pattern's literal CORE, which is the stable handle across an instance world being torn down and rebuilt under a fresh uuid name (*KweebecNightmare* keys under KweebecNightmare, and the narrower *KweebecNightmare_Barn* scopes per arena). An entry's Once is spent by COMPLETING the beat (choosing any option on the routed node, the implicit farewell row included), so leaving mid-beat shows it again; an option's is keyed by its LabelKey (or an explicit OnceId), never its index, so reordering a node's options can neither resurrect nor spend one.
• Adds declared dialogue Memories: named state declared once at the dialogue top level with its own scope and lifetime (Where for per-world-family, taking the same world-selector group as Once; ResetWithQuest to be forgotten when that quest resets; Shared for cross-dialogue visibility), then used by BARE NAME through the Remember/Forget actions and Remembered/NotRemembered conditions. The map merges per key under Parent. Validation catches what raw flags could not: an undeclared name, declarations of a shared memory that disagree, a memory never written or never read, a blank scope, and a scope pattern that would match every world.
• Adds one shared condition-factor vocabulary across NPC placements, dialogue options, and RPG Stations: the same {Factor, Param, Min, Max} leaf everywhere (a dialogue writes it as {"Type": "Factor", ...}), with a portable hytale:* standard library of straight native reads - hytale:stat (any registered stat channel, which is how MMO skill levels are reached), hytale:tool_power / tool_durability_percent / tool_quality / tool_item_level, hytale:held_tag, and hytale:held_item. The same ids resolve context-appropriately: a work station answers the tool ids from the session's tool, a dialogue or placement gate from what the player is holding. A pack can now gate a dialogue option on a stat or a held item with zero Java.
• Adds authoring diagnostics for placements that used to fail silently: a validator finding for a binding key with no yourmod: namespace (previously dropped with zero signal even at runtime), for a binding namespace nothing registered, for a ui_target prefix nothing can open, for an alias no content anywhere names, and for two placements claiming the same primary npc id. Every open registry (binding channels, condition factors, custom anchor providers) now records the mod that claimed each id plus a per-id failure count and last message, surfaced by the new /mmonpc channels and fed to the in-game Asset Editor's pick lists.
• Adds pack-authorable quest-giver and hub NPCs the native way: a placement names its character with Identity.Role, and that role is an ordinary Hytale role file a pack ships at Server/NPC/Roles/** with full engine validation. The jar ships two parameterized Abstract templates holding the whole stationary-greeter body, Template_Mmo_Hub and Template_Mmo_QuestGiver, each declaring exactly the five parameters a variant can really override (Appearance, NameTranslationKey, Weapons, OffHand, DefaultOffHandSlot), so a pack's own giver is a three-line Variant with a Modify block. Beside them the jar ships three ready-to-place roles: Mmo_Hub and Mmo_QuestGiver as thin variants, and Mmo_Mastery_Trainer as a full body, because the engine reads a role's press-F Hint and worn Armor literally and the trainer's prompt says train rather than talk. MmoRoleTemplateParameterTest fails the build on a Compute binding at either literal-only field and on a Modify key the referenced template does not declare, across the jar's roles and the content packs' alike, since both mistakes show up in game only as an NPC who is never anywhere.
• Adds the shared quest and achievement content schema: both lift onto ziggfreed-common's engines and both author as native assets under Server/ZiggfreedCommon/Quests///.json and Server/ZiggfreedCommon/Achievements///.json. One shape covers both (Text / Listing / Requires / Rewards plus Flow/Repeat/Npc/Objectives on a quest and Scoring/Criteria/MetaChildren on an achievement; who may SEE content before taking it - Hidden, RequirePrerequisites - and its Icon live on the shared Listing group for both), with native Parent inheritance instead of a hand-rolled template DSL, a recursive folder scan, id = filename (a leading-underscore folder contributes its name as an id prefix, stacking in path order), and unique basenames store-wide. QuestGenerators stamp a family of near-identical quests from one file. The legacy Server/MMOSkillTree/Quests/ and Server/MMOSkillTree/Achievements/ stores stay registered as the compat surface for existing packs and owner files, and precedence is unchanged bottom to top: shared schema, then the legacy pack layer, then mods/mmoskilltree/quests/ and achievements/.
• Adds the Repeat group, the whole vocabulary for a quest that comes back around. Authoring the group AT ALL is what makes a quest repeatable, so "Repeat": {} is a quest with no clock of its own, governed entirely by whatever offers it - which is exactly what a rotating bounty-board contract is. Inside it, four INDEPENDENT constraints compose and all must pass: Cooldown, a rolling wait written through one structured time group whose parts are summed ({"Hours": 24}, {"Days": 7}); Reset, a calendar allowance ({"Period": "Daily"} or "Weekly", plus At, Weekday and Times, anchored to the server clock in UTC); MaxCompletions, a lifetime cap; and ResetsOnComplete, the quest ids wiped when this one finishes. CooldownFrom picks which instant the rolling wait counts from: Claim (the reward being taken) by default, so a quest parked completed-but-unclaimed at an NPC is not quietly burning its cooldown, or Complete (the last step ticking over) for a quest belonging to a rotating offer, so collecting late does not burn a slot in the next period. An admin quest reset wipes the completion record, because a reset means starting over; abandon and self-heal preserve it, so a lifetime cap stays enforceable in play.
• Adds CompletionDialogue, a top-level leaf on a shared-schema quest naming the conversation that follows it settling at a character. It plays only where there is somebody to play it, so a hand-in at an NPC runs the beat and a quest finished from a log or an objective book skips it - and that decision belongs to the shared engine rather than to whichever screen the player was looking at, so every consumer surface behaves the same way. Authoring an empty string drops a conversation inherited from a Parent.
• Adds Meta.mmoskilltree, the structured consumer-knob block on shared-schema content: a quest reads NpcOnly (cannot be taken from the quest log) and Feature; an achievement reads ServerFirst, Feat, Feature, Class, LegacySince, Announce/Announce.Body, and the two per-skill stencils under PerSkill. Every leaf is nullable and inherits through Parent. The engines' own schema carries no consumer vocabulary: Meta is one generic namespaced extension map any mod can claim its own key in.
• Adds Listing.Chains, multi-membership content laddering: an item may sit in several chains at once ([{"Id": "sands_hunter", "Tier": 2}, ...], tier per membership, ids are free strings), and the ladder UI treats the first membership as primary. Quests carry the same leaf as questline grouping vocabulary.
• Adds Text.TextArgs, auto-calculated display arguments: a title or flavor key can name argument slots filled by engine sentinels rather than baked numbers, with @amount (the objective or criterion's own required amount) pre-seeded. An author writes the sentinel once and the number follows a retune.
• Adds one gate schema across quests AND achievements: an achievement's Requires block (feature factors, class, and the factors axis) is evaluated exactly the way a quest's is, so a pack that gates its taming or mastery content on a feature gets that gate honored with no content edits. Gates also gained a factors axis on requirements/prerequisites blocks ({"factor", "param", "min", "max"}, Factors on codec surfaces); skills and minCombatLevel are unchanged sugar for it, and a bounds-less condition is a genuine presence check that fails closed on an unresolvable factor.
• Adds honored Scoring.CountsTowardTotal: an achievement may state outright whether it contributes to a player's point total, instead of that being derivable only from its feat-of-strength flag. A feat of strength still never counts toward the total, so a true on a feat does not override it.
• Adds STAT_THRESHOLD, a generic objective and criterion kind: {"type": "STAT_THRESHOLD", "target": "", "amount": N} completes when that channel reaches the amount, so any registered stat channel (including another mod's) becomes a step with no new objective type. REACH_LEVEL keeps working unchanged and is the friendly form for skill levels - it desugars onto the same kind at runtime, so the two render identically and a player can never tell which one an author picked.
• Adds two public level channels, MMO_TotalLevel and MMO_HighestSkillLevel, beside the existing MMO_Level_ and MMO_CombatLevel. All four are readable from any factor formula - a loot chance, a content gate, mob scaling, a work station - the same way, and all four are written on every path that can move a level.
• Adds a process-wide factor CONTRIBUTION door in ziggfreed-common, so one mod can publish what it knows as ordinary factor readings and another mod's authored content can cite them with no dependency in either direction. A contributor claims an id at setup (owner-tagged, identity-idempotent, one boot line per id's first claim) and every factor site falls through to the contributions on a local miss, so a consumer's own registration always wins. FactorContext gains a nullable target leaf beside subject - the entity a moment is ABOUT, as opposed to the one acting - and MobKillEventSystem threads the victim into it, which is what lets a mob-kill formula weigh the mob's own properties and the killer's luck in one expression. An id nobody answers degrades by the standing rule: a gate stays shut and a formula term adds zero, so one authored file is correct on every server.
• Adds five citable readings from the standalone MMO Mob Scaling companion, usable in any Chance, Conditions or gate formula the moment a server has that mod installed: mmomobscaling:mob_rarity_tier (the mob's place on the rarity ladder, 0 for plain and one step per authored tier, derived from the tiers themselves), mmomobscaling:mob_rarity (Param = a rarity id), mmomobscaling:mob_affix (Param = an affix id), mmomobscaling:mob_difficulty, and mmomobscaling:region_power. So a bonus drop can be richer off an elite, a quest gate can want a boss, and neither mod knows about the other. That mod's own rarity and variant death loot also re-bases onto the shared Loot block this release, so a tier's loot, a bonus drop, a station find and a quest reward are one vocabulary.
• Adds the open reward vocabulary: Kind (or type, on the older surfaces) names a kind and every other field is that kind's parameter, so alongside the mod's own Mmo_Xp/Mmo_Boost_Token/Mmo_Currency/Mmo_Ability_Mod a piece of content can pay out any framework kind - Item ({"Kind": "Item", "Params": {"Item": "Ingredient_Bar_Iron", "Count": "5"}}), Lootable (roll a shared loot table), Stamped_Item (grant gear with rolled stat bonuses already stamped on the stack), Effect (apply a native entity effect), Droplist (roll a native ItemDropList and spill it at the player's feet, or at an authored position), and Command (run an authored command line). A kind id is native-asset style, PascalCase with underscores, unprefixed for the framework's own and mod-prefixed for a consumer's; ids match case-insensitively and every historical lower-case spelling (xp, item, boost_token) translates through one canonicalization, so the older surfaces keep working verbatim. It works on every reward surface at once - quests, achievements, point milestones, shop offers, bounty crates, dialogue reward actions, command rewards - and a kind a companion mod registers is authorable with zero changes here. An item reward renders with the real item icon, its name and count, and the item's own native tooltip.
• Adds reward kinds AS CONTENT: Server/ZiggfreedCommon/RewardKinds/.json declares a Params schema (Required / Default per parameter) plus one Command template with {player} / {uuid} / {} substitution, run as the server console through the shared command primitive, and the file name is the kind id. All four of this mod's kinds ship that way in the jar (Mmo_Xp, Mmo_Currency, Mmo_Boost_Token, Mmo_Ability_Mod, each mapping to an admin command), so a server owner with an admin command they want paid out as a reward needs no plugin to say so. Kind assets layer defaults < pack < owner and inherit through Parent (Params merges per parameter, Command replaces). Collision policy is JSON WINS, loudly: a kind asset may shadow even a Java-registered id, with one boot WARN naming the shadowing file and a matching validator finding, because a command-backed kind gives up that kind's engine services (the ask-first inventory fit check, the replayable offline retry) and the warning says so.
• Adds one inventory-room probe paired with its own granter, so a payout that would not fit is refused before anything is charged instead of overflowing or vanishing. The quest, shop and achievement claim paths share it, and a full backpack with a free hotbar slot now correctly grants a single-stack reward that used to be refused.
• Adds BonusDrops, ONE pack-authorable surface for what a moment hands over on top of whatever the game already gives for it - the lucky find in a broken block and the bonus a killed mob is worth, which were the same question in two vocabularies. One row per file at Server/MMOSkillTree/BonusDrops/.json: a nested When group (Kind, BreakBlock or KillMob, plus a Match name pattern), an optional Chance, a Loot reference, an optional Notify, and Enabled. Chance is a percent factor formula, so {"Factor": "hytale:stat", "Param": "MMO_Luck", "Weight": 0.2} is literally how a lucky player is luckier, and Loot is the same vocabulary a station's rare find and a quest reward speak - shared Lootables by id, Rolls written inline, or both, with a roll's Grants paying out items, native drop lists, commands or any registered reward kind. Native drop lists spill where the moment happened, at the block or at the corpse, beside whatever fell there anyway, with no vanilla table touched. The two moments keep their own per-trigger behaviour and their own documented default odds: a BreakBlock row with no Chance is as likely as the player's own summed luck, a KillMob row with no Chance always fires and leaves the odds to its rolls, and only a player's kill counts.
• Adds one matching rule across both moments: When.Match speaks the shared name grammar (Ore_Coal exactly, Ore_* starting with, *_Cracked ending with, *Trork* anywhere in the name, * everything, case ignored) and the row pinning down the most characters wins - exact first, then the longest literal core, then the catch-all. Luck's old first-match-over-a-hash-map pick was nondeterministic for two overlapping patterns; it is deterministic now, and a family row plus a one-block row compose without either file knowing about the other. An ENABLED row with no Loot is a first-class deliberate hole: the more specific pattern wins, so it stops a broader row covering that one name, which is different from "Enabled": false taking the row out entirely and letting the broader row take over again.
• Adds mods/mmoskilltree/bonus-drops.json, the one owner layer over both moments: it overrides a row BY ID through the same codec with the shipped row as its parent, so the body merges per leaf. {"Enabled": false} switches a row off without erasing its pattern, a Loot block alone re-tunes what it hands over, and "__DISABLED__" in place of the whole body is the one-word spelling. Precedence is the ordinary defaults < pack < owner.
• Adds a shared Notify group on both moments ({Enabled, Color, Icon, TitleKey, SubtitleKey}, off unless a row asks, fired once after the grants and only when something actually landed), which retires luck's hardcoded English "Lucky!" literals: the shipped luck rows author the note explicitly and its wording comes from translation keys in all nine languages.
• Adds the fourteen built-in luck rows as readable jar assets (ten ore families, plus four cracked-ore variants shipped as worked deliberate holes), so a pack can Parent-retune a built-in row and a server owner can read the file that decides what a lucky break gives. config/defaults/LuckDefaults.java is deleted; no Java default luck table survives.
• Adds BonusDropsValidator in place of LuckValidator, auditing both moments under one domain: an owner body that cannot be read, a row naming no moment, a pattern with a wildcard in the middle, a row-level chance that can never rise off zero, an unknown factor id, a row that hands nothing over (reported as information, since it may well be a deliberate hole), and two rows pinning down the same literal core in one moment.
• Adds native Parent-inherited dialogues as fully structured assets: a dialogue is decoded once through its own codec, so an unknown condition or action type fails the read loudly at load instead of misbehaving at the first conversation. Authored dialogue JSON is unchanged.
• Adds NPC identity as first-class content: Identity.NpcId and Identity.Aliases on a placement, plus overlay assets at Server/ZiggfreedCommon/NpcIdentities/.json for aliasing, the same character in two roles, and renames. Identity resolves down a documented ladder - the placement's own declaration, then a role overlay (walking the native variant chain), then a group overlay, then the role id - and a placement that declares no NpcId IS its role, so identity costs an author nothing and two placements of one role are two standings of one character (a quest bound to it is offered, credited and handed in at either). Authoring an NpcId opts out and makes a standing a character of its own, which is how a step is scoped to one of them: the jar's temple guide is the worked example, with its own id plus the spawn guide's as an alias. One authority answers "does this NPC answer to id X" for quest offers, turn-ins, dialogue conditions, the quest list, talk objectives, and map waypoints, so those can never disagree.
• Adds an explicit talk-credit pipeline: MarkTalked in a conversation and ZigTalkCredit on an NPC with no conversation both feed one credit sink with a shared de-duplication window, so one conversation credits once no matter how many beats mention it. A talk at an aliased placement credits both the primary id and each alias without double-counting the statistic, and a native NpcTalkedEvent fires once per credited conversation for third parties.
• Adds an honest split between "this NPC is your destination" and "this NPC can take your hand-in" for new-shape quests: a TALK_TO_NPC step still lights the character up as where to go, but their conversation no longer offers a hand-in for a quest with nothing to hand over. Old-format quests keep the previous conflated behavior exactly, so nothing already authored changes.
• Adds achievement categories and point milestones as SHARED-schema assets (Server/ZiggfreedCommon/AchievementCategories//.json for order, icon, title key and subcategories; Server/ZiggfreedCommon/AchievementMilestones//.json for the points ladder), so a pack can declare its own category and a server owner still outranks it. A category's filename IS the category word content writes; a milestone's Threshold is its identity, so a file re-authoring 3000 replaces that rung outright whatever it is called. A milestone pays out through the shared Rewards vocabulary (Auto lands the instant the total is crossed, Claim waits on the achievements page), so a milestone can hand over a real item or roll a loot table like anything else. The five built-in point milestones ship as assets rather than Java, and mods/mmoskilltree/achievements/point-milestones.json stays the sanctioned owner layer.
• Adds ONE Where spelling for every world-targeting field: an NPC placement, a world rule, a dialogue World condition and a mob-scaling world rule all author the same nested group (Match / GameplayConfig / ExcludeMatch), scored on one specificity ladder, so an author learns one grammar and a mod never invents a second. A bare word under Match is an EXACT world name, and ExcludeMatch takes the same grammar as a FILTER over the positive axes rather than a complement of them. /mmoconfig validate reports a Where matching none of the loaded worlds and one with no positive axis at all, from one shared check every surface calls.
• Adds ONE shared loot asset type. A Server/ZiggfreedCommon/Lootables/.json gained the competing-outcome half it was missing, a nullable Pool group of {Rolls, Entries[{Weight, Conditions, Grants}]}, so a score-tiered or luck-tiered reward pool is an ordinary shared table anything can point at. Pool.Rolls is the standard {Base, Factors, Clamp} factor formula, so "one more pick per 1200 points" is a term weighted 1/1200 over any registered reading rather than a bespoke field, and a premium entry's requirement is an ordinary Conditions gate; picks draw with replacement, and an entry can hand over items (with an optional CountMax quantity range), native drop lists, commands, or any reward kind.
• Adds Lootable.ContributesTo, cross-mod loot enrichment: a file naming another table's id has its rolls and pool entries folded INTO that table on top of what is already there, so a pack enriches another mod's loot without touching its files and removing that pack removes exactly what it added. Ordinary defaults < pack < owner id layering resolves first and contributions after, so an owner override of a table keeps every contribution made to it, and how often the merged pool is drawn stays the target's decision.
• Adds dialogue authoring in the shared store: a conversation is authored at Server/ZiggfreedCommon/Dialogues//.json with an Owner leaf, the same way quests and achievements are, and this mod folds its own owner plus every unowned file. Server/MMOSkillTree/Dialogues/ stays registered as the compat surface for packs written earlier, precedence runs shared store then legacy pack layer then mods/mmoskilltree/dialogues.json, and an id authored in both stores is named in one boot warning with both file locations rather than silently shadowed.
• Adds a Mastery Trainer NPC at the Forgotten Temple, standing beside the guide: taller, darker, staff in hand, opening the Mastery screen on use, and gated on the mastery feature so it never appears on a server that has mastery switched off. With the Mastery pack installed, the trainer talks instead: a short conversation offering their quest list, the mastery menu, or a farewell (the pack overrides the trainer's placement by id and binds its four mastery quests to the trainer as their giver, accepted and handed in at that quest list).
• The quest log IS the shared Objective Book. /mmoquests, the hub tile and every menu's quests tab open ziggfreed-common's ObjectiveBookPage, which gained the whole quest-log feature set for it: category tabs, a search field, a tag dropdown and status filters (all read from the shared Listing schema any mod's quests author), per-row track/untrack and abandon on carried quests, and a "Completed" filter view for finished ones. The page wears this mod's theme through the book's theme seam, and the mod ships no quest page of its own; the old page's Pages/QuestPage.ui family and its ui.quests.* strings are gone.
• Completing a quest now arms whatever it unlocked IMMEDIATELY: an auto-accept quest gated on the one that just finished (the tutorial chain) lands on the tracker the moment its prerequisite settles, not on the next login. An auto-accepted quest also records its giver as where it was taken, so a hand-in of the "return to whoever gave you this" form resolves at that character.
• /mmoquestadmin reset now puts the player back at day one for real: the same maintenance a fresh login runs re-arms every auto-accept quest the wipe re-opened, and the tracked-quest HUD repaints instead of keeping the wiped quests on screen.
• A locked quest row now says WHAT is missing: a quest gated on another quest reads "Complete quest: " on the giver's list and in the book, instead of a generic "Not available yet"; a full quest log gets its own line too.
• Fixes the NPC quest list's header showing a raw id (such as Mmo_Hub) instead of the character's name: the page now reads the name off the live character it was opened on, and the static role-name resolve seeds the engine's execution scope first, the way the engine's own off-entity reads do, so a Variant role built on an Abstract template resolves everywhere else too.
• Fixes ability cards and tooltips showing literal // markup (the onboarding ability step, skill-tree claim cards, bind-page tooltips): every composed fragment now carries its emphasis as structured message styling, which survives nesting, and the number/school/source tints moved from lang markup to the one Java vocabulary that builds those fragments.
• Fixed: slows, roots and hastes reach player targets too. An EntityEffect speed change used to author only the NPC leaf (ApplicationEffects.HorizontalSpeedMultiplier), which a player's client never applies - so Crippling Slam's slow, Arcane Lash's root and Concussive Dive's stun held mobs but let a player target keep running, and Tempest Vault's self-haste never sped its caster up at all. Every shipped speed-changing effect now also authors the Update 6 player leaf (MovementEffects.SpeedMultiplier) at the same value, so mobs and players feel the same slow. A new ability audit WARN (EFFECT_SPEED_NPC_ONLY) catches the gap going forward: any MMO-family EntityEffect authoring the NPC leaf away from 1.0 with no player leaf beside it is reported as a slow that does nothing to players.
• Adds a mastery audit domain under the startup audit and /mmoconfig validate: every ability id, skill id, modifier paramKey, prerequisite and cross-node gate reference a track makes is checked (a dangling one was silently inert before), and the content fold's own findings are replayed into the same report.
• The mastery node effect line covers the whole canonical paramKey vocabulary in all nine languages (five new nouns); no canonical key falls to the raw-text fallback any more.

• The mastery paramKey check accepts the clamp-store extension seam, the same rule the ability audit applies: a mastery modifier's ParamKey passes when it is canonical OR a Server/MMOSkillTree/ModifierClamps/.json DECLARES it (a clamp file authoring IsParamKey: false, like the hit-side HitDamage.json bucket, bounds its fold without declaring an authorable key), and the WARN on a genuinely unknown key now names the clamp file as the way to declare a new one.
• Adds a kill-rarity attribution seam for companion mods (MMOSkillTreeAPI.registerKillRarityProvider, additive on the FQN-frozen api/ surface beside registerMobKillXpMultiplier): ONE registered provider names a killed mob's rarity, the shared kill producer consults it once per credited player kill (through the kill-qualifier bridge the mod registers into the shared progression runtime), and the answer rides the kill moment as its qualifier. That one answer feeds BOTH halves of a kill's rarity: quest and achievement criteria authoring the rarity word as their Qualifier match the kill - the tier achievements (First_Legend_Kill, Legendary_Slayer, Rare_Hunter, Elite_Slayer) progress on scaled kills - and the mob-drop command placeholders resolve a kill row's {tier} to it. An unqualified criterion still counts every kill exactly once (there is one dispatch per kill, never a second qualified re-fire). MMO Mob Scaling 1.1.0 registers its rolled rarity ladder (Rare / Epic / Legendary / Boss); without a provider, or for an unscaled mob, kills fire unqualified and {tier} stays empty.

Technical: the ability-modifier vocabulary and grammar (the pre-release break wave)

• The ability-modifier grammar is PascalCase ({"Shape","ParamKey","Value","TargetAbility","School","CombatTarget","Condition"}); the arithmetic shapes are FLAT / PERCENT / SET (replace, last-write-wins), and any modifier can carry an optional Condition (SelfHp/TargetHp {Min,Max} + HostileOnly/OnCritOnly/Filter). Field names match case-insensitively like every hand-parsed surface, and the two shape words the 1.5.x public mastery format shipped, OVERRIDE and ADD_PARAM, still parse as SET - that is the whole legacy surface: the Key field alias, the flat camelCase HP-bound spellings and the CONDITIONAL wrapper shape are not read. Every writer and every shipped entry emits ParamKey.
• Adds ability/ParamKeys, the one canonical paramKey vocabulary; the content validator checks every authored modifier key and every body-declared MmoNum key against it plus the pack extension seam (a pack declares a new key by shipping its ModifierClamps asset), WARNs an unclamped authored key, and ERRORs an unclassified body declaration. The mastery validator's canonical-key check is a view of the same authority.
• Adds seven ModifierClamps assets (onHitHealPercent, lifesteal, lootMultiplier, comboFinisherBonus, schoolResist, armMultiplier, armFlatBonus), per-leaf clamp merging across layers, per-key clamping inside the fold, and a new owner file mods/mmoskilltree/ability-clamps.json, loaded beside the other owner configs and re-read (with a re-fold) by /mmoconfig reload.
• The four non-ability paramKeys are clamped at their own aggregation seams, since their values never pass through the per-cast fold the other clamps guard: the mastery swing aggregation clamps its summed lifesteal / comboFinisherBonus totals, the per-skill lootMultiplier sum clamps before it is cached, the mastery school-resist mirror clamps each channel's summed FRACTION (so SchoolResist.json's Max 0.9 is the same 90-point ceiling the damage fold enforces), and the tree+mastery stat aggregator clamps the mastery subtotal of any channel whose paramKey is non-ability. A stack of mastery nodes past a clamp now caps exactly the way stacked gear or cast modifiers do.
• A ModifierClamps/*.json file says whether its key IS a modifier paramKey with a nullable IsParamKey leaf (absent means true, so every existing clamp keeps declaring its key). HitDamage.json authors false: it clamps the hit-side percent fold bucket, which no modifier may target directly, so shipping its bounds no longer smuggles hitDamage into the authored-key vocabulary - the ability and mastery validators consult the declared set and flag a modifier authoring it, while the bounds still apply. A pack declaring a genuinely new key still just ships a clamp file for it.
• The defense-reduction cap and the school-resist ceiling are clamp assets an owner can retune. A reserved ModifierClamps/DefenseReduction.json (Max 0.9, IsParamKey: false like HitDamage.json) bounds the victim's total percent damage reduction from defense, resolved at the damage pipeline's one cap site through the new fail-closed ParamClampTable.maxOr (armor penetration still applies before the cap, and with no asset loaded the 0.9 convention stands in - a safety cap exists even on a broken pack layer); the school-resist reconciler's whole-percent bucket ceiling and the damage-school audit's overcap WARN both derive from SchoolResist.json's Max through the same read, so retuning either bound in ability-clamps.json moves every reader of it together.
• The mastery damage mirror is bounded by the same clamp the cast fold uses: each per-channel total the mirror writes onto the MMO_Damage* / MMO_Bonus* channels is clamped to Damage.json's bounds in its authored unit (a percent total as the summed fraction, a flat total as a value), so a repeatable-purchase damage stack caps on the channel route exactly as it does per cast.
• MmoArmNextHit's arm flavor is the explicit Momentum knob (a 0.0 FlatBonus is no longer load-bearing) and its keys split to armMultiplier/armFlatBonus so an arm scale and a damage value never share a fold bucket. The ability audit WARNs a Momentum: true node that also authors FlatBonus/OnHit/CastRay/CastDamage - the momentum branch never reads those leaves.
• Adds the MMO_AbilityDamageRadius gear channel (damageRadius) beside MMO_AbilityRadius (radius).
• Schema nestings: Casting.SelfHp, PassiveTrigger.SelfHp/TargetHp/Bonus{FromAbility,Multiplier,ScalesParam}, Presentation.Animation{Name,Item,Slot} and Presentation.Particles{Id,MaxMs} (both with a bare-string shorthand); MmoProjectile.Raycast, MmoDeployable.FaceCaster, MmoHookshotPull.GapCloseSeconds; MmoDot/MmoHeal's effect key unified as EffectAsset.
• Passivity derives from the PassiveTrigger group's presence; the legacy Identity.Passive leaf still decodes and gets a validator WARN.
• The three snake_case interaction-Type aliases are deleted; the scan-only cause tag is MmoCauseScanRef.
• The nine slam-family native damage leaves are MmoDamage nodes, so gear and mastery damage bonuses reach them.
• Adds two grantable ability-mod exemplars: Duelist's Instinct (TRIGGER, grants the Punishing Dodge passive) and Tremor Aftershock (ADD_STEP, a second shockwave on Ground Slam).
• The GateOnly-without-paired-cast WARN (CAST_GATE_ONLY_UNPAIRED) is wired into the ability audit.
• The body-fidelity oracle gains a post-wave baseline: a verbatim capture of every shipped ability body (post-wave-fidelity.json) the equivalence check compares against going forward, with the frozen pre-wave digest kept byte-identical as the record of the pre-wave shape.

Technical: the progression move is write-first, claim-last

• ProgressStateMigration writes every legacy leaf BEFORE spending its one-time claim, each leaf family under its own guard: a throw mid-move now costs a retry on the player's next ready instead of a permanently-burned claim over half-moved data (every write is a SET, so the clean leaves re-move harmlessly). The achievement-progress pass re-keys positional records onto criterion ids through the folded catalogue (a pluggable resolver, so the move stays pure logic a test can drive), and ZigProgressComponent.setAchievementUnlockedAt keeps an existing stamp (putIfAbsent, the legacy contract), so a replay can never rewrite the instant something was first earned.

Technical: `/zigprogress`'s two groups conjugate the same way

• The shared admin family's achievement group gains claim (--achievement=, the peer of quest claim), its force-it verb is give (the same word, the same meaning, as quest give), reset takes --achievement= on both groups (the one-item wipe subsumes the old revoke, meta-cascade included), and achievement status takes the same one-id filter quest status has. Node depth follows nesting: reload, the one family-level verb, sits under the family and every group verb under its group. The MMO's own aliases keep their shipped names and gates. A contract posted on several boards now credits every one of them on completion - the primary board rides the full COMPLETE_BOUNTY fan-out and each further board fires as a targeted alias, so an achievement naming a second board counts while the untargeted "complete N bounties" tallies count one completion.

Technical: the reward reading converges on ziggfreed-common

• A reward reads the same everywhere, through the library's ONE chip ladder. RewardPreviewBuilder no longer derives a RewardSpec's name and icon per kind: both come from ziggfreed-common's RewardChips (a reward's own words and picture first - an authored Icon wins on every rung, the contributed one included - then the Server/ZiggfreedCommon/RewardKinds/Mmo_*.json kind files, then the item form), and the new pages/render/MmoChipReading is contributed process-wide at setup - the same rung zc-commerce's wallet reading uses - carrying only the lines a file cannot say: the boost multiplier-and-duration sentence, an ability-mod title read out of AbilityModCatalog for a modifier that never named itself, a parsed /give or /mmoboost give command line (an unparseable one still reads as the neutral generic label, never the raw command), and the XP line for a custom skill whose pack shipped no reward.xp. key. The roll-at-grant-time kinds (lootable / drop list / effect) need no arm at all: ziggfreed-common ships their presentation-only kind files itself, so reward.line.lootable / reward.line.droplist / reward.line.effect retire from all nine of this mod's locale files in favour of the library's own ziggfreedcommon.loot.* copies (same wording, same icons). The quest book takes the same shared ladder with no per-consumer reward reading (MmoObjectiveBookDeps registers no chip source), so this mod's panels and toasts, the quest book, the NPC quest page and the board cannot disagree about what a reward is called - and a reward of a kind nothing on the server can read rows as the localized "Special Reward" label, never the raw kind id.
• XP wording settles on the per-skill key family, with digit grouping. The reward.xp. values gain {0, number} in all nine locales, so every surface shows the grouped "+2,000 Mining XP", and Mmo_Xp.json authors the new Args: ["Amount"] so the amount binds as a typed number wherever the family renders. The Java-composed reward.line.xp / reward.line.xp_all survive only as the custom-skill fallback line.
• Mmo_Boost_Token.json authors no NameKey: a boost token's one label is the computed sentence ("Swords XP x2 for 30m"), so a book row, a board row and a panel row all read that same sentence. Two reward-row wordings move deliberately and stay moved: a currency row reads through the shared wallet reading as "+50 Bounty Tokens" (the wallet's own icon and name, the plus kept, and the amount bound as a typed number so each player's own client decides the digit grouping), and an item row reads through the shared item form as "x3 Iron Bar" - both in place of this mod's private compositions.
• Four unread lang keys retire from all nine locales: reward.line.currency, reward.line.item, reward.line.amount (an authored reward title is used verbatim, never amount-wrapped) and reward.boost_token.
• Reward-toast row capping routes through the library's RewardToastLines (ToastablePage.showRewardToast and the quest completion toast), so the "+N more" overflow row is computed in one place instead of two private copies.
• A display number binds as a typed param, never as server-formatted text - build-enforced. The cost chips, balance strip and cost summary route bare figures through the shared {0, number} reading (Msg.num, and CostRenderer.currencyAmountMsg through zc-commerce's shared price composition), and the ability bind page's cooldown meta becomes the localized ability.bind_page.cooldown_meta key ("{0, number}s cd") in all nine locales, so digit grouping and decimals are each client's own decision. RepoHygieneTest gains the matching rule: a Msg.raw(...)/Message.raw(...) wrapping a NumberFormatter.*/String.format result fails the build, with // NUMBER-OK: (reason mandatory) as the one escape hatch for a number that is genuinely not localized display text.

Technical: the quest and achievement notices speak one lang-key vocabulary

• The keys the seven shipped FeedbackMoments files author unify under notify.*: achievement.unlocked / achievement.points_awarded / achievement.server_first_lost become notify.achievement_unlocked / notify.achievement_points_awarded / notify.achievement_server_first_lost, and the bounty-worded notify.bounty_ready_to_claim in the quest-domain Quest_Parked file becomes notify.contract_ready_to_claim, renamed across all 9 locales. Filenames are untouched.

Technical: six retired SkillComponent leaves stop writing

• Currencies, LifetimeCurrencySpent, ShopPurchaseTotals, ShopPurchasesToday, ShopPurchaseEpochDay and SlotRerolls keep their decoders (the one-time CommerceStateMigration reads them at ready, before the first save can drop the keys) and their encoders return null - the same one-way self-retiring idiom the removed built-in skills use - so a stale ghost copy of the wallet no longer rides every save beside the live economy's own record. A rollback to an older jar still recovers the values from an un-migrated save.

Technical: English is authored in the `.lang`, not generated from Java

• The Java-baked English-defaults paradigm is deleted. i18n/lang/EnglishDefaults.java (3,546 lines), the LanguageDefaults interface, i18n/lang/EnglishLangWriter.java, the generateEnglishLang Gradle task and EnglishLangExportTest are all gone, and the i18n/lang/ subpackage with them. src/main/resources/Server/Languages/en-US/mmoskilltree.lang is the authored English now: it is edited directly, nothing regenerates it, and it is byte-identical to what the retired task last produced, so no key moved and no value changed. Adding a key is one line in that file plus the eight sibling locales.
• i18n/LangResources replaces the in-code map by reading the shipped file back. It parses Server/Languages//*.lang off the classpath, so LocalizationConfig's layer-3 fallback and hasKey now answer from the exact file I18nModule loads as a pack. The fallback can no longer disagree with what a client resolves - the whole class of "server-resolvable but not client-resolvable" drift that hasClientKey exists to guard. It also absorbs StatTooltipLangGenerator's private parser and EnglishLangWriter's escapeValue, so the mod has ONE .lang parser and ONE escaping authority instead of three.
• A net-new lang file is namespaced mmoskilltree..lang, matching what ziggfreed-common (ziggfreedcommon.fmt.lang, ziggfreedcommon.commerce.lang) and RPG Stations already ship. I18nModule derives a key's namespace from the file's basename, so entries in a domain file drop the segment the filename carries and every call site keeps its bare key: hud.layout.title in mmoskilltree.hud.lang is written layout.title. LangResources.MMO_LANG_FILES declares the set and the new LangResourcesTest fails the build if it drifts from what is on disk or if a locale is missing a declared file. The existing mmoskilltree.lang is deliberately not split; the convention applies going forward.
• Two dynamic key families become authored data. skill. and reward.xp. were synthesized in Java from the live SkillRegistry, which only ever reached the built-ins at build time anyway; both families are plain entries in the .lang now. Adding a built-in skill means authoring both keys in all nine locales (the recipes skill says so at the step).
• Fixed: passive ability cards emitted a lang key that shipped in no locale. ability.bind_page.passive_tag was authored as an empty string, and the retired writer SKIPPED empty values because Hytale's LangFileParser aborts a whole file on one - so the key never reached any .lang while AbilityBindPage still emitted Msg.tr for it on every passive card, leaving the client an id nothing could resolve. The tag is authored as real text ("PASSIVE") in all nine locales, matching its three sibling branches. Removing the generator is what surfaced it: MsgTrKeyCoverageTest now checks literal Msg.tr keys against the shipped file rather than the Java map, so this shape cannot recur.
• Tests, hooks and docs follow the source. Twelve test files read the authored file instead of the Java map; SkillNameMsgClientResolvabilityTest now pins both halves of the custom-skill bug (the fallback carries no runtime-only id AND the client probe refuses it) where it could previously only pin the gate. check-localization.ps1 drops its generator-parity branch, no-balance-tests.ps1 drops a dead exemption and carves Server/Languages out of its resource heuristic, and the localization / recipes skills, the localization-translator agent and both CLAUDE.md routers describe the authored-file workflow.

Technical: the content-key namespace is no longer registered

• The MMO registers nothing for authored-key resolution any more. i18n/MmoContentI18n and its ContentKeys.install call in setup() are deleted along with ziggfreed-common's whole registration surface: the shared ContentKeys now attributes a bare authored key against the server's live loaded lang catalogue (the exact id first, then the key under any loaded .lang namespace with the alphabetically first id winning a tie, else the key exactly as written). Shipping mmoskilltree.lang is the whole declaration, for this jar and for every content pack that ships into the same filename. No authored content key changed anywhere: a TitleKey, NameKey, FlavorKey or FeedbackMoment Key resolves to the same registered id as before.

Technical: the tracked-quest HUD becomes the library's, event-driven

• The in-world tracked-quest HUD is no longer this jar's. ziggfreed-common ships it (objectives/hud/TrackedQuestHud, its .ui and the three native objective textures beside it, attached to every player at ready), and it repaints on the quest engine's SIX native events - a pin or unpin (the library's new QuestTrackedEvent), an accept, an objective moving, a completion, a claim, an abandon - with a burst folded into one paint per tick and NO tick anywhere. ui/hud/QuestTrackerHud, event/QuestHudTickingSystem, pages/render/TrackedQuestPanelRenderer, Common/UI/Custom/Hud/MmoSkillTreeQuestTracker.ui and its three textures, and Common/UI/Custom/Pages/TrackedQuestRow.ui are DELETED. Titles and objective lines on the panel come from the shared text sources this mod already folds its content into, so the tracker cannot drift from the quest log; the panel looks exactly as it did.
• What this mod keeps is one class, pages/quest/MmoQuestHudDeps. It answers the library's three seams and nothing else: WHERE the owner put the panel and WHETHER the owner has it on, both read live off HudLayoutConfig under the unchanged mmoskilltree:quest_tracker entry (so /mmoconfig questhud and the admin page keep working verbatim, now persisting and broadcasting through the library, and no saved layout moves); and whether THIS player wants it - the /mmohud quest preference plus the world's own abilities-and-HUD rule. The theme seam is filled with NOTHING: the native look is preserved bit for bit, and a theme, when there is one, goes through UiRetint on the tracker's own selectors, never the page-frame painter.
• Two moments no quest event announces are pushed by this mod. /mmohud show|hide quest|all asks the library for one repaint after it writes the preference, so the panel hides or shows at once instead of on a tick; the world-change hook does the same after a player lands, so a world with HUDs off hides it and the return trip shows it again. MMOSkillTreeAPI.isHudVisible is unchanged.
• The quest-giver map waypoints rebuild off the same six events plus PlayerReady (QuestWaypointService.install / refresh(UUID)), which is what let the HUD tick delete clean: what a player is being pointed at only changes when their quests do.
• The tracked-quests SIDE PANEL on the quest log and the Skill Overview is painted by the library's TrackedQuestPanelRenderer (rows Pages/ZigTrackedQuestRow.ui), handed a read-only subject through the new QuestService.readerFor; the two host pages keep only their #TrackedQuestsList container, #TrackedQuestsEmpty label and header. ui.viewxp.tracked_quests_empty retires from all nine languages (the empty note is the library's tracked.empty line now).

Technical: quest and achievement toasts become authored JSON

• Every quest and achievement lifecycle moment is authored JSON; no toast, jingle or banner for either is Java any more. ziggfreed-common gained an asset-driven feedback engine (Server/ZiggfreedCommon/FeedbackMoments/.json) that the two shared progression engines announce every lifecycle moment to, and this mod SHIPS a file for each of the seven moments, reproducing today's wording, icon and sound, each file's colour spoken as its whole-toast Tone: Quest_Completed.json (the gold "Quest complete" line plus its jingle), Quest_Parked.json (the gold "open the Quests page" notice plus its jingle, with two Variants: reason: no_space reads red "free up inventory space" and stays silent, turnIn: accept_site reads "claim your reward at the Bounty Board"), Quest_Objective_Progressed.json (the {step} ({current}/{required}) tick, the green "Objective complete" finish, EveryPercent: 25 on the toast for the quarter marks), Quest_Claimed.json and Achievement_Claimed.json (the legendary-chest chime, When: {collected: true} only, so a quest or achievement that settled on the spot keeps its one completion or unlock jingle), Achievement_Unlocked.json (the golden title, the points line, the achievement's own icon, the unlock jingle, AND the server-wide announcement as a Broadcast group whose two lines read their keys through KeyArg from the announcing achievement's own Announce {TitleKey, BodyKey}, carried into the moment as announceTitleKey / announceBodyKey / announceSkill / announceAmount by AchievementDefinition.toRuntime through the runtime Achievement.momentArgs) and Achievement_Server_First_Lost.json (the quiet amber note). A server owner retunes any of it by overriding the file, with no jar involved, and can add a Broadcast banner or a console Command to any of them the same way.
• MmoQuestListeners and MmoAchievementListeners keep ONLY the gameplay side effects: the completion log line, resetsOnComplete and the completion fan-out (achievements, the completed-N credit, a contract's board tail) on the quest side; the log line and the PowerLevel cache drop on the achievement side. The objective-progress notification, its 25-percent-tick math, the parked wording, the announcement banner and every claim jingle are deleted from Java: RewardSoundUtil loses SOUND_QUEST_READY, SOUND_QUEST_CLAIM and SOUND_ACHIEVEMENT_CLAIM (the points-milestone claim keeps its chime as SOUND_MILESTONE_CLAIM, since a milestone is derived state the engine fires no moment for), and QuestService.claimQuest / AchievementService.claimAchievementRewards no longer play a sound of their own. The parked wording branches on arguments the shared quest engine now carries (reason, turnIn) rather than on this mod's own bounty and inventory reads, so it needs no Java; the per-player verbosity gate stays MmoQuestSubject's FeedbackAudience answer, now graded per moment (MmoQuestSubject.wantsToast: all sees every tick, milestones the authored marks and the finish, objectives the finish, quests no step toast, none nothing) off the values the engine hands it. One deliberate change: a player on none no longer sees the red inventory-full notice either, which used to bypass the setting; the reward still waits, and the Quests page still shows it. The notify.bounty_inventory_full key, reachable by no branch, is removed from all nine locales.
• Meta.mmoskilltree.Announce keeps only TitleKey and BodyKey; the written-out Title / Body leaves and the legacy owner-file announcementCommand are retired. Both lines are keys (a key no lang file ships is shown as written, so a one-server broadcast can put the sentence itself in TitleKey), and how the banner is drawn is authored once for every achievement in Achievement_Unlocked.json. An owner-file achievement still carrying announcementCommand gets one boot WARN naming the replacement (a Command group on that file, or a Variants entry scoped by When: {achievement: }), and the leaf is otherwise ignored.
• The runtime Achievement gains the icon this mod's own resolver produces, stamped on when the catalogue folds (and folded again on every republish, so a chain or category layer that lands later still reaches it), so the shared unlock toast paints exactly the picture the achievements screen does without re-walking the authored-then-chain-then-skill ladder per unlock.
• A shared moment fires for shared content, so the toast reaches quests and achievements this mod does not own. The old Java handlers drew nothing for a quest or an achievement missing from this mod's own catalogue (a board contract published straight to the shared runtime, or another mod's content on the same server); the moment is announced by the engine for everything in that runtime, so such a completion or unlock now wears these files' wording and jingle. A line whose named value the moment did not carry is skipped rather than drawn with a gap, so content with no title stays silent. A server running two mods that both want their own words gives one of them its own moment ids rather than sharing these.
• A player's own questNotificationLevel still silences the completion toast. An authored file cannot read a per-player setting, so the moment engine asks the SUBJECT instead: MmoQuestSubject answers ziggfreed-common's FeedbackAudience off the level the player chose, and a player on none keeps the jingle and loses the toast exactly as before. Only the personal toast is gated that way; a banner, a sound and a console command belong to the moment rather than to one screen.

Technical: the five progression seam fills delete

• The MMO no longer answers a single shared progression seam. MmoQuestGates, MmoAchievementGates, MmoQuestTextSource, MmoAchievementTextSource and MmoNpcOffers are DELETED outright, and none of them is replaced by a smaller version of itself: what each one knew now rides the runtime Quest / Achievement the fold already builds - the authored Requires block, the words, the giver id and listing order, the one-winner flag, and availability as a live PREDICATE - so ziggfreed-common's ONE gate, ONE text source and ONE offer provider answer for this mod's older authoring format exactly as they do for the shared schema. ConsumerOwnsNothingTest fails the build if a class here implements one of those seams again.
• A quest's whole requirement set is now one block. The older format spelled a permission node, a total-level floor and per-skill floors as leaves of their own beside Requires; they are folded into it as ordinary factor bounds at the one point a definition becomes a runtime quest, so a permission, a level and a prerequisite are all answered by the same evaluator. An achievement's classRequired folds in the same way, as an mmoskilltree:class bound at AchievementDefinition's constructor, which is why no Java compares a class anywhere any more.
• One GateEvaluator per server, and it is the library's. This mod built a second one over its own factor registry and its own completion probe, so a shop row rendered from saved records and the same requirement on a quest were two decisions that agreed only by inspection. Now MmoGates keeps the LANGUAGE half (the lock reasons a player reads) and reads the shared evaluator, and this mod registers ONE factor vocabulary (GateFactors, saved-record-first) plus one factor context onto the shared runtime. MmoQuestGates.preSatisfiedAmount deletes with it: the engine's own standing-value reading now reaches the same saved skills.
• The quest-log cap and content availability became data. The engine reads the live maxActiveQuests number and a live availability predicate, so the "log full" and "unavailable" refusals are the engine's own - one refusal instead of two that could disagree. The engine counts the same set the quest screen's own "X/Y" header counts: a board contract is carried beside the quest log rather than inside it, so it spends no slot and is never refused for a full one, exactly as before. A bounty's park-at-its-board rule deletes here too: the engine already parks a contract at the board it was taken from.
• A requirement with nothing to read now refuses, where three older leaves used to wave it through. Permission, MinLevel and SkillRequirements were each checked by a helper that skipped the check when it had no player or no saved skills in hand; folded into the requirement block they are ordinary factor bounds, and a bound that reads nothing shuts. It bites only where a requirement is evaluated with no records at all behind the player, and no shipped quest authors a Permission.
• An achievement's claim rewards are now checked for somewhere to land before the claim spends, the same check quests already had. This mod's own screen already asked first and still answers "your inventory is full"; a claim reaching the engine from anywhere else now parks instead of paying out into nowhere.
• Server-first races keep working exactly as before (one winner, a loser keeps their criteria met and is told once), with the arbitration in the library, only the persisted claim table left here, and the notice itself authored as the Achievement_Server_First_Lost moment above.
• What a server owner may notice. A quest kept out of open listings until its requirements are met is still offered at the character who hands it out, and a giver's list is sorted by the SortOrder its files author, with quests sharing one SortOrder now falling into id order rather than catalogue order. A quest that sets RequirePrerequisites WITHOUT Hidden is a second change on that screen: the giver now lists it only once the requirements pass, where it used to be listed locked from the start. No shipped quest is affected (every one that sets RequirePrerequisites also sets Hidden), and /mmoconfig validate names the combination as VISIBILITY_GIVER_GATED so a pack author is told rather than left to find out. Because the whole requirement block is one question now, a quest gated behind a level floor, a skill floor or a permission is held back at its giver in the same way, rather than being listed there locked until the player is up to it; again no shipped quest pairs one of those with RequirePrerequisites. Going the other way, a quest a player is already CARRYING stays listed at its giver even if the feature behind it is switched off mid-run, which is what lets them finish and hand in something they were given before the switch. On the shared screens (the objective book and the NPC quest list), a quest refused by a requirement reads as the generic locked line rather than a prerequisite-specific one, because the refusal now carries the evaluator's own token naming the factor, the permission or the quest that shut it; this mod's own screens read that token and are strictly more specific than before. A step still reads with this mod's own auto-generated sentence unless its file authors a TextKey that a shipped translation actually answers.

Technical: six more consumer fills move down into the library (the zc-lift wave, items 1-6)

• The dialogue factor vocabulary is no longer installed by this mod. MmoDialogueEngine stops building a FactorRegistry and claiming the shared dialogue engine's one factor slot; ziggfreed-common's own wiring root seeds the hytale: standard library there at library setup (which also fixes conversations gated on hytale: factors failing closed on servers running the library without this mod). This mod's three mmoskilltree: factor ids already ride the process-wide contributions table (util/MmoFactorContributions), so nothing this mod's dialogues gate on changes.
• util/MmoFactors is deleted. Its about(store, subject[, target]) builder was the zc FactorContext verbatim with validity guards and no MMO type anywhere; the factory now lives on FactorContext itself and the two callers (event/MmoMomentReactions, util/LuckUtil) call it there.
• player/CommerceSubject is deleted. The live-player Subject factory is the library's own Subject.of(player) / Subject.of(playerRef, player); the thirteen files that built commerce subjects through the local class now call the library, byte-identically.
• player/PlayerRefSubjectHandle moves to ziggfreed-common (subject/PlayerRefSubjectHandle, unchanged contract: resolve-on-demand, Player/PlayerRef facets, the all-zero anonymous id). Its three callers re-import; the MMO's SubjectHandle interface stays, implemented by the two engine handles that carry real MMO state. util/PermissionUtil.resolvePlayer folds onto the library's new PlayerAccess.player(PlayerRef) primitive at the same time (one behavioral hardening: a stale-but-non-null reference now resolves to null instead of throwing from the engine's ref validation).
• The station flair-unlock provider is deleted (integration/stations/StationFlairUnlockProvider and its bridge registration). Reading ziggfreed-common's ZigFlairComponent is RpgStations' own built-in provider now, so flair unlocks resolve on servers running RpgStations without this mod; the write side (/mmostation flair) stays here.
• pages/quest/MmoNpcQuestDeps stops filling the NPC quest page's completion hand-off. The library's NpcQuestPageDeps default already routes a settled quest through the dialogue engine's installed quest runtime - the same MmoDialogueQuests instance this mod installs - so the fill was a second spelling of the same answer. The theme painter and the completion toast stay, being real presentation policy.

Technical: the lock-reason vocabulary is the library's, and this mod ships only names

• This mod has no gate language of its own any more. The per-mod lock-reason model and its renderer (content/gate/GateReason, pages/render/GateReasonRenderer, the ui.gate.locked_* sentence family) are deleted; every locked surface renders ziggfreed-common's LockReasons lines over the evaluator's structured GateRefusal records, through the thin MmoGates facade (refusals / lockLines). One requirement is one sentence on every screen on the server, whichever mod's content authored it, and a refusal now quotes where the player stands - "Requires Mining level 40 (currently 12)" - off the very reading the evaluation was decided on, on every gated surface at once (the bounty board's contracts included, which never had the readout).
• What this mod ships instead is NAMES: four Server/ZiggfreedCommon/Factors/ overlays in the jar. The hytale:stat overlay bridges every per-skill level channel onto the skill. name keys the jar already ships (one line: strip MMO_Level_, lower-case, pattern-substitute) and folds each resolved name into the one factor.skill_level "{0} level" phrase via WrapKey, so a skill gate reads "Requires Mining level 40" for every built-in skill and for any custom skill whose pack ships its own name key - no per-skill phrase keys. The three aggregate channels (MMO_CombatLevel, MMO_TotalLevel, MMO_HighestSkillLevel) carry bespoke complete-name keys the wrapper never touches. mmoskilltree:mastery_node reaches each node's own title off the compound : Param (StripThrough ":" cuts to the node id, the pattern lands on the mastery..title keys the mastery pack already ships, and a node without one falls back to the generic name); mmoskilltree:class names a class through its own class..name key, and mmoskilltree:feature carries a generic name a pack can override per id with an overlay of its own. Seven new factor.* name keys, nine locales; the fourteen retired ui.gate.locked_* keys leave all nine (only ui.gate.locked survives, still painted as the bare LOCKED status word).
• The mastery page paints client-resolved lock lines. MasteryService.PurchaseCheck hands back Message lines instead of server-resolved English strings (the bespoke mastery refusals - prerequisite node, choice-group sibling, cost shortfalls - nest their names as client-resolved arguments too), and MasteryPage paints each as its own line, so the lock panel reads in the viewer's language instead of the server's. String-typed result toasts still flatten their one line server-side, as before.
• The cheap path is still the right tool for a boolean check. MmoGates.passes / firstFailure short-circuit, which is what a per-row loop wants (the mastery track rail, ClassService.recheckAdvancements, QuestService.evaluatePrerequisites); MasteryService.canPurchase keeps its listEveryReason knob, with both arms reading one collect-all walk so even the one-line failure toast can carry the current-value readout.
• An AnyOf refusal stays ONE entry - its routes are alternatives, not separate chores - and carries what each route asks for, so the shared mapping reads it back as "Unlocked by: A or B" (the routes joined by a translatable or; one route reads as its own line, and a multi-ask route stays one comma-joined bundle). A passing Not reads as the negated sentence naming the met requirement, and a permission refusal reads its own sentence instead of squeezing into the numeric-bound frame - all of it the library's rendering, so every mod's gates read the same way.

Technical: the `content/reward` package shrinks to this mod's own vocabulary

• Four classes delete. MmoRewardKinds (a seam over the ONE shared kind table that registered nothing: a payout site now names RewardKinds.shared() directly, and isPayable(kind) moved onto RewardSpecs where the kind vocabulary already lives), RewardFit (a wrapper over the framework's own LootRewardKinds.canAddAll, now asked directly by the quest and achievement surfaces that want to warn before an irreversible claim), RewardGrantService (the grant PASS is the library's RewardGrants.grantAll, called directly by the three payout paths outside the two progression engines) and RewardParser (lifted to ziggfreed-common as a generic reader this mod builds with its own dialect). RewardExecutor keeps only the connect-time spool drain; its retryCommandOf / processQuestPlaceholders pair had no production caller left, because the framework's Command handler is what resolves a retry line. The package drops from 1,571 lines to 1,122.
• The two rules every payout site was applying in front of a grant became the library's. A reward authored queueIfOffline: false is dropped when nobody is there to receive it, and a reward that names no source is stamped with what actually paid it out, both once in front of every kind. The behaviour is unchanged; what changed is that a companion mod's payout gets the same two rules for free instead of re-deriving them.
• Reward refusals still happen at LOAD. A command with no command, a currency reward naming no wallet or a non-positive amount, and an ability_mod with no mod id are still skipped with a boot WARN naming the file, and /mmoconfig validate still reports them. The rules are this mod's (RewardSpecs.refusalReason) and are handed to the shared reader, so a pack author finds out at boot rather than a player finishing a quest and receiving nothing.
• One factor registry in this mod, not two. A luck formula, a bonus-drop chance and the bonus-drop validator resolved factors through a second, live-only registry while every Requires block read the saved-record-first one, so an authored hytale:stat had two possible readings depending on where it was written. All three now read GateFactors.registry(), which is a strict superset; nothing reads differently today because every formula site runs with a live entity in hand. Which entity a formula is asked ABOUT is the other half of the question, and it is the shared FactorContext.about(...).
• A payout outside the progression engines is built through the shared subject/PlayerRefSubjectHandle, since who a payout is for is an identity question rather than a reward one.

Technical: the producer claim mechanism deletes; the placed-block guard becomes the library's

• Block break, mob kill, craft and pickup progress is produced by ziggfreed-common alone. The claim-and-stand-down mechanism is gone: the library's four generic producers always run, this mod claims nothing, and MMO_PRODUCED_KINDS deletes. Those producers feed the same shared QuestEngine and AchievementEngine this mod's own services read, so one break advances one objective once. What this mod DOES with those four moments (XP, statistics, bonus drops) is a reaction to the library's dispatch, event/MmoMomentReactions, described in its own section below; the harvest ALIAS (a pickup also credited as break-blocks progress under the picked-up ITEM id) stays this mod's own to send, and a kill landed by a turret or summon reaches the library's own kill producer through its KillAttribution seam.
• The place-then-break and place-then-harvest guard moved into ziggfreed-common, as the shared world/placed/PlacedBlockLedger. skill/PlacedBlockTracker deletes. The library's own place-block system is the single writer, and the library's producers plus this mod's XP path all read the SAME ledger, so quest progress and XP can never disagree about whether the breaker put that block there themselves - which the old arrangement could not have survived, since the library's producers knew nothing about this mod's tracker. The four knobs stay exactly where server owners already have them, in skill-config.json (trackPlacedBlocks, strictPlacedBlockCheck, placedBlockExpireMinutes, placedItemExpireMinutes); this mod installs them as a live policy on the ledger, so a reload still moves them. A creative-mode placement is still not recorded.
• Placements do not survive the upgrade. The ledger keeps its own file at mods/ziggfreedcommon/placed-blocks.json and the old mods/mmoskilltree/placed-blocks.json is not read: it is renamed to .legacy at boot with one notice naming the replacement, never deleted. Blocks placed before the upgrade are forgotten once, so for one expiry window a player could break something they had placed earlier and be credited for it; placing anything after the upgrade is remembered as usual. The pre-1.0.2 hash-keyed placed-block key migration retires with the file it migrated.
• The boot log's [progression] producers line changes shape: the per-kind "N of M library defaults standing down" count is gone, replaced by a single always-on line naming the four built-in kinds and pointing at ProgressDispatch.fire as the open extension point for a net-new moment.
• Everything a produced moment used to carry still travels with it, which is what makes the swap invisible in play. The library's shared dispatch resolves the ZONE for itself now (through ziggfreed-common's own ZoneLocator, which util/ZoneUtil was a line-for-line copy of; that copy is DELETED and ProgressEvents reads the library's), so a zone-scoped kill or block break still completes; the achievement POINTS-MILESTONE toast rides the registered call scope rather than only this mod's own facade, so a milestone crossed by a produced break or kill still announces itself (a milestone is derived state the engine fires no event for, and a missed one would have stayed silent forever, since the next call's before-snapshot already holds the threshold); it wraps each engine call in this mod's registered call scope, so a finished quest still fires its message, its jingle and its objective line; and it asks this mod first whether the player's quest and achievement systems are switched on, so enableQuests / enableAchievements and their bypass permissions still hold for those four kinds - contributed as ONE ProgressionSystemGate (quest/MmoSystemToggles) rather than answered by refusing to build a subject, since the same subject carries the player's wallet and board state and a null would close the shop along with the quest log. The harvest alias above stays this mod's own to send, because no library producer covers it; a kill landed by a turret or summon is the library's producer's to fire, once this mod's KillAttribution contribution names the owner (the attacker itself has no PlayerRef).
• BreakBlockEventSystem declares itself BEFORE the library's block-break producer in the engine's own system-dependency graph. A break this mod cancels for an unmet tool or item-level requirement is one the producer must see cancelled, and without the declared order the engine was free to sort them either way.

Technical: the MMO reacts to a produced moment; it does not re-detect it

• The five block / kill / craft / pickup / place event systems collapse into ONE reaction listener. event/MobKillEventSystem, event/CraftRecipeEventSystem, event/PickupItemEventSystem and event/PlaceBlockEventSystem are DELETED, and event/BreakBlockEventSystem keeps only what CANCELS the engine event (the tool-type and item-level requirement gates and their notifications, still declared BEFORE the library's break producer, with the unordered fallback and its warn untouched). Everything they awarded - gathering / building / crafting / kill XP, the blocks_broken / items_pickedup / items_crafted / mobs_killed statistics, the LuckUtil bonus drops, the mob-drop commands, PassiveAbilityTriggers.onKill, the fish branch, the crafting eat-veto mark and the harvest alias - now lives in event/MmoMomentReactions, this mod's one MomentListener, registered into the shared progression runtime from MmoQuestEngine.register() and fanned by ziggfreed-common's ProgressDispatch.fire FIRST, before the subject test and both system gates: a player who has never opened a quest log still mines ore for XP, and enableQuests=false never switches off mining XP. The method bodies moved rather than being rewritten; every gate inside them (the entity blacklist, PermissionUtil.canGainSkillXpByName, the MMOSkillTreeAPI kill-XP multiplier, LethalHitAttribution, the deployable skill list, XP per craft ACTION never per unit) is intact.
• XP, statistics and bonus drops hang off the library's produced moments, through its typed payloads. Each reaction reads the record ziggfreed-common's producer ships with the moment (BlockBreakPayload for the block position a lucky find drops at, PickupPayload for the picked-up stack, CraftPayload for the RECIPE id the craft XP table is keyed by beside the moment's output-item target, MobKillPayload for the victim and the death, PlaceBlockPayload) and does nothing without it, so a library kind fired by hand advances objectives and earns nothing here. The placed-block anti-exploit guard is now read by NOBODY in this mod: a placed-then-broken block or placed-then-picked-up item produces no moment, so no XP, no statistic, no drop and no progress, and the two ledger reads this mod used to make are gone with the systems. ProgressEvents.fireStatisticsOnly is deleted (the reactions feed StatisticsService.handleEvent directly); fireObjectivesOnly stays for the movement accumulators.
• Turret and summon kills credit the owner through the library's attribution seam. DeployableAttribution.KILL_ATTRIBUTION (the existing resolveOwner, in ziggfreed-common's KillAttribution shape) is registered beside the listener, so the library's own kill producer fires a deployable's or summon's kill for its owner and the kill reaction routes the XP to the spawning ability's skills off the raw attacker the payload's death names. The MMO-side "fire the objective half myself for the redirected kill" branch is gone with MobKillEventSystem.
• The harvest alias never re-enters the fan-out. A pickup also credits BREAK_BLOCK under the picked-up ITEM id (no library producer fires that); the pickup reaction sends it through the library's new engines-only ProgressDispatch.fire(..., DispatchOptions.OBJECTIVES_ONLY) overload, which reaches no listener, so one harvest cannot pay block XP twice or count a blocks_broken it never earned.
• Two behaviour notes an owner may notice: a CANCELLED placement earns no building XP any more (the deleted PlaceBlockEventSystem never checked the cancel; the library's PLACE_BLOCK producer does), and a CREATIVE-mode placement produces no PLACE_BLOCK moment at all (the producer mirrors the placement recorder's three filters), so it earns no building XP and advances no place-block objective.
• The deprecated-engine-API convergence reaches event/: every plain-deprecated Damage#getCause() read in CombatDamageEventSystem and CombatXpEventSystem becomes DamageUtil.causeOf(damage), CombatDamageEventSystem's private duplicate of AbilityDamageUtil.resolveCause is deleted in favour of the one implementation, every raw store.getComponent(ref, PlayerRef.getComponentType()) in the package becomes PlayerAccess.playerRef(store, ref), and EntityCombatTextSanitizeSystem no longer returns the deprecated AllLegacyLivingEntityTypesQuery: it queries the engine's own UIComponentList component - the one it sanitises - and declares itself Order.AFTER the engine's UIComponentSystems.Setup that puts it on every living entity's holder (with the same unordered-fallback-plus-warn shape as the break gate).
• Tests: MmoMomentReactionsTest (a hand-built moment, no ECS: an unknown kind and a library kind without its payload are left alone before any world handle is touched; the attribution answers nobody for a stranger) and MmoProgressionRegistrationTest.thisModReactsToTheLibrarysMomentsAndAttributesItsSpawnedKills. CraftRecipeEventSystemTest retires WITH its system; its guarantee (a batch craft counts every unit, clamped to at least one) now lives in ziggfreed-common's ZigCraftProducerTest.