Progression Recipes

Status: Reference / authoring aid. Companion to: STAT_PIPELINE.md, COMBAT_SYSTEM.md, Source/CRADL/Inventory/ItemRow.h

Scope

Tabular reference for stamping tiered weapons and armor with OSRS-shape progression curves. Each table pairs the OSRS reference values for a family (so the curve is anchored to a known good ramp) with the concrete FItemRow field values that reproduce a similar curve in the CRADL pipeline. Absolute numbers are not sacred — the shape (relative ramp between tiers, distribution across stat axes) is the contract.

This document is not a balance spec. Curve shape comes from OSRS; final tuning belongs to playtest.

Field Mapping (OSRS → CRADL)

Tick → SwingInterval cheat sheet: 3t = 1.8s · 4t = 2.4s · 5t = 3.0s · 6t = 3.6s · 7t = 4.2s.

EquipEffects vs row scalar. Per STAT_PIPELINE.md "Item Authoring Shape": static numerical bonuses use the row scalar fields. EquipEffects is reserved for conditional / multiplier / set-bonus shapes — see "Capstone & Conditional Recipes" at the bottom.

Melee Weapons

Per-family StyleDamageTypes mapping. Each melee family below carries a StyleDamageTypes mapping that controls which Combat.DamageType.* axis the active style consumes. The per-axis AttackBonus columns below are all reachable from gameplay — under Aggressive a scimitar swings Slash and rolls against AttackBonus[Slash]; under Controlled it swings Stab and rolls against AttackBonus[Stab]. The same author-once AttackBonus matrix supplies the right axis to whichever style the player picks. See COMBAT_SYSTEM.md "Combat Styles → Style → Swing Axis" for the resolver. Ranged/magic weapons don't author StyleDamageTypes — they swing their single WeaponDamageType regardless of style.

Scimitar family (4-tick, slash-biased one-hand)

OSRS scimitars are the canonical slash mainline: fast, slash-heavy, modest stab, slight crush penalty. Recipe mirrors OSRS values one-to-one — the ramp is already the curve we want.

DefaultStyle = Combat.Style.Aggressive for all (scimitars default-aggressive in OSRS). All other axes on AttackBonus / DefenseBonus left empty (treated as 0).

StyleDamageTypes: { Aggressive → Slash, Defensive → Slash, Controlled → Stab } — matches OSRS's Chop/Slash/Block→Slash and Lunge→Stab button mapping.

Longsword family (5-tick, balanced stab/slash one-hand)

Slower than scimitar, marginally higher slash, similar stab. Used as the "balanced" alternative.

WeaponDamageType = Combat.DamageType.Slash, DefaultStyle = Combat.Style.Controlled.

StyleDamageTypes: { Aggressive → Slash, Defensive → Slash, Controlled → Stab } — same shape as the scimitar family; longswords give up a tick of speed for slightly higher slash/stab numbers but keep the same per-style axis mapping.

Dagger family (4-tick, stab-focused, low Str)

Fast, stab-dominant, weak base — pure DPS-via-speed/style ramp. Capstone is the special-attack-driven tier in OSRS; we don't model the spec here, just the base values.

WeaponDamageType = Combat.DamageType.Stab, DefaultStyle = Combat.Style.Aggressive.

StyleDamageTypes: { Aggressive → Stab, Defensive → Stab, Controlled → Slash } — inverse of the scimitar shape (daggers are stab-default, slash on the off-style).

Mace family (4-tick, crush-biased one-hand)

Crush is the only tier-stamped weapon line that ramps the crush axis. Mace also carries a prayer bonus in OSRS — park that until prayer ships.

WeaponDamageType = Combat.DamageType.Crush, DefaultStyle = Combat.Style.Aggressive.

