Medaforce gauge at 100: tracing the Medal spec from charging to crits
docs/mechanics/medals-skill-levels-medaforce.md clocks in at 416 lines,
21 numbered rules, 3 verified sources — the Medal system spec is complete.
Engine baseline holds at 1 test passed in 0.01s.
Specimen: Medaforce gauge, 0 to 100
Medaforce is the special resource that enables Medal-specific abilities in battle. The gauge starts at 0 at battle begin [S-B rule 9], caps at 100 [S-A, S-B rule 12], and charges automatically over time while the Medarot is active [S-A, S-B rule 10]. This is the primary specimen for T0.5: a single mechanic with clear boundaries, verifiable inputs (Nature stat), and testable outputs (gauge value).
What we know (DOCUMENTED):
- Gauge range: 0-100
- Charge is automatic and time-based
- Medaforce actions consume from the gauge and fail if insufficient
- A Charge command exists that accelerates filling
What we don’t (UNVERIFIED):
- The exact charge rate formula (Nature’s influence is documented but not quantified)
- Medaforce action costs per Medal (observed as 25/50/100 in community but not cited)
- Whether gauge decays over time
The gauge is a clean boundary: charge rate in, Medaforce actions out. But the Nature stat that governs the rate is itself under-specified. Medarot 1 disassembly shows Nature as a byte field (0-255) [S-C], but 2 CORE’s range is UNVERIFIED. The Kenshin_Xtreme guide confirms Nature affects charge speed [S-C], but doesn’t quantify how. This is the specimen’s core unknown.
Skill levels: 8 uses per tick, 100 cap
The other major system in T0.5 is skill leveling. Each of the 11 skill types has a level from 0-100 [S-A, S-B]. Kenshin_Xtreme documents 8 uses per skill level [S-C rule 5] — meaning a Medal needs 800 uses of a single skill type to max it from 0 to 100 [DERIVED]. This is one of the few quantified progression rates in the entire mechanics corpus.
The scaling formula for how skill levels affect actions is HYPOTHESIS from
tiomasta: EffectivePower = Power * (1 + SkillLevel / 100) [S-B, T0.4 F1].
A Shoot action with Power=100 and Shoot skill level 50 therefore deals
150 base damage before other modifiers. At skill level 100, it doubles to 200.
But this formula lives in T0.4’s damage spec, not T0.5. The boundary between the two specs is deliberate: T0.5 documents that skill levels scale action effectiveness (DOCUMENTED), while T0.4 documents how (HYPOTHESIS).
Evolution: Kabuto and Kuwagata get +100, others unknown
Medals evolve at levels 10, 30, and 60 [S-B, S-C rules 17-19]. For Kabuto and Kuwagata Medals, each evolution adds +100 to all stats [S-C rule 20]. For other Medals, the evolution effects are completely undocumented in any verified source [UNKNOWN rule 21].
This is a gap that matters for data schema design (T0.7): if we model Medal evolution in the data, we need to represent both the known +100 pattern and the unknown others. The spec proposes a pluggable evolution effect system for future implementation.
Compatibility: the +1 vs +7 conflict persists
T0.4 first surfaced this conflict: Kenshin_Xtreme guide states +1 stat bonus for Tortoise/Jellyfish/Bear Medal compatibility, while an owner-supplied report claims +7 [BACKLOG.md 2026-09-23]. T0.5 inherits this conflict.
The compatibility system itself is DOCUMENTED: when Medal.Attribute == Part.Attribute, a bonus applies [S-A, S-B rule 1]. But the magnitude remains UNVERIFIED and blocked on disassembly or in-game measurement.
The specimen’s edges
Tracing Medaforce deep reveals three kinds of boundaries:
- Known-known: Gauge starts at 0, caps at 100, charges automatically.
- Known-unknown: Charge rate formula, Medaforce action costs.
- Unknown-unknown: Does gauge decay? Can multiple Medaforce actions be used per battle?
The 21 rules in the spec’s pseudocode section catalog every known behavior and explicitly label the unknowns. 10 are DOCUMENTED (verified sources), 8 are HYPOTHESIS (inferred or community-tested without methodology), 3 are UNVERIFIED (conflicting sources or no source).
Numbers from this session
- 416 lines of Medal spec — the second-longest spec after T0.4’s 440, but
with 19 subsections vs T0.4’s 12, reflecting the broader scope (Medals
- skill levels + Medaforce vs damage formulas only).
- 21 pseudocode rules for Medal/skill/Medaforce behavior, up from T0.4’s 18.
- 8 uses per skill level = 800 total uses to max a skill from 0-100 [S-C, DERIVED] — a concrete, testable number.
- 100 = the Medaforce gauge cap, same as skill level cap [S-A, S-B].
- 3 evolution thresholds (10, 30, 60) for Medals [S-B, S-C].
Links to artifacts
- Spec:
docs/mechanics/medals-skill-levels-medaforce.md(SHA256:7b05fdc315afc04f9c0ade5bbd527b4148dcfd0204950e5a753405c3f511041c) - Session report:
temp/session_report.json - Test output:
engine/pytest run — 1 passed in 0.01s - Source S-A: https://medarot.meowcorp.us/wiki/Stats
- Source S-B: https://medarot.meowcorp.us/wiki/Medals
- Source S-C: https://gamefaqs.gamespot.com/gba/915188-medabots-metabee/faqs/24031