<p>Before describing a rising multiplier, identify what is multiplied and when the value resets. ETGAME treats these as documentation questions rather than assumptions drawn from animation. The same displayed number can be misleading when its interval or calculation base is left out.</p>

<h2>Track multipliers and totals by scope</h2>
<p>For each multiplier or amount, write down its calculation base and the part of the sequence it covers. An amount awarded at one step differs from a total accumulated across the round. A comparison table should preserve that distinction. Where reset conditions or the meaning of a total are missing, mark the field as unresolved. A plausible-looking arithmetic example cannot substitute for a documented rule. Every amount should have a label describing the part of the round it covers. Keep a running total separate from newly awarded values, and document the base of any multiplier. If the scope remains unclear, preserve that uncertainty as a question for the rules.</p>

<h2>Describe the event before naming it</h2>
<p>An animated board can show several events in quick succession: an award, symbols being removed, replacement symbols appearing, and another evaluation. Start by describing what the rules say happens at each step. A familiar animation is not enough to identify the whole mechanic. The useful question is which event changes the board, which event checks a winning pattern, and where the documented sequence ends. Keep these observations separate before applying a feature label. A compact feature table can separate the initiating event, symbol changes, matching conditions, counter behaviour and stopping condition. Add the game version and a source for each rule being summarized. This structure is more informative than a single feature score because it shows which parts are known and which have not been stated. Use an explicit unavailable label for missing information rather than converting an empty field into a zero or a negative answer.</p>

<h2>Record an event sequence</h2>
<p>Write the initiating event, what changes on the board, and what happens next. Keep the exact feature label used in the source, but do not let it replace the sequence description. Add the game title, version and review date so the worksheet refers to a defined product rather than a generic animation. Record how symbols qualify for an award independently of how the board changes afterward. Add the documented continuation and termination conditions. If a counter or retained position is not explained, identify the gap instead of guessing its role from an animation.</p>

<p>Before using the worksheet summary, read the recorded events in order. Confirm which source supports the start, the changes and the end of the feature, and keep uncertain transitions separate. A single animation frame may not establish what was evaluated before or after it. The worksheet should show that limit instead of supplying a plausible but unverified sequence. Attach a source note to each conclusion that goes beyond direct observation. Where the game documentation uses a different term from your draft, keep the original wording and explain the editorial label separately. The completed sheet is a reading aid, not a test report. It does not establish probabilities, expected returns or a strategy for selecting when to play.</p>
ETGAME game mechanics guide