Saved match plans
Previously generated AI plans, with their original supporting stats and data dates. Expand a plan to read both perspectives.
Ken · Latest 100
What to improve
Find the cause of punish events
Got Punish Countered: profile 0.3 · reference 0.09
Review five Punish Counters received and five landed. Separate whiffed attacks from unsafe actions on block before choosing what to practice.
Try thisRecreate one repeated situation in training. Check the spacing and frame meter, then practice a safer choice or a punish that actually connects.
Supporting stats
- Got Punish Countered: profile 0.3 · reference 0.09
- Punish Counters landed: profile 0.2 · reference 0.11
Make Drive Impact a deliberate choice
Drive Impact: profile 0.3 · reference 0.18
Review five Drive Impacts and record the situation and outcome. Keep effective uses; investigate repeated failures rather than aiming for the reference frequency.
Try thisRecord Drive Impact and an ordinary attack in separate dummy slots. Mix playback and practice recognizing the difference with a response available in your current gauge state.
Supporting stats
- Drive Impact: profile 0.3 · reference 0.18
- Drive Impact gauge: profile 2% · reference 1.3%
Review defensive decisions
Drive Parry: profile 0.6 · reference 1.97
Compare five defensive situations: what did the opponent do, what did you choose, and what happened? Low parry or throw-tech counts alone do not establish a weakness.
Try thisRecord two different options from one troublesome situation. Practice identifying them and choosing a response, then review whether the same decision improves in your next set.
Supporting stats
- Drive Parry: profile 0.6 · reference 1.97
- Perfect Parry: profile 0.4 · reference 0.79
- Drive Reversal: profile 0.1 · reference 0.21
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 6, 2026 · AI: dots-studio/dots-3-note-preview:free
How to beat this player
Test the Drive Impact tendency
Drive Impact: profile 0.3 · reference 0.18
Observe whether Drive Impact repeats in a particular situation. Prepare a response you have verified in training, while respecting range, recovery and available gauge.
Try thisRevisit that situation with a less committal approach. If the Impact appears, use your practiced response; if it does not, resume your usual game plan.
Supporting stats
- Drive Impact: profile 0.3 · reference 0.18
- Drive Impact gauge: profile 2% · reference 1.3%
Probe defense before committing
Drive Parry: profile 0.6 · reference 1.97
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 thisTry 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 0.6 · reference 1.97
- Perfect Parry: profile 0.4 · reference 0.79
- Drive Reversal: profile 0.1 · reference 0.21
Test the close-range pattern
Throws: profile 1.3 · reference 2.59
Observe actual strike, throw and defensive choices at close range. Change one part of your familiar mix only after a tendency appears.
Try thisIf 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
- Throws: profile 1.3 · reference 2.59
- Throw techs: profile 0.4 · reference 0.46
- Got thrown: profile 2.4 · reference 2.28
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 6, 2026 · AI: dots-studio/dots-3-note-preview:free
Luke · Latest 100
What to improve
Find the cause of punish events
Got Punish Countered: profile 0.3 · reference 0.06
Review five Punish Counters received and five landed. Separate whiffed attacks from unsafe actions on block before choosing what to practice.
Try thisRecreate one repeated situation in training. Check the spacing and frame meter, then practice a safer choice or a punish that actually connects.
Supporting stats
- Got Punish Countered: profile 0.3 · reference 0.06
Review defensive decisions
Drive Parry: profile 0.6 · reference 1.82
Compare five defensive situations: what did the opponent do, what did you choose, and what happened? Low parry or throw-tech counts alone do not establish a weakness.
Try thisRecord two different options from one troublesome situation. Practice identifying them and choosing a response, then review whether the same decision improves in your next set.
Supporting stats
- Drive Parry: profile 0.6 · reference 1.82
- Perfect Parry: profile 0.4 · reference 0.71
- Drive Reversal: profile 0.1 · reference 0.2
Give each meter spend a purpose
Drive Arts: profile 7.5% · reference 15.4%
Review five resource decisions with the actual gauge visible. Note what the spend gained and what options remained; usage shares alone cannot measure efficiency.
Try thisPractice a familiar sequence with a resource spend and a conservation alternative. Compare the outcome and remaining gauge before deciding which situation calls for each.
Supporting stats
- Drive Arts: profile 7.5% · reference 15.4%
- SA2: profile 12.5% · reference 22.5%
- Drive Guard: profile 6.5% · reference 13.7%
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 6, 2026 · AI: dots-studio/dots-3-note-preview:free
How to beat this player
Use matchup records as scouting leads
vs Ryu: 9 wins in 16 games
A lower win rate suggests footage to examine, not a guaranteed counterpick. Check whether the same difficult situation appears in multiple matches.
Try thisIf you play the cited character, test one familiar situation from that footage. If the player handles it well, abandon the assumption and adapt to what they show.
Supporting stats
- vs Ryu: 9 wins in 16 games
- vs Luke: 6 wins in 12 games
Separate a tendency from a one-off event
Recent stored ranked sample: 22 wins in 41 games
Scout several recent matches and compare wins with losses. Prepare around a repeated situation rather than one memorable mistake.
Try thisUse the first round to check one scouting hypothesis. If it repeats, apply your prepared adjustment; if it does not, discard it and observe a new pattern.
Supporting stats
- Recent stored ranked sample: 22 wins in 41 games
Look for a repeatable punish opportunity
Got Punish Countered: profile 0.3 · reference 0.06
Use the stats as a scouting lead. Watch for an action you have already verified as punishable at that spacing; do not assume every apparent opening is unsafe.
Try thisTest one confirmed response when that action appears. If it stops appearing, return to your normal spacing instead of forcing the punish.
Supporting stats
- Got Punish Countered: profile 0.3 · reference 0.06
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 6, 2026 · AI: dots-studio/dots-3-note-preview:free

