Loading recipe…

Skip lands a nudge immediately, success path. The nudge() promise resolves with the new visible column on the next microtask. exactly as if the tween had run to completion. Use this for player-driven turbo buttons or accessibility shortcuts where the post-nudge UI (win re-detect, spotlight, HUD update) should still fire.

The one-liner

const p = reelSet.nudge(2, {
  distance: 1, direction: 'down', incoming: ['wild'], duration: 1500,
});
skipButton.onclick = () => reelSet.skipNudge(2);
const { symbols } = await p; // success path

Call skipNudge(col) to skip a single reel, or skipNudge() (no argument) to skip every in-flight nudge across all reels. A skip on a reel that isn’t nudging is a no-op. safe to call defensively.

Skip vs abort

	`skipNudge(col)`	`signal.abort()`
`nudge()` promise	Resolves normally	Rejects with `AbortError`
Strip lands	Yes (deterministic)	Yes (deterministic)
Event	`nudge:complete` fires	`nudge:cancelled` fires
Use when	Player wants it NOW	Tear-down / cancel-the-whole-feature

See Abort a nudge for the rejection path.

How the RecipeRunner handles it

The canvas button in this site’s recipe runner intercepts the player’s mid-action tap. Its priority order:

If the recipe declared a custom onSkip callback in its return object, that wins.
Else if any reel isNudging, call reelSet.skipNudge().
Else call the spin pipeline’s skip() / requestSkip().

So this recipe needs no custom handler. the default behaviour does the right thing.

Abort a nudge. reject the promise, fire nudge:cancelled.
Nudge guide. full event map and contract.

The one-liner

Skip vs abort

How the RecipeRunner handles it

Related