Ingrid
Updated 8 hours agoSteamSteamOtherOtherC100%

れいまん

Let's Do This
Rank 36MR 1,500#258,775
Last 107–3Last 2014–6
Winrate
63%
69W · 41L · 110 stored
Ranked matches
110
selected mode
Wins
69
Ranked
Losses
41
Ranked
Peak MR
1,500
Ingrid

Ranked MR · Ingrid

32 local · 2 imported · 32 on chart · 259 battles stored

Latest game

DefeatRanked

Replay not requested
Ingrid
れいまん · Ingrid
A.K.I.
Opponent · A.K.I.baskerville

Playstyle reference

Habits vs top — Ingrid

Loading Ingrid…

Saved match plans

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

Alex · Latest 100

What to improve

  1. Review defensive decisions

    Drive Parry: profile 1.3 · reference 1.63

    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 this

    Record 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 1.3 · reference 1.63
    • Perfect Parry: profile 0.4 · reference 0.7
  2. Find the cause of punish events

    Punish Counters landed: profile 0.2 · reference 0.12

    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.2 · reference 0.12
    • Got Punish Countered: profile 0.1 · reference 0.12

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 10, 2026 · AI: nex-agi/nex-n2.5-mini:free

How to beat this player

  1. Use matchup records as scouting leads

    vs Alex: 7 wins in 11 games

    A lower win rate suggests footage to examine, not a guaranteed counterpick. Check whether the same difficult situation appears in multiple matches.

    Try this

    If 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 Alex: 7 wins in 11 games
  2. Separate a tendency from a one-off event

    Recent stored ranked sample: 20 wins in 30 games

    Scout several recent matches and compare wins with losses. Prepare around a repeated situation rather than one memorable mistake.

    Try this

    Use 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: 20 wins in 30 games
  3. Probe defense before committing

    Got thrown: profile 2.8 · reference 2.12

    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
    • Got thrown: profile 2.8 · reference 2.12
    • Drive Reversal: profile 0.1 · reference 0.47

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 10, 2026 · AI: nex-agi/nex-n2.5-mini:free

Ingrid · Latest 100

What to improve

  1. Find the cause of punish events

    Punish Counters landed: profile 0.3 · reference 0.13

    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.3 · reference 0.13
  2. Make Drive Impact a deliberate choice

    Drive Impact: profile 0.4 · reference 0.27

    Review five Drive Impacts and record the situation and outcome. Keep effective uses; investigate repeated failures rather than aiming for the reference frequency.

    Try this

    Record 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.4 · reference 0.27
    • Drive Impact gauge: profile 3.3% · reference 2.1%
  3. Give each meter spend a purpose

    SA3: profile 60% · reference 15%

    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 this

    Practice 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
    • SA3: profile 60% · reference 15%
    • SA2: profile 15% · reference 57%

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 13, 2026 · AI: dots-studio/dots-3-note-preview:free

How to beat this player

  1. Look for a repeatable punish opportunity

    Got Punish Countered: profile 0.4 · reference 0.08

    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 this

    Test 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.4 · reference 0.08
  2. Test the Drive Impact tendency

    Drive Impact: profile 0.4 · reference 0.27

    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 this

    Revisit 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.4 · reference 0.27
    • Drive Impact gauge: profile 3.3% · reference 2.1%
  3. Probe defense before committing

    Drive Parry: profile 2.4 · reference 1.51

    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.4 · reference 1.51
    • Drive Reversal: profile 0.3 · 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 13, 2026 · AI: dots-studio/dots-3-note-preview:free

Privacy settings

Allow YouTube/Twitch media, usage analytics and remembered history? Choices last 180 days and can be withdrawn here anytime.

More options & details

Optional features are off until you choose them. You can change or withdraw your choices here at any time.

Security and storage needed for features you request remain available, including saved fighters, replay requests and feedback.

Choices are saved for 180 days on this device. Turning analytics off reloads this page to stop the loaded beacon.

Privacy & storage