Skip to content

Mythic Masters: combat feel hill climb to 7/10, rounds 1+ (from #3252) #3465

Closed

Description

@QuinnsCode

Leapfrogs #3252 (the leftovers of the superseded combat PRs #2946, #2949, #2950) into a climb with its own goalpost. Part of #2945 (orbit-and-commit combat, weighty attacks). The attacks redesign being built in #3268 (shapes, tempos, field kits, then telegraphs and effects) is the main thing this climb judges, so rounds follow its steps rather than racing them.

The goalpost

Target 7/10 for how a fight feels to watch and to play: weighty, committed melee where the fighters circle but never stand and trade, hits you can see land (squat, stagger, camera shove, shockwave), and wind-ups you can read and punish. No score yet: the first round scores main.

Agent judges run about 2 points high on visual climbs (#2943: judges 5, owner 3), so the owner's score at the target decides it, through one MANUAL RUN.

One round

One worker, from main:

  1. BEFORE: hit-cued bursts from main (apps/mythic-masters/scripts/burst-shots.ts, side camera via window.mythicMasters.camera("side")), one fight per archetype, saved to apps/mythic-masters/docs/shots-<date>-combat/.
  2. The change the newest Next: line names.
  3. NOW: the same bursts, then a fresh judge agent scores BEFORE vs NOW out of 10 without the worker's reasoning. Keep the change only if the score went up.
  4. Balance must hold: bun run tune 800 before and after, every creature still wins 41-55%.

Carried over from #3252 (each has its own issue)

Ending a round

Comment here, first line Score: x/10 (target 7), then the shots, then Next: <the judge's top gap>. The PR says "Part of #", never a closing word. Then hop forward (the baton text is in scripts/climbs.ts).

Activity

  1. QuinnsCode commented on Nov 4, 2026

    @QuinnsCode
    OwnerAuthor

    Score: ?/10 (target 7)

    No score yet. The goalpost is new; it leapfrogs the leftovers in #3252.

    Next: score main with hit-cued bursts (the before shots #2953 never got), then a judge's top gap.

  2. self-assigned this
    on Nov 4, 2026
  3. QuinnsCode commented on Nov 4, 2026

    @QuinnsCode
    OwnerAuthor

    Score: 5/10 (target 7)

    Round 1, PR #3492. A fresh judge scored main 4.5/10. A second fresh judge then scored BEFORE 4/10 and NOW 5/10.

    The change: the bruiser and tank bot now circles a ring 0.8 m outside its reach and steps in only to swing (or to punish an opening), then backs out. Before, it held its spacing inside its own swing and traded. balance.json was re-fit, and every creature is at 44-56% (main was 42-55%).

    Shots: apps/mythic-masters/docs/shots-2026-11-04-combat/ (before-* and now-*), made with bun scripts/burst-shots.ts <dir> <prefix> --combat: one fight per archetype, a wind-up burst and a hit burst, frames 0.2 s apart. They are on the PR branch until it merges.

    The judge's next gaps, in order:

    1. Wind-ups you can see: about 0.4 s of anticipation (pull back, sink, a reach arc on the ground), tracking stops partway through so a sidestep beats it, and bots sometimes sidestep it. Today the tell lasts under 0.2 s. This one should follow Mythic Masters: build the attacks redesign (shapes, tempos, field kits) #3268 step 4 (telegraphs).
    2. Impact on every hit: hit-stop, the struck fighter squashes and slides about 0.5 m with dust, the camera shoves, and the tank's ground ring plays on every heavy hit.
    3. More spacing in the bot: skirmisher and flyer exchanges still close to trading range; whiffs need recovery frames that can be punished.

    Note: the issue's bun run tune 800 would be 800 matches per pairing, hours of runs. The per-creature 41-55% check is bun scripts/tune.ts --each 6 (one minute).

    Next: readable wind-ups, about 0.4 s of anticipation with a pull-back pose and a ground reach arc, and tracking that stops partway so a sidestep punishes it (alongside #3268 step 4).

  4. QuinnsCode commented on Nov 4, 2026

    @QuinnsCode
    OwnerAuthor

    Moved up to #3493

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions