Feedback & Colored Combat Text

Overview

Adds a single feedback layer so the big moments of play - a critical hit, a level-up, a bounty completion, a shop purchase - feel like more than a line of text. One service fans each moment out to up to five channels at once, in lockstep: floating combat text (colored where it fires), a 3D sound at the player, an optional camera shake, the corner notification feed, and an in-menu toast for actions taken from inside a UI page (for example accepting a quest from the Quests menu shows a toast over that page in addition to the shared sound cue). Everything is cosmetic, server-owner configurable, and can be turned off.

The two pieces are colored combat text (the red "CRIT!" and gold level-up popups, tuned in combat-text.json) and the broader feedback layer (the per-moment sound and camera, tuned in feedback.json). Each channel is independently guarded, so a misconfigured asset can never break combat.

Feedback moments (authored files)

New: the toast and the jingle a player gets for a progression moment are files, not code. One file per moment lives at Server/ZiggfreedCommon/FeedbackMoments/<moment id>.json, and the file name is the moment. Reword one, recolour it, give it a different sound, announce it to the whole server, or run a console command on it, all without a jar involved.

Eight moments fire today, and the mod ships a file for each of them. Seven are the quest and achievement notices players already know; the library underneath ships a plainer, neutral file for those same seven under the same names (so a bare server gets a notice and a jingle out of the box), and the MMO's files win because a pack that depends on the library loads after it. The eighth, Rare_Find, is the MMO's own, with no neutral default beneath it.

Rare_Find also shows the no-Java celebration rule: the cue id IS the moment id. Any loot roll or ladder floor in a Lootables file can carry a Cue, and a pack that authors a different cue value plus a moment file of that same name gives that roll a celebration of its own, with no code anywhere. A cue fires only when the grants beside it genuinely paid out, so it never celebrates over an empty hand.

Three of the shipped files, to show the shape:

{
  "Toast": {
    "Title": { "Key": "notify.quest_complete", "Args": ["title"] },
    "Tone": "Reward"
  },
  "Sound": { "Id": "SFX_Discovery_Z2_Short" }
}

{
  "Toast": {
    "Title": { "Key": "notify.quest_ready_to_claim", "Args": ["title"] },
    "Tone": "Reward"
  },
  "Sound": { "Id": "SFX_Discovery_Z1_Short" },
  "Variants": [
    {
      "When": { "reason": "no_space" },
      "Toast": {
        "Title": { "Key": "notify.quest_inventory_full", "Args": ["title"] },
        "Tone": "Error"
      },
      "Sound": {}
    },
    {
      "When": { "turnIn": "accept_site" },
      "Toast": {
        "Title": { "Key": "notify.contract_ready_to_claim", "Args": ["title"] },
        "Tone": "Reward"
      }
    }
  ]
}

{
  "Toast": {
    "Title":     { "Key": "notify.achievement_unlocked",        "Args": ["title"] },
    "Secondary": { "Key": "notify.achievement_points_awarded",  "Args": ["points"] },
    "Tone": "Reward"
  },
  "Broadcast": {
    "Title":     { "KeyArg": "announceTitleKey", "Args": ["announceSkill", "announceAmount"] },
    "Secondary": { "KeyArg": "announceBodyKey",  "Args": ["player", "title"] },
    "Major": true
  },
  "Sound": { "Id": "SFX_Capture_Crate_Capture_Succeed_Local" }
}

The unlock toast draws the achievement's own picture beside the words, so there is nothing to name per achievement. The banner is drawn only for an achievement whose own file authored an Announce block: that block carries just two keys, TitleKey and BodyKey, and the moment reads them through KeyArg, so the words are the achievement's own and one that authored none shows no banner at all. The server-first note is deliberately grey and silent: losing a race should never be louder than winning one.

The four groups

A moment file carries up to four independent groups. Author the ones you want and delete the rest; none of them needs any of the others.

A line of text is written the same way everywhere: Key, Args, and optionally Color; the toast as a whole carries a Tone.

• Key is a line from a language file, written without that file's own name prefix, exactly as you wrote it there. Point it at a key of your own to reword the moment entirely; a key no language file ships is shown as written, so a one-server line can be the sentence itself.
• KeyArg reads the key from one of the moment's values instead of naming it. That is how Achievement_Unlocked.json draws each announcing achievement's own words.
• Args names which of the moment's values fill that line's blanks, in order. A line naming a value the moment does not carry is skipped rather than printed half-empty, so an experiment can never leave a broken line on screen. player always answers with the player's name.
• Toast.Tone colours the whole notification, frame and words together, from the closed set Info / Success / Reward / Warning / Error, and picks the matching corner-feed style. Unauthored reads as Info, the neutral blue.
• Color on a single line, as hex, still overrides the tone's colour for that line alone.

Two more knobs branch on the moment itself:

• Variants is an ordered list of {When, <groups>} entries. The first entry whose When values all match the moment's own values (compared as text, so true and 25 may be written bare) overlays only the groups it restates; an empty group there means "nothing for this case". This is how one Quest_Parked.json says three things and how the two claimed files chime only for a collect ("When": {"collected": true}).
• Toast.EveryPercent shows an ordinary progress tick only when it crosses a multiple of that many percent, which is what keeps a long step from chattering. Without it there are no marks at all, and a player on the "milestones" setting sees only the finish.

