How should you read a Mirrors High Draw Point Bonus line?
Start with one line and one event. Write down the exact variant, the ability heading, the required event and the displayed reward. The similar numbers in the fact table do not make the events interchangeable. A record of an attempted action also does not establish that the required event happened. This is a source-reading aid, not a simulation of an entire point economy.
The examples come from the October 23 official introductions, checked October 31, 2026. They remain marked as development information that may change. Match the current in-game text before using a statement to evaluate your own account. An observed disagreement is a reason to check the version and condition, rather than silently replacing one source with a guessed rule.
Separate the event from the action you intended
Suppose you press an action because you expect a reward. Your intention is not the evidence you need. First identify what the relevant line requires, then record whether that event was actually confirmed. Keep an unsuccessful attempt in a different column from a confirmed event. That distinction prevents a failed setup from becoming an unsupported claim that the reward is broken.
The Ichigo character guide addresses his wider offensive kit. This page owns a narrower question: which reward statement belongs to the event being inspected? It does not replace the exact variant guide, assign a new tier or tell you that every character has the same event coverage. A familiar action name alone is insufficient to transfer another record’s bonus.
Why should overlapping-looking rewards stay separate?
Two lines can look relevant to the same moment without proving how the game resolves them together. Do not add their values and label the sum a verified payout unless the current rules or a properly documented observation establishes that relationship. The lookup preserves individual statements. It does not decide hidden eligibility, stacking, event priority or whether a particular animation satisfies several conditions.
A useful note can say that two candidate lines need investigation. That is more informative than a confident total with no evidence of the event sequence. If you later collect observations, record the setup and the individual events clearly enough that another person can understand what was compared. A favorable isolated screenshot cannot establish a general rule for every encounter.
Keep entry and standby descriptions attached to their source
The Rangiku guide offers a contrasting record because movement between field and standby appears in her published conditions. For this page, keep the reward-bearing event in the note. Use the separate Chain Attack guide when your uncertainty is which entry or standby term a statement refers to. Repeating the same numeric reward table there would not answer a different question.
Preserve qualifiers and headings rather than simplifying every arrival into one generic entry. A later switch is not evidence that a line headed First Entry repeats. Equally, the brief preview should not be expanded into a complete repeatability model that the source does not explain. When the current screen is unclear, leave that part unresolved and record the text you actually have.
What should a short observation record contain?
Use a narrow question, such as whether the named event is recognized in your chosen situation. Keep the character variant, active abilities, target or mode and relevant teammates together. Then separate the intended action, confirmed event and observed outcome. Leave those fields blank until you have observations. The worksheet does not supply a sample result that could be mistaken for playtesting.
Change one relevant condition when you can. If your setup, investment and opponent all change between attempts, a different result cannot be confidently attributed to one reward line. If the obstacle is that a teammate is unavailable, investigate Switch cooldown separately. A reward statement by itself does not establish that the next planned action is available.
What does this page deliberately leave uncalculated?
These kit statements do not establish the full set of spending costs, regeneration rules, caps or an optimal action order. They also do not establish a conversion into summon currency, guaranteed pulls or exchange rewards. Keep a combat ability’s named bonus separate from a claim about obtaining characters. Current official game screens are needed for questions outside this reading task.
Use ability stages when an effect belongs to a different stage from your current copy, and the editorial method when deciding what counts as evidence. This page’s output is a clearer statement to check, not a damage score or a measured resource return.