Imogen Pallister, slot mechanics editor
Slot Mechanics Editor
Our editor

Imogen Pallister

Imogen Pallister spent eight years as a game designer, shaping feature flow, reel behaviour and the rules screens players scroll through before a first spin. She now writes about how slot features actually resolve, and why two slots with the same headline features can play very differently.

Slot mechanicsFeature flowRules screens
The designer's view

Explaining a Slot the Way It Resolves

Most slot descriptions list features. Imogen's pages follow time. A round starts, symbols land, something is evaluated, something disappears, something else falls into its place, and only then do prizes, multipliers and collectors get their turn. Written in that order, a game with six moving parts stops sounding like six separate ideas and starts to read as one machine.

She learned that habit on the other side of the screen. As a designer she drew the flow charts that engineers built from, wrote the text in the info panels and sat through playtests where a player misread a single arrow and misjudged a whole feature. It left her with a strong dislike of vague wording and a habit of asking what a player would believe after reading a sentence.

Today her work covers cluster and cascade slots, multiplier stacking, sticky-feature bonuses, buy menus and the small print of paytables. She reads provider documents the way a designer does, looking for the spot where a summary quietly drops a condition, and she treats any page that cannot be redrawn as a flow chart as unfinished.

A good explanation can be redrawn as a flow chart by a stranger, so every page is written to be redrawn.

Working method

From Sequence Map to Published Page

Every page passes through the same four stages, in this order, before it goes to the reviewer.

1

Map the resolve order

Before any prose, she lists every event in a round in the order the game handles it: evaluation, removal, drops, reveals, multipliers, collection. Gaps in that list show where the explanation would have been guesswork.

2

Check the map on screen

The map is compared with the official demo, frame by frame where a chain moves too fast to follow, until the written order and the observed order agree.

3

Check numbers against the rules

Paytable values, coin ranges and buy prices are read from the info screen and the provider page. If a figure cannot be found there, it stays off the page instead of being estimated.

4

Write toward a decision

The draft ends with who the game suits and who should walk away, because a reader who has just learned the mechanics is finally able to judge that.

Coverage

What She Covers

Cluster and cascade mechanics

how removals, drops and repeated evaluations chain into one spin

Multipliers and collectors

which values stack, what they apply to and in which order they resolve

Bonus structures

triggers, retriggers, sticky features and how buy options change the cost of reaching them

Rules screens and paytables

reading provider documents and spotting where the summaries disagree

One writer, one maths reader

Every page Imogen writes goes to Tobias Wraxall, who recomputes the numbers with fresh eyes before it is published.

Meet Tobias