What each moment carries, for Args, KeyArg and When:

A Command line may use {player} and any of those values in braces. Each shipped file's own comment repeats the list for its moment.

Overriding one

A moment is content, so it layers like any other: ship a file with the same name from your own pack, or drop one into a pack you already load, and yours wins. Deleting the toast group and keeping the sound is a valid file, and so is a file with nothing but a Broadcast.

A player's own quest-notification setting still has the last word on the personal toast, graded per moment: all sees every progress tick, milestones the authored marks and the finish, objectives the finish only, quests no step toasts, and none nothing at all (a player on none no longer sees the red inventory-full notice either; the reward still waits, and the Quests page still shows it). Only the personal toast is gated that way; a banner, a sound and a console command belong to the moment.

The server-wide banner an achievement shows is authored on the achievement itself, as an Announce block carrying TitleKey and BodyKey; how it is drawn is authored once for every achievement, in Achievement_Unlocked.json. The older written-out Title / Body leaves and the owner-file announcementCommand are retired: an achievement file still carrying announcementCommand gets one warning at start naming the replacement (a Command group on Achievement_Unlocked.json, or a Variants entry scoped by "When": {"achievement": "<id>"}) and the leaf is otherwise ignored.

Because the moment is announced by the engine for everything in the shared runtime, these files also dress a quest or achievement the MMO does not own (a board contract, or another mod's content on the same server). 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.

Colored Combat Text

Two combat moments float colored text above an entity. The text is fully localized into every supported language and ASCII-only, so it renders cleanly everywhere.

Only crits and level-ups float. Kill XP and per-action XP show in the corner notification feed instead of floating above mobs, the combo finisher keeps its bonus and notification but does not float, and lifesteal keeps its notification. One color renders per entity per instant, so a held crit color also tints that hit's damage number red - that is intended.

Critical-hit corner notifications ship off by default: the red floating "CRIT!" already marks every crit, so the separate corner toast is redundant. Anyone who wants both can re-enable the crit toggle in Settings and the choice sticks.

combat-text.json

Colored combat text lives in mods/mmoskilltree/combat-text.json. It is override-based - only the fields you change are written; everything else tracks the shipped defaults. A master enabled flag gates the whole feature, and crits and level-ups each have their own toggle.

{
  "schemaVersion": 1,
  "enabled": true,
  "crits": true,
  "levelUps": true,
  "critStyle": "MMO_CombatText_Red",
  "levelUpStyle": "MMO_CombatText_Gold"
}

The Feedback Layer

Behind the floating text, one service emits a moment and fans it out to a sound, an optional camera shake, the notification feed, and (in menus) a toast - all in lockstep, all from one call. Each moment maps to a row in feedback.json that carries the sound and camera ids for that event.

Moments that fire a sound or a shake

Combat moments (KILL_XP, CRIT, COMBO_FINISHER, LEVEL_UP) ship with their sound off by default because they fire often and a default chime would be spammy. Quest, bounty, and shop moments ship with a sensible stock sound. Set a sound id on any row to opt a moment in.

Camera shake

Every moment can also drive a brief camera shake, written straight to the player the same way the engine drives its own damage shake. Camera shake is off by default for every moment (no shake assets ship); the channel exists for servers that want it. Set a cameraEffect id and an intensity on a row to turn it on.

feedback.json

The sound and camera channels live in mods/mmoskilltree/feedback.json. Each moment is one row; an empty sound or cameraEffect string means that channel is off for that moment.

{
  "enabled": true,
  "events": {
    "QUEST_ACCEPT":    { "sound": "SFX_Drop_Items_Paper",       "cameraEffect": "", "cameraIntensity": 1.0 },
    "QUEST_ABANDON":   { "sound": "SFX_Generic_Crafting_Failed", "cameraEffect": "", "cameraIntensity": 1.0 },
    "BOUNTY_COMPLETE": { "sound": "SFX_Chest_Legendary_Open",    "cameraEffect": "", "cameraIntensity": 1.0 },
    "SHOP_PURCHASE":   { "sound": "SFX_Coins_Land",              "cameraEffect": "", "cameraIntensity": 1.0 },
    "CRIT":            { "sound": "",                            "cameraEffect": "", "cameraIntensity": 1.0 }
  }
}

The top-level enabled flag gates the entire sound and camera layer; turning it off leaves colored combat text and the notification feed untouched, since those are governed separately.

Turning It Off

There are independent switches at every level, so you can keep exactly what you want.

• All colored combat text - set enabled: false in combat-text.json.
• Just crits or just level-ups - flip crits or levelUps in combat-text.json.
• All sounds and camera shake - set enabled: false in feedback.json, or clear a single moment's sound / cameraEffect string.
• Corner notifications - players toggle individual notification categories (including the crit toast) in their in-game Settings, and the choice persists.

Quest accept and abandon cues are shared across every surface, so the bounty board, the NPC quest page, dialogue, and the quest log all play the identical cue. See Quests and Combo Finishers for the gameplay those moments come from.