Verdant 03 — Worlds: Snow, Desert & Volcanic [16x16]

Three biomes, and every one of them joins the grass properly.

Verdant 01 gave you a grassland. Verdant 02 gave it elevation. This is the rest of the world — a snowfield, a desert and a volcanic waste, each with a complete 47-mask transition into Verdant 01's grass, so the three packs build one continuous map instead of three separate ones.

And two things the earlier packs did not have: animated tiles, and a contact shadow under every prop.

A finished sample map — as data, not just a picture

A 30×20 map built from this pack ships in sample_maps/, as a PNG and as sample_map_01.json: every cell listed by tile id, with a legend and prop draw order, so you can rebuild or edit it in any engine instead of tracing it. Cells that use Verdant 01 grass are emitted as verdant-01-overworld:grass_N with a dependencies block naming the pack — stated openly rather than hidden.

What is in it — 330 tiles

• Six complete 47-mask autotile sets — 282 tiles. snow→grass · dune→grass · ash→grass · ice→snow · lava→basalt · mesa→dune
• 19 fills. 4 snow + tussock + ice sheet · 4 dune + crest + mesa + cracked earth · 4 ash + basalt + lava
• 9 props, every one with a contact shadow. Snow pine, boulder, ice shard · saguaro, mesa stone, skull · basalt column, embers, scorched snag
• 5 looping animations × 4 frames. Lava flow · water surface · drifting ice floe · torch · banner

Three of the transition sets carry a biome into Verdant 01's grassland. Three work inside a biome — sheet ice in the snow, a lava pool in the basalt, a mesa outcrop rising out of the dunes.

Animated tiles

The lava crust holds still while the light travels underneath it; foam rides the swell; dark leads of open water drift through the ice floe; the torch flickers on a hand-authored four-frame cycle; the banner's wave travels down the cloth.

Each loop advances a spatially periodic field by exactly a quarter period per frame, so the last frame leads back into the first with no duplicated endpoint and no stutter. Both properties are machine-checked before the pack builds: every sequence must MOVE (no two adjacent frames identical) and must LOOP. tiles.json gives your engine the frame order and the loop flag.

Contact shadows

The shadow ellipse is measured from each prop's footprint — the trunk, not the canopy — because a shadow scaled to the widest part of a sprite reads as a puddle the object is floating in. It is dithered with the same ordered Bayer matrix as the colour ramps, so it stays hard-edged pixel art rather than a soft airbrushed blob, and it only ever writes two declared palette colours.

Engine-ready, not just art

• RPG Maker MZ — object sheets at exactly 768×768, upscaled 16→48px by nearest-neighbour, plus a slots file mapping every tile to its sheet, column and row. The pack needs two sheets because it is larger than MZ's 256-slot limit; all 330 tiles are placed and none are omitted.
• Tiled — one .tsx per atlas, image copied beside it, so nothing dangles.
• Godot 4 — a TileSet resource describing all 330 tiles across 11 atlas sources.
• Plus one PNG per tile, role-grouped atlases, and tiles.json mapping tile → role → biome → slot.

What is proven, and what is not

• Exact grid. Every tile exactly 16×16, every sheet an exact multiple. Machine-checked.
• Palette lock. Every opaque pixel inside the declared 66-colour palette — 1,159,682 opaque pixels checked. The generator refuses an undeclared colour at write time rather than auditing for one afterwards, which is why tile 300 matches tile 1.
• No anti-aliasing. Alpha strictly binary — 1,967,616 pixels checked.
• Autotile completeness. All 282 mask slots across the six sets verified present.
• Seams. Every tile's wrap boundary is measured against its own interior, and every 4×4 repetition is rendered and reviewed by eye. That is a floor, not a proof, and we would rather say so: the automated check catches hard edge artefacts reliably and catches "edges taken from different regions of a larger image" only rarely, because that defect damages the interior the check calibrates against. The rendered fields ship in proof/ so you can check us.

Scoped limitations — stated up front

1. Transitions are biome-to-grass, not biome-to-biome. No snow→dune or dune→ash set; put a strip of grass between two biomes.
2. cracked_earth has no 47-mask entrance. Use it as a region with its own edge, not as scattered single tiles in sand.
3. No structures. The banner and the torch are the only built objects.
4. No elevation in the new biomes — cliffs and plateaus are Verdant 02, same palette and grid.
5. The Godot .tres is written to spec and has never been opened in the Godot editor. We do not claim it is Godot-verified, because we have not verified it.
6. The animated tiles ship as ordered frames, not as an engine-specific animation format. Your engine drives them; 8–12 fps suits the lava and water, 6–8 the torch.

The series

All three packs share one 16px grid and one palette, and each extends the last without changing a single colour of it — checked by regenerating the 228 tiles that engine produces and comparing them byte for byte against the files that pack currently ships. 228 of 228 identical, zero mismatches. (Verdant 01 also ships 11 grounded prop variants added later, composited rather than generated, which sit outside this check.)

• Verdant 01 — Overworld — 239 tiles, 5 ground materials, 4 autotile sets, 17 props
• Verdant 02 — Elevation — 149 tiles, plateaus and tall cliffs
• Verdant 00 — Free Sample — 64 tiles, free, if you want to try the palette first
• Verdant Forge — the generator, if you would rather make your own

Licence

Commercial use permitted, including in paid games, on unlimited projects, no attribution required. You may not resell or redistribute the pack itself as an asset pack. Full terms in LICENSE.txt.

AI disclosure

Graphics: yes. Every tile is generated programmatically by a procedural pixel engine written for this series — it places each pixel on an integer lattice and refuses any colour outside the declared palette. There is no diffusion model, no image generator and no upscaler anywhere in the pipeline; that is why the grid, palette and anti-aliasing claims above can be stated as measurements rather than as hopes. The code that generates the art is ours.