element-ability-table
/element-ability-table
Query the fleet's element → ability → level-5-upgrade table — which ability each element owns on each vessel, what its L5 upgrade is and where that upgrade is actually gated, and how the ability scales with its element (with the authored numbers). Reads the shipped assets and code, never the docs. Use when asked what an element does on a vessel, what a level-5 upgrade is or whether one is really wired, whether an element slot is an open design slot, or before touching Assets/Resources/ElementalAbilityMaps/**, an ElementalAbilityMapSO, ElementalScaling, ElementalFloat, or any IsUpgradeActive ga
- Author
- froglet-studio ↗
- Repository
- cosmic-shore ↗
- Licence
- MIT
- Last repository change
- 28.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Query the fleet's element → ability → level-5-upgrade table — which ability each element owns on each vessel, what its L5 upgrade is and where that upgrade is actually gated, and how the ability scales with its element (with the authored numbers). Reads the shipped assets and code, never the docs. Use when asked what an element does on a vessel, what a level-5 upgrade is or whether one is really wired, whether an element slot is an open design slot, or before touching Assets/Resources/ElementalAbilityMaps/**, an ElementalAbilityMapSO, ElementalScaling, ElementalFloat, or any IsUpgradeActive ga
Original author description
Query the fleet's element → ability → level-5-upgrade table — which ability each element owns on each vessel, what its L5 upgrade is and where that upgrade is actually gated, and how the ability scales with its element (with the authored numbers). Reads the shipped assets and code, never the docs. Use when asked what an element does on a vessel, what a level-5 upgrade is or whether one is really wired, whether an element slot is an open design slot, or before touching Assets/Resources/ElementalAbilityMaps/**, an ElementalAbilityMapSO, ElementalScaling, ElementalFloat, or any IsUpgradeActive ga
How it works
- What it is joining, and why that is the whole point
- The four scaling channels
- Reading the flags
- The gate that still applies
SKILL.md preview
---
name: element-ability-table
description: Query the fleet's element → ability → level-5-upgrade table — which ability each element owns on each vessel, what its L5 upgrade is and where that upgrade is actually gated, and how the ability scales with its element (with the authored numbers). Reads the shipped assets and code, never the docs. Use when asked what an element does on a vessel, what a level-5 upgrade is or whether one is really wired, whether an element slot is an open design slot, or before touching Assets/Resources/ElementalAbilityMaps/**, an ElementalAbilityMapSO, ElementalScaling, ElementalFloat, or any IsUpgradeActive gate.
---
# Element ability table
```bash
python3 Tools/Build/element_ability_table.py # whole fleet (~1s)
python3 Tools/Build/element_ability_table.py Dolphin Sparrow # named vessels
python3 Tools/Build/element_ability_table.py -e Space # one element, fleet-wide
python3 Tools/Build/element_ability_table.py --gaps # only rows that disagree
python3 Tools/Build/element_ability_table.py -v Dolphin # + the authored prose
python3 Tools/Build/element_ability_table.py --json # machine-readable
```
Run it **before** answering any question about what an element does, and before editing a map
asset. It is a READER — it writes nothing, needs no ship contract (`Docs/TOOLING.md`), and never
opens Unity.
## What it is joining, and why that is the whole point
An element's ability is **declared** in one place and **implemented** in others, and the three
drift. `/vessel` SKILL.md §2 states the rule this tool automates: *docs drift; the map asset, the
prefab and the code are the record.*
| Source | What it is the record of |
|---|---|
| `Assets/Resources/ElementalAbilityMaps/{Vessel}.asset` | the DECLARATION — ability name, input, unlock/relock levels, latch policy, the L5 upgrade's name and prose. **No numbers**: the generic multiplier was retired 2026-09-18 |
| `IsUpgradeActive(Element.X)` call sites | the L5 UPGRADE, actually. The replicated `NetElementUnlocks` bit is the only thing that makes an upgrade real. **An `UpgradeLabel` with no reachable gate is prose.** |
| the four scaling channels below | the SCALING, actually |
The tool resolves which of those call sites a given vessel **reaches** — a reference walk from
`{Vessel}.prefab` through its wired action SOs, its executors and vessel-root components, and its
impact-effect containers, plus one hop through static calls (over comment- and string-blanked
source, so a doc comment naming a type is not a call). Never a naming convention. Where a site
takes its element or its endpoints from a serialized field, the value is read from the asset
instance the walk actually arrived at, so the numbers printed are **that vessel's** numbers.
**It reads four shapes of authored value, and knowing which is which saves an argument:** a
contiguous ElementalFloat block on an asset; the scattered `m_Modifications` entries a **nested
prefab instance** writes (six of twelve vessel prefabs author a float this way); a C# **field
initializer**, which is the only home a `static` class has and is also what ships when an asset
predates the field (rule 4-i); and a serialized bool's **C# default**, so an unauthored `false`
correctly reads as a dead branch rather than a live gate. All four were blind spots until
2026-09-18, and between them they accounted for seven of twelve reported gaps
(`Docs/ElementalAbilitySystem/FLEET_GAPS.md` §3).
## The four scaling channels
A row is only "no scaling" if all four are absent. This is the part that is easy to get wrong by
grepping.
1. ~~**Generic map multiplier**~~ — **RETIRED 2026-09-18** (`ELEMENT_SCALING_UNIFICATION.md`). It
addressed an ELEMENT and not a parameter, so every reader of that element got it. A leftover
`MultiplierAtFullLevel` in an asset is now a loud finding (`RETIRED CHANNEL PRESENT`), never a
tuning value.
2. **Bespoke authored endpoints** — `ElementalScaling.Multiplier` / `MultiplierFromRest` /
`RoundGrowthFactor` with a `…AtRest<Element>` / `…AtFull<Element>` pair on an action or effect
SO. Printed as `×a at rest → ×b at L10`.
3. **`ElementalFloat`** — pure serialized data (`Enabled`/`Min`/`Max`/`element`) with **no call
site at all**; `EvaluateLive` lerps Min→Max over level/10. Printed as `a → b across L0..L10`.
The Squirrel's Mass slot is only this.
4. **A direct level read** feeding a bespoke lerp (`GetLevel(Element.X)` +
`…AtResting<Element>` / `…AtFull<Element>` beside it). Printed as absolute values, not a
multiplier. The Urchin's Slip is only this.
Several channels on ONE element is now ordinary and correct — the Sparrow's MASS scales turret
prism stretch, bullet growth and missile growth: three parameters, one element. The old
**TWO LIVE SCALING CHANNELS** flag is gone with the channel whose specific hazard it guarded
(generic + bespoke landing on the same number), which cannot happen once every channel names its
own parameter.
## Reading the flags
| Flag | What it means |
|---|---|
| `OPEN DESIGN SLOT` | the map authors no ABILITY. **Blocked on design, not wiring** — see the gate below. **It can still carry a live L5**: the row is keyed off `AbilityLabel`, so an approved upgrade on an element with no ability yet (the Rhino's Space-5 Breaker, 2026-10-13) is COUNTED in the `L5 gates wired` total but its label and gate site are not printed. Read the map's `UpgradeLabel` before concluding the element has nothing. |
| `UPGRADE IS PROSE` | `UpgradeLabel` is authored and no live gate is reachable |
| `RETIRED CHANNEL PRESENT` | a generic map multiplier is still authored, or something still calls `handler.Multiplier(element)` |
| `NO SCALING` | none of the four channels is live for this element |
| `gate exists but the map names no upgrade` | a SHARED effect SO puts a gate in this vessel's reach (every hull carries a crystal-explosion effect and a `VesselPrismController`) while the map declares no upgrade. Usually noise. |
| `(inert - authored ×1)` | a bespoke endpoint pair authored ×1 → ×1, i.e. "this element does not scale me" |
| `[OFF: field = 0]` | the code is reachable but a serialized bool in the same condition is authored **false on this hull** — the Dolphin reaches the Squirrel's Heavy Trail gate with `massUpgradeShieldsTrail: 0` |
| `[OFF: field (unauthored, C# default false) = 0]` | the same, but the bool is **absent** from this prefab's YAML, so Unity ships its C# initializer. `turnUpgradeShieldsTrail` is absent on ten of twelve vessel prefabs |
**A row with every gate `[OFF]` prints `UPGRADE IS PROSE … (every gate is authored off on this
hull)`.** That is how the Scarab's "Armored Switch" — retired in code on 2026-08-24 and still
named by the map — was finally caught.
## The gate that still applies
**Never invent an element→ability→input mapping or an L5 upgrade to fill an open slot or to
clear a flag.** Open slots on Rhino / Serpent are blocked on design; proposals live in
`Docs/ElementalAbilitySystem/FLEET_MAPS.md` §2 and are un-implemented until Garrett marks them
up. A flagged row is a finding to REPORT, not a defect to silently fix — several are shipped,
play-tested behaviour. For any actual edit, use the `/vessel` skill.
Versions
The database has no other skills named element-ability-table.
Database snapshot: 13.11.2026 · package version a99f6e453df0 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 91vessel
Use for ANY work on a Cosmic Shore vessel class — creating or registering a new vessel, vessel abilities/actions/executors (R_VesselActions), elemental ability maps and level-5 upgrades, vessel HUDs (the four-icon ability row, control hints, gauges, controller/view pairs),… - 100ability-system
Use when building or replacing an ability system — abilities with cost/cooldown, buffs/debuffs, stat modifiers, and gameplay tags. Not for extending an existing one - 100arenagame
Use for ANY new Cosmic Shore ARENA game mode - a card that seats SEVERAL vessel classes (the Arena screen's roster, ArenaGames, launched through the ArenaLaunchPanel's vessel carousel) - or a change to how one is authored - a per-hull STARTING ELEMENT table… - 95godot-ability-system
Expert patterns for RPG/action ability systems including cooldown strategies, combo systems, ability chaining, skill trees with prerequisites, upgrade paths, and resource management. Use when implementing unlockable abilities, character progression, or complex skill systems.… - 90godot-ability-system
Expert patterns for RPG/action ability systems including cooldown strategies, combo systems, ability chaining, skill trees with prerequisites, upgrade paths, and resource management. Use when implementing unlockable abilities, character progression, or complex skill systems.… - 90element-plus
Element Plus Vue 3组件库开发专家助手。当用户需要进行Element Plus组件使用、按需自动导入、主题CSS变量定制、el-table/el-form/el-dialog等常用组件封装或组件库防坑处理时调用。