I interpret this as a game-development request involving conditional animation states tied to environmental tiles. The core task is probably not creating new animation assets from scratch, but modifying the sprite/animation system so that the player's idle state branches depending on terrain metadata — specifically whether the current tile is tagged as ice.

I'd infer there are already separate animation definitions or sprite rows available for standard idle versus icy idle behavior, and the important implementation detail is detecting tile context at runtime and switching animation state cleanly without disrupting movement transitions or causing animation flicker when entering or exiting ice tiles.

A few things worth confirming before touching the sprite sheet: do you have a separate idle-on-ice sprite row already drawn, or does that still need to be created? And is the tile tag system already in place, or are we also adding tile.type === 'ice' detection?

Good — with Phaser 3 and Tiled JSON, tile type detection is straightforward. You'll query the tilemap layer for the tile at the player's current grid position and check a custom property you set in Tiled.

In Tiled, select the ice tile in your tileset, open its properties, and add a custom boolean property: isIce: true. This gets embedded in the exported JSON and Phaser can read it directly. Then in your player update loop, something like:

const tile = layer.getTileAtWorldXY(player.x, player.y);
const onIce = tile?.properties?.isIce === true;

From there you switch animation state: if onIce and velocity is near zero, play idle-ice. The key is checking velocity before switching so a moving player on ice still uses the movement animation. Want me to write out the full state machine logic?

For the flicker issue, the standard approach is a small debounce on tile-type changes — don't switch animation state the moment the tile changes, wait until the new tile type has been stable for 2–3 frames. This catches the case where a player crosses a tile boundary quickly and lands on a non-ice tile within a single physics step.

Here's the full state machine with debounce baked in:

// In your player class
this.iceDebounce = 0;
const ICE_FRAMES = 3;

// In update():
const tile = layer.getTileAtWorldXY(this.x, this.y);
const tileIsIce = tile?.properties?.isIce === true;

if (tileIsIce) { this.iceDebounce = ICE_FRAMES; }
else if (this.iceDebounce > 0) { this.iceDebounce--; }

const onIce = this.iceDebounce > 0;
const isIdle = Math.abs(this.body.velocity.x) < 5;

if (isIdle && onIce) this.anims.play('idle-ice', true);
else if (isIdle) this.anims.play('idle', true);
else this.anims.play('run', true);

The true parameter in anims.play prevents restarting the animation if it's already playing — which is another common source of flicker.