<p>A multiplier needs both an amount to act on and a boundary that defines its scope. This ETGAME guide separates a feature step from an entire round before interpreting accumulation or reset behaviour. A number on screen cannot supply those missing rules by itself.</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>When a game screen changes after an award, record the documented sequence rather than assigning a name from appearance alone. Removal, replacement and evaluation may be distinct steps. A screenshot can illustrate one moment, but the rules establish how that moment belongs to the round. Describe the action, the subsequent evaluation and the stopping condition separately so that an attractive animation does not stand in for a complete explanation. Compare like fields with like fields: what starts the sequence, what changes, how an award is evaluated, what a counter means, and what ends the sequence. Include the relevant version and the evidence behind the description. A missing rule should remain visible as a gap. Combining unrelated feature counts into a ranking would hide the distinctions that the table is supposed to explain.</p>

<h2>Record an event sequence</h2>
<p>Begin with the game and version, then describe the events in their documented order. Include the source title and date checked. A picture can illustrate a step, but it should not be treated as a complete account of the sequence or its stopping condition. 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