StyleDamageTypes: { Aggressive → Crush, Defensive → Crush, Controlled → Stab } — Spike (OSRS's Controlled mace style) routes to the secondary stab axis; the row's modest stab numbers above are what the swing rolls against under Controlled.

Two-hand greatsword / godsword (7-tick, capstone-tier slash/crush)

Two-hand slot. The godsword tier in OSRS unifies an extremely high slash and crush axis on the same weapon — pick the higher of the two as the player's effective attack roll via the combat-style choice.

WeaponDamageType = Combat.DamageType.Slash. Godsword tier ships with both Slash and Crush bonuses populated; the active swing axis is whatever the style → damage-type mapping resolves to at swing time.

StyleDamageTypes: - Greatsword tiers (Bronze → Dragon 2h): { Aggressive → Slash, Defensive → Slash, Controlled → Crush } — OSRS Chop/Slash/Block are Slash; Smash is Crush. - Godsword: { Aggressive → Slash, Defensive → Slash, Controlled → Crush } — same family shape; the godsword's distinguishing feature is that both its slash and crush AttackBonus entries are high (132/132), so picking Controlled is a real damage choice instead of a sacrifice.

Ranged

Bows (3-5 tick, ranged attack only — strength comes from ammo)

Two-hand slot. OSRS shortbows are 3t (fast, low ranged str on the weapon); longbows are 6t (slow, high accuracy). Capstone bows (Crystal, Faerdhinen, Twisted) break the pattern with weapon-supplied ranged str.

WeaponDamageType = Combat.DamageType.Ranged, DefaultStyle = Combat.Style.Aggressive (Rapid in OSRS — map to whatever the project's "fast-but-no-accuracy-bonus" style ends up tagged).

Arrows / bolts (ammo slot — supplies ranged strength)

Ammo authoring is identical to a one-line item: empty WeaponDamageType, ranged str only. Ammo consumption is keyed off the bow's WeaponDamageType == Combat.DamageType.Ranged — see COMBAT_SYSTEM.md "Ammo Slot".

Magic

Staves (magic attack + sometimes magic damage)

Magic damage on staves is a percentage (MagicDamageBonus, float — 0.15 reads as +15%). Most low-tier staves are pure magic-attack bumps; only capstone wands/staves carry the damage %.

WeaponDamageType = Combat.DamageType.Magic. SwingInterval depends on the spell, not the staff — OSRS spells are 5t (autocast); set staff SwingInterval = 3.0 as a baseline for autoattacks if the project models a staff "bash" cadence.

Armor

Defense matrix only; armor doesn't contribute to attack bonuses except where the OSRS source data does (rare — most lower-tier armor is pure defense). Magic defense is universally negative on metal armor in OSRS; preserved here because the shape matters (metal-armor mages get cratered by magic).

Body (platebody / chainbody, body slot)

Helmets (full helm, head slot)

Legs (platelegs, leg slot)

Same shape as platebody scaled ~2/3. Skipped per-tier — copy platebody column-wise at ~65%.

Shields (kiteshield, offhand)

Roughly platebody-scaled to 30-50%, plus modest Stab/Slash/Crush attack on dragon-tier and up.

Boots / Gloves / Cape / Amulet (jewelry & accessory slots)

These slots in OSRS contribute small flat per-axis bonuses and meaningful Str/Ranged-str/Magic-damage scalars — they're the slot where capstone scalar progression hides.

Capstone & Conditional Recipes (EquipEffects)

Conditional bonuses, multipliers, and set-bonus shapes use the EquipEffects GE path — not row scalars. See STAT_PIPELINE.md "Target-Conditional Modifiers". These are sketches; the GE classes need to be authored in C++ (or BP-inherited from a parameterized base) and dropped into EquipEffects at item-row author time.

Each recipe lists what authoring work is still required; the dependency table near the bottom (Roadmap to Shippable Recipes) summarizes the remaining work per recipe.

Slayer-helm equivalent — +15% melee Str vs assigned target

Row:
  StrengthBonus = 0   (no static contribution)
  EquipEffects  = [ GE_Item_StrengthBonus_Plus15_VsAssignedTarget ]

GE class:
  Modifier:                Strength += 0.15  (Multiply Additive)
  OngoingTagRequirements:  Status.AssignedTarget.MatchingFamily

Status.AssignedTarget.MatchingFamily is declared as a stub in DefaultGameplayTags.ini but has no current publisher — an EquipEffects GE gated on it will load and remain inert until an assignment system ships. Recipe is authorable now; expect it to fire only once that system lands.

Salve amulet — +15% melee acc & dmg vs undead

EquipEffects = [
  GE_Item_Strength_Plus15_VsUndead,
  GE_Item_AttackBonus_Plus15_VsUndead   (or via a synthetic accuracy attribute)
]

Both GEs:
  OngoingTagRequirements: Enemy.Family.Undead

Authoring requires the Enemy.Family.Undead leaf in DefaultGameplayTags.ini plus the two EquipEffects GE classes. The runtime hook that surfaces Enemy.Family.<leaf> tags during damage resolution is already shipped — see FTargetClassificationScope in Source/CRADL/Combat/TargetClassificationScope.h.

Dragon hunter lance — +20% acc & dmg vs dragons

Row:
  StrengthBonus     = (base lance value, e.g. 70)
  AttackBonus[Stab] = (base lance stab atk, e.g. 82)
  EquipEffects      = [
    GE_Item_Strength_Plus20_VsDragons,
    GE_Item_AttackBonus_Plus20_VsDragons
  ]

Conditional GEs:
  OngoingTagRequirements: Enemy.Family.Dragon

Same machinery as Salve amulet. Authoring requires the Enemy.Family.Dragon leaf in DefaultGameplayTags.ini plus the two conditional GE classes.

Berserker necklace + obsidian weapon — set bonus (+20% Str when both worn)

On Berserker necklace:
  EquipEffects = [ GE_Item_Strength_Plus20_WithObsidianWeapon ]

GE class:
  Modifier:                Strength += 0.20  (Multiply Additive)
  OngoingTagRequirements:  Item.Equipped.Material.Obsidian

UEquipmentComponent publishes Item.Equipped.Material.Obsidian on the owning ASC whenever any equipped item carries Item.Material.Obsidian in its row Tags. Authoring requires the Item.Material.Obsidian source tag on the obsidian weapon's FItemRow::Tags, the Item.Equipped.Material.Obsidian mirror in DefaultGameplayTags.ini (already declared), and the GE_Item_Strength_Plus20_WithObsidianWeapon class. No GE on the weapon itself — the necklace's conditional GE handles the +20%.

Ancestral / Ahrim's-style magic set — +6% MagDmg per piece

Three pieces, three identical row entries — no GE needed if the bonus is unconditional:

Per-piece row:
  MagicDamageBonus = 0.06    (stacks additively across all 3 = +18%)

If the design wants the set bonus to require all three pieces (rather than per-piece additive), move it to EquipEffects:

Per-piece row:
  MagicDamageBonus = 0       (no per-piece contribution)
  Tags             += Item.Material.Ancestral
  EquipEffects     = [ GE_Item_MagicDamage_Plus6_AncestralSet ]

GE class:
  Modifier:                MagicDamage += 0.06        (Additive; attribute is the % itself, composes by sum)
  OngoingTagRequirements:  Item.Equipped.Set.AncestralFull

Authoring requires the Item.Material.Ancestral source tag on each piece, the Item.Equipped.Set.AncestralFull mirror (already declared in DefaultGameplayTags.ini), a configured FEquipmentSetThreshold entry on the loadout's UEquipmentComponent ({SourceMaterial: Item.Material.Ancestral, MinPieces: 3, PublishedSetTag: Item.Equipped.Set.AncestralFull}), and the GE_Item_MagicDamage_Plus6_AncestralSet class. The per-piece additive recipe above remains the lower-friction option when full-set gating isn't strictly required.

(Note: the row field is MagicDamageBonus; the GE modifier targets the MagicDamage attribute. The synthesizer in UEquipmentComponent::ApplyEquipEffect bridges the two — runtime reads UCradlAttributeSet::GetMagicDamage(). Final damage scales by (1 + MagicDamage).)

DefenseBonusFlat — when to use it

The OSRS pipeline has no analog. The DefenseBonusFlat row field synthesizes into the universal Defense attribute via UGE_Equip_DefenseBonus at equip-time (synthesized in UEquipmentComponent::ApplyEquipEffect's SynthesiseScalar lambda). Reserve the row field for items whose defensive contribution isn't naturally per-axis:

• Set bonuses across non-comparable slots (e.g., "Wearing all 4 pieces of Justiciar grants +20 universal defense").
• Capes / amulets that read as "general toughness" rather than per-type plating.

Do NOT use DefenseBonusFlat for:

• Consumable defense potions — those write to the Defense attribute directly via their own HasDuration GE (CONSUMABLES.md "Stat Boost Channel"), they don't go through any row field.
• Per-archetype enemy defensive profiles — those use the UGE_DefMult_* per-type multiplier GEs on the DefenseMultiplier[Stab/Slash/Crush/Ranged/Magic] attributes (STAT_PIPELINE.md "Defense Granularity").

Tier-stamped gear in this document leaves DefenseBonusFlat = 0 and expresses all defensive character through the per-type DefenseBonus matrix.

Quick recipe for new tier authoring

1. Pick the family table above whose curve shape matches the new item's intended role.
2. Locate the OSRS tier closest to the intended power band.
3. Copy the recipe column values into the items DataTable row.
4. Set WeaponDamageType + DefaultStyle (weapons only) from the family header.
5. If the item has a conditional / set / multiplier bonus, author a GE class and attach via EquipEffects — leave the row scalar field for that stat at 0 (validator rejects double-author).
6. Run the items DataTable validator (Source/CRADLEditor/Validators/) — it enforces the one-path-per-stat-per-item rule from STAT_PIPELINE.md "Item Authoring Shape".

Roadmap to Shippable Recipes

Mapping each currently-pending recipe to the work it still needs:

The per-piece additive recipe path is the lowest-friction option for every set-style bonus that doesn't strictly require full-set gating. When in doubt, ship the per-piece additive first; the full-set marker is a tightening, not a foundation.