Why Your Tilemap Looks Like Stickers (and How to Fix It)
The map is fine. The tiles are fine. You exported them at the right resolution, the palette is consistent, and every sprite lines up on the 16-pixel grid. It still reads as stickers — like somebody cut shapes out of coloured paper and laid them on a board. Why your tilemap looks like stickers is almost never a resolution problem or a palette problem. It is a depth, lighting and edge problem, and every item on this list can be fixed without redrawing a single tile. Most of the fixes are export settings, blend modes, or one extra variant row in your atlas.
Flat Shading With No Consistent Light Direction
The failing look
Every tile looks lit from a slightly different angle. Grass blades cast their highlight to the upper-left, rocks highlight to the upper-right, the well has its bright side facing the camera. Individually each tile reads fine. Together they read as a pile of separate objects, because the eye cannot infer a sun.
The cause
Tiles drawn in different sessions, or by different hands, or traced off different references. There is no declared light vector anywhere in the project, so "top-lit" is a feeling rather than a rule.
The minimum edit
Pick one light vector and write it down. A common choice for top-down and 3/4 view is upper-left, roughly 35–45° elevation — light coming from the top-left of the screen, slightly toward the viewer.
Then obey it on exactly three faces:
- Top face — full value, this is your brightest plane
- Right / lower-right side face — mid value, one step down
- Left / lower-left side face — dark value, two steps down
That is the whole rule. A rock with a flat top, a grass tuft with a couple of side pixels, a crate, a barrel, a roof — all of them use the same three steps of the same ramp. The palette does not need to change. You are re-mapping existing colours onto fixed planes.
In the Neta Studio 3D game builder, if you are projecting a sprite onto a surface, the equivalent discipline lives in the material: use an unlit or flat-shaded material for anything that carries baked directional shading, and light everything else with a single directional light. Two lights plus baked-in lighting on the same object is how you get tiles that look painted on.
If you bake lighting into tiles and also run a directional light over the scene, the two will disagree somewhere on every map. Bake it, or light it. Mixing means the well is always lit from the wrong side.
No Value Hierarchy Between Ground, Detail and Prop
The failing look
Everything is equally important. The dirt path, the pebbles on the path, the fence, the fence's shadow, the tree — all sit in the same band of lightness. Squinting at the map produces one uniform grey texture, not a readable layout.
The cause
The palette has enough colours, but they all live in a narrow value range. Value hierarchy is a separate decision from hue. You can have twelve greens and still have no hierarchy, because all twelve greens are around the same lightness.
The minimum edit
Sort your layers into three value bands and refuse to let them overlap.
Layer | Role | Value band | Contrast vs. neighbours |
|---|---|---|---|
Ground | Base terrain — grass, dirt, stone floor | Mid, largest area | Low contrast internally |
Detail | Paths, cracks, flowers, debris | One step either side of ground | Medium contrast |
Prop | Trees, buildings, fences, characters | Darkest and lightest values in the scene | High contrast, carries outlines |
The reason this works is that the ground band is allowed to be boring. Ground is the page. If your grass tile has high internal contrast, it competes with the props standing on it, and the props stop reading as objects in front.
Check it by desaturating the whole map to greyscale. If you cannot tell ground from prop in greyscale, no amount of colour work will fix the sticker read.
Hard Uniform Outlines On Every Tile
The failing look
Every tile is enclosed. Grass tile, dirt tile, water tile, all wrapped in the same one- or two-pixel dark line. The map looks like a grid of framed pictures.
The cause
The outline is being applied per tile on export, usually automatically, instead of per object. An outline is a statement that "this thing is an object." Applying it to terrain says the terrain is also an object. Now everything is an object, and nothing sits behind anything.
The minimum edit
Delete the outline from the ground layer entirely. Ground tiles should butt against each other with no seam — the surface runs continuously and only changes colour where terrain changes.
Then add outlines only where an object boundary exists:
- Full outline around props and characters
- Partial outline (bottom and one side only) around objects that are meant to sit on the ground rather than stand on it
- No outline at all around ground transitions — those get edge variants instead, below
If your pipeline is doing outline-on-export, it is probably a post-process step in the atlas packer. Turn it off for the terrain row.
Outlines are not a style. They are a depth cue. The moment every tile has one, you have told the player nothing, because a depth cue that applies everywhere carries zero information.
The Missing Transition: Grass to Dirt With No Edge Variants
The failing look
Two sheets of stickers meeting at a line. The grass region ends, the dirt region begins, and the boundary is a hard, perfectly regular seam with a few awkward corners where the two patterns clip into each other.
The cause
You have exactly one grass tile and one dirt tile, and you are tiling them. Terrain without transitions has no boundary — it has a cut.
The minimum edit
Author an edge set. The minimum useful set for one terrain-to-terrain boundary:
- 1 interior tile (plain, already have it)
- 4 straight edges (N, E, S, W)
- 4 outer corners
- 4 inner corners
That is 13 tiles per terrain transition. If you are doing this by hand it is a couple of hours. If you are generating them, it is a shader or a mask bake. The important detail is that the edge tile belongs to the terrain being entered — a grass tile fading into dirt should be grass with a ragged, irregular bottom edge, not dirt with a neat top edge. Terrain erodes into its neighbour; it does not sit on top of it.
A cheap shortcut that gets you most of the way: keep a single interior tile per terrain and paint the transition by hand as a decoration layer, with irregular blobs of the incoming terrain overlapping the outgoing one. This reads acceptably in Neta Studio's Mini World-style low-detail scenes. It stops reading acceptably the moment the player walks the boundary, because the same blob repeats.
Cast Shadows Drawn Per-Tile Instead of Derived From the Light
The failing look
The tree has a shadow. The fence has a shadow. The rock has a shadow. They all point in different directions, and none of them agree with the highlights on the same objects. Or worse, every prop casts down-left, and every highlight is also down-left, which is physically impossible and reads as a printing error.
The cause
Shadows were drawn into the tile art as decoration, at the time the tile was made, without reference to the declared light vector. Once a shadow is baked into a tile, it is frozen — it cannot respond to the prop moving, and it cannot agree with anything authored later.
The minimum edit
Two options, and you should pick per object type:
Baked, but derived. Any prop that never moves gets its shadow drawn, but drawn from the declared vector: if light is upper-left at 40°, the shadow occupies the lower-right of the sprite and is offset by a distance proportional to the object's apparent height. A short fence has a short shadow. A tall tree has a long one. The ratio between card height and shadow length should be roughly consistent across the project.
Runtime, for anything that moves. Characters, doors, anything the player pushes. Use a projected shadow — in a 3D scene, that is a shadow map from the single directional light; in a 2D scene, it is a squash-and-offset blob under the sprite.
The failing configuration in the 3D game builder is specifically this: sprite-based props lit by a baked highlight, sitting on a real ground plane that receives a real directional shadow. The baked highlight says upper-left. The runtime shadow says whatever the light object says. Move the light once and the whole map falls apart. Fix it by baking neither, or by setting the sprite to unlit and letting the shadow do the work.
Scale Inconsistency: Props Drawn at Tile Scale, Not Scene Scale
The failing look
A chair the same size as a tree. A door two tiles wide and one tall. Boulders the size of the player's head, and also boulders the size of houses, in the same biome. The map has no consistent sense of how big a metre is.
The cause
The prop was drawn to fill its tile, because the tile grid is the only unit of measurement the artist had. The grid is a container, not a scale reference.
The minimum edit
Define the scene's unit first: for example, one tile equals roughly one metre of ground, and a typical character occupies one tile wide by two tiles tall. Then size every prop against the character, not against the tile.
If your tile is 32 pixels and a character is 64 pixels tall, a table should be around 32–48 pixels wide and 24–32 tall. A single door leaf should be about the character's width and slightly taller than the character. A tree trunk should be narrower than the character and the canopy much wider. Write these numbers into the asset naming or the atlas metadata so the next prop cannot drift.
The scale inconsistency check is cheap: place the player sprite next to everything in the scene, one at a time, in a straight line. Anything that makes you pause is wrong.
A Four-Background Test That Exposes the Sticker Read
Before anyone else sees the map, run it through four backgrounds. The settings matter less than the fact that you run all four, because each one isolates a different failure.
Test | Setup | What it exposes |
|---|---|---|
Own floor | Map in engine, actual ground material, no background | Whether baked lighting agrees with the real light; whether ambient and shadow values match the floor |
Flat colour | Map on a single mid-grey, no grid | Outline uniformity (every tile reads as a box) and value hierarchy failure |
50% zoom | Map scaled down | Ground texture noise competing with props; missing edge variants become regular, obvious dots |
Motion | Map with camera panning at normal play speed | Baked shadows that do not stay put; seams that only show when scrolling; scale inconsistency as props pass the player at different apparent speeds |
The flat-colour test is the one people skip and the one that catches the most. On a plain mid-grey, a sticker map is unmistakable — you see the rectangle of every single tile. A map with proper terrain transitions, no ground outlines, and a real value hierarchy looks like a continuous surface with objects on top of it, even with the background removed entirely.
The motion test catches what the others miss. Static frames hide a great deal. If you can pan the camera and nothing pops, the layering is holding. If edges shimmer, your terrain transition tiles are not aligned to the grid, or your camera is snapping to sub-pixel positions and the atlas has no padding.
Run the four tests before anyone plays it. Players do not report "the value hierarchy is flat." They report "it looks weird." You will spend longer guessing what weird means than you would have spent running the tests.
The Order to Fix Things In
If the map already looks like stickers and you have limited time, work in this order. Each step is cheaper than the one after it and each one changes the read.
- Turn off ground outlines. One export setting. Immediate improvement.
- Declare the light vector and re-map the three faces on existing tiles. No new art, just value reassignment.
- Flatten the ground band. Reduce internal contrast on terrain tiles so props can sit in front.
- Add one terrain transition set. Thirteen tiles for the boundary the player crosses most.
- Fix prop scale against the character. Adjust the handful of props that are obviously wrong.
- Re-derive or remove baked shadows. Last, because it is the most work and the least visible until everything else is right.
None of these steps require redrawing a tile from scratch. The failing look is a set of configuration and consistency mistakes stacked on top of each other, and they unstack in the reverse order they were made.
Why Your Tilemap Looks Like Stickers, in One Line
Because depth, light and edge are three separate systems, and the sticker read happens when any one of them is inconsistent — the drawing is the last thing to blame. Fix the light vector, fix the value hierarchy, fix the boundaries, and the same tiles will read as a place instead of a set of cutouts.
Keep going
Build the world it goes in
A tileset is a material with nowhere to stand. Every world on the 3D game builder was made from one written description and published as a page you can play — including The Cyclops' Island and Mini World.