SF6Statsv0.20.18
Preparing fighter pageOpening fighter statsChecking saved stats first. New fighters take a little longer to prepare.

Saved match plans

Previously generated AI plans, with their original supporting stats and data dates. Expand a plan to read both perspectives.

Manon · Latest 100

What to improve

  1. Find the cause of punish events

    Punish Counters landed: profile 0.1 · reference 0.14

    Review five Punish Counters received and five landed. Separate whiffed attacks from unsafe actions on block before choosing what to practice.

    Try this

    Recreate one repeated situation in training. Check the spacing and frame meter, then practice a safer choice or a punish that actually connects.

    Supporting stats
    • Punish Counters landed: profile 0.1 · reference 0.14
    • Got Punish Countered: profile 0.1 · reference 0.11

  2. Review close-range choices

    Throws: profile 2.7 · reference 2.53

    Look at five close-range exchanges. Separate throw opportunities, throw attempts and defensive choices; the aggregate counts cannot show which option was correct.

    Try this

    Replay one recurring situation in training with both a strike and a throw recorded. Practice your chosen responses, then check how often you make that choice deliberately in matches.

    Supporting stats
    • Throws: profile 2.7 · reference 2.53
    • Throw techs: profile 0.4 · reference 0.56
    • Got thrown: profile 3 · reference 2.28

  3. Compare decisions across wins and losses

    Recent stored ranked sample: 14 wins in 28 games

    Choose two wins and two losses from the recent stored sample. Find one decision that changes between them; the record alone cannot explain why results changed.

    Try this

    Write down one specific decision to test in your next five games. Review whether you executed it and what happened, rather than judging the drill only by wins.

    Supporting stats
    • Recent stored ranked sample: 14 wins in 28 games

AI selects and prioritizes reviewed practice plans from the cited stats. Habits cover the whole profile; character records and recent samples have separate scopes. These are ideas to test, not confirmed weaknesses or video analysis. Latest reported trends across the last 100 matches, not lifetime habit averages.

Data saved Sep 9, 2026 · AI: nex-agi/nex-n2.5-pro:free

How to beat this player

  1. Test the close-range pattern

    Throw techs: profile 0.4 · reference 0.56

    Observe actual strike, throw and defensive choices at close range. Change one part of your familiar mix only after a tendency appears.

    Try this

    If the same response repeats twice, try a different option in that situation. If the player changes their response, return to varied choices instead of assuming the pattern is permanent.

    Supporting stats
    • Throw techs: profile 0.4 · reference 0.56
    • Got thrown: profile 3 · reference 2.28
    • Throws: profile 2.7 · reference 2.53

  2. Probe defense before committing

    Drive Parry: profile 2.1 · reference 1.8

    Test one familiar pressure situation and observe the actual response. Use that observation to vary your next choice; do not infer a success rate from event counts.

    Try this

    Try your usual strike/throw decision in a situation you understand. Repeat only if the response is consistent; if they adapt, vary your timing or reset to neutral.

    Supporting stats
    • Drive Parry: profile 2.1 · reference 1.8
    • Perfect Parry: profile 0.6 · reference 0.64
    • Drive Reversal: profile 0.1 · reference 0.3

AI selects and prioritizes reviewed practice plans from the cited stats. Habits cover the whole profile; character records and recent samples have separate scopes. These are ideas to test, not confirmed weaknesses or video analysis. Latest reported trends across the last 100 matches, not lifetime habit averages.

Data saved Sep 9, 2026 · AI: nex-agi/nex-n2.5-pro:free