Fist of God — art mockup

Nothing on this page is wired to the game. It is the place the Fist's art and its timing get settled, the way Eruption's were settled on docs/verify-shots/eruption-mockup.html. The terrain underneath is the same straight port of MapRenderer.buildTerrainCache that page used (same palette, same jittered borders, same tile details, same tileSize = 20), so the fist is being judged against the real map at the real size, not against a stand-in.
Every number below is a slider. Play to a version you like and the slider readouts are what goes to powersConfig.

THE FIVE BEATS, IN YOUR ORDER.

  1. A pixellated god fist appears about 200px above the map and comes down on it.
  2. It lands with a crash: chunky pixels are thrown into the air and bounce, and the screen shakes.
  3. It hurts any creature it lands on. (Structures too. Structures do not exist yet, so that half is a note for later.)
  4. The fist dissipates like a dust cloud.
  5. When the dust clears, every mountain and forest tile in a 4×3 grid is grass. Water and ocean untouched.

1. The full cast, start to finish

Click anywhere on the map to slam there, or press Slam for the last spot. Hovering shows the aim rectangle: a tile outlined in gold will be levelled, a tile outlined in blue is water and is left alone. The dust cloud is deliberately thick enough to cover the moment the ground changes: the terrain re-bake happens inside the cloud, so the map is already grass when the dust thins. That is not just staging, it is the honest place to hide the one expensive frame this power costs (see the readout under the canvas).

level
px ms px px px % of rock px px ms
ms ms ms % of crumble ×
idle · click the map re-bake: not yet measured

THE ONE EXPENSIVE FRAME. The number above is this page baking its whole 46×30 terrain in one call, which is the same shape of work the client's patchTerrain does on a tilesChanged broadcast (measured in the game at 144-239ms on a real world, which is bigger than this one, so treat the figure above as a floor and not as the game's number). It is the reason the twelve tiles must go over the wire as ONE broadcast: twelve events is twelve re-bakes and about two seconds of frozen frame.

UPDATE 2026-09-09: the game no longer works that way. patchTerrain re-bakes only the tiles that actually moved, measured by tools/bench-bake.js at 1.3 to 5.8ms per single tile against a 145ms full bake, so the figure above is this page's own bake and not the client's cost any more. Both rulings survive it. One broadcast is still right, because one array is one patch and one render rather than twelve of each; and re-bake at is now about PHASING rather than cost, which is the more interesting half. Sliding it to 0% fires the change on the impact frame, where the hitch lands on top of the shake and reads as a stutter; at 35% it lands inside the thickest part of the cloud, where nothing is moving that you can track.

2. The fist itself

The sprite at 1× over the three grounds it has to read against, and at 3× so the pixels can be argued about. It is modelled on your reference sprite and flipped vertically, which is also the only orientation that makes sense here: the wrist goes up into the sky and the curled fingers are at the bottom, so the fingers are what arrives first and what hits the ground.
It is built as labelled regions (a hand, four fingers, a thumb) rather than as a shaded lump, and the hard black line falls out of wherever two regions meet, which is what makes the creases between the fingers read at all. A hard outline over a six-step ramp, lit from the north-west like every other rock on this map, with the shading gradient taken within each region only so every finger keeps its own lit edge and its own shadow. The fist grain and shade band sliders genuinely re-cut it at the new resolution rather than scaling a picture. Three separate grain dials: the fist is a carved object, the thrown rock is loose material, and the ground shadow is a stamp. They want different block sizes, so they have different sliders. (The dust that the fist itself crumbles into keeps the fist's grain, deliberately: those motes were the fist a moment ago.)

loading the drawn sprite...

3. The 4×3, before and after

The same patch three times: as it stands, what the cast claims, and what it leaves. Mountain and forest go to grass. Grass was already grass. Lake and ocean are untouched, which is what makes the footprint a ragged shape rather than a stamped rectangle, and is the thing worth looking at hardest here: a cast half in the sea leaves a bite out of the coast.

4. What this page has not decided

Every row wants your ruling. None of them is art, which is why none of them is a slider.

questionthe neighbours it has to sit againstmy recommendation
Damage
per rank now
Eruption's opening blast is 20 / 30 / 40 and its lava is ~4 HP/s over a long burn. Terraform does none. A single crushing blow, flat, no falloff, everything in the rect, and it should out-hit Eruption's opener because Eruption gives five seconds of warning and this gives none. Now that there are three ranks it wants three numbers: 30 / 45 / 60 against Eruption's 20 / 30 / 40. Note the shape of the trade, because it is the interesting one: rank III already hits four times as many tiles as rank I, so if its damage also doubled there would never be a reason to cast I on anything but a single creature.
Cooldown
SETTLED
Terraform is 60s for one permanent tile. Eruption is 180 / 240 / 300s. Per rank, 120 / 240 / 360s, against Eruption's 180 / 240 / 300. Twelve permanent tiles per cast is twelve Terraforms, and this also kills; twenty-four is worth waiting six minutes for. Trap: a recharge lives in BOTH COOLDOWNS_MS and the per-tier override the cast handler applies, and changing one leaves the tooltip printing the stale number.
The three ranks
SETTLED
Ranked powers here are a cast picker, not an upgrade ladder: Eruption's node data says "Adds Eruption II to the cast picker" and the client carries a selectedLevel, so a god who owns III still casts I whenever they want. Raze I 3×2 = 6 · Raze II 4×3 = 12 · Raze III 6×4 = 24. The footprint doubles each rank. Rank I is the small one on purpose: since every rank stays castable it is a permanent precision tool, not a stepping stone. Lives in RAZE_TIERS on this page, written in the same shape as ERUPTION_TIERS so the port is a copy. Still open: the fist's width per rank, the damage and the cooldown — and rank III rewriting 24 permanent tiles a cast is the balance number to argue about, not the art.
Grid orientation and anchor 4 wide by 3 tall as written. An even dimension cannot be centred on a tile — that is exactly the bug that crashed every Eruption II. Carry an integer rect (corner + size), never a half-width. The clicked tile is the 2nd of the 4 columns and the middle of the 3 rows, which is what the aim box in section 1 is doing; it is the closest thing to centred that an even number allows. Test the 4-wide dimension by name.
Does the flattening last
SETTLED
scheduleMapSave already writes data/map.json after any tile change, guarded on the world id and not on the flag. loadOrCreateMap only reads it back when GENERATE_NEW_MAP is false. Yes, it should survive. Most of that is already true and free: Raze writes through World.setTileBiome, the save rides along, and production already runs GENERATE_NEW_MAP=false, so a Raze survives a restart there today. A default dev boot regenerates and loses it, which is existing intended behaviour. A rebuilt map comes back clean, and that is intended: once the terrain is completely redrawn there is nothing worth remembering about what Raze cut into the old one, so there is no replay log and none is wanted. Same answer for Terraform and Eruption. The whole question costs this build zero lines; the tooltip just makes the promise Terraform's already makes.
The name
SETTLED
The power was filed as Fist of God and named Raze once the art was done. Nothing in the repo used "raze" before. Raze is the official name. The nodes are Raze I / II / III, and that is what the tree, the hotbar plaque, the armed banner and the cast picker say. "Fist of God" may appear inside the description copy, as the image the power paints, not as the node's name. House style applies to every word of it: no em dashes in player-facing text.
A warning before it lands Eruption warns for five seconds so a creature can run. No warning, and do not add one "for consistency". Eruption is a thing you can walk out of; the Fist is a thing that has already happened. That contrast is the whole reason to have both.

5. The numbers, live

Type in the white cells. Everything else is worked out from them, including what each rank actually kills and the rate at which one god rewrites the map. The block at the bottom is powersConfig.RAZE_LEVELS in the shape ERUPTION_LEVELS already uses, so carrying a tuning pass to the server is a paste.

THE REWRITE RATE IS RULED ON AND RAZE STAYS WHERE IT IS (owner, 2026-09-07). Raze III rewrites 4.0 permanent tiles a minute against Eruption III's 1.8 and Terraform's 1.0, and that was put to the owner as the number to argue about. The answer was to keep Raze and fix the system instead: if the map-rewrite cost becomes the problem, optimise the rewrite, do not slow the power. Recorded here so the next reader does not re-open it as a balance bug.

That had a name and a filed item, and it SHIPPED on 2026-09-09 (commit 7f8fbb0, increment B). Everything from here to the end of this paragraph is the state of play on 2026-09-07 and is kept as the record of why the work was done; the fix landed as specced. maprenderer-patchterrain-re-bakes-the-wh-1: patchTerrain was a full buildTerrainCache(), measured at 144-239ms on a 100×100 map, over the 150ms bar docs/TERRAFORM_PLAN.md set. Its own body says it "stops being affordable the moment something changes tiles OFTEN" — and Raze is now that something. The fix is already specced there (increment B: hoist the bake state, factor _bakeRegion, re-run it over the 3×3 around each changed tile), so this is a known job and not a discovery. Note also that it is not a per-tile cost: twelve tiles in one tilesChanged is ONE re-bake, which is why the single-broadcast rule matters more than the footprint does.

Terraform's 60s is not the benchmark to respect. The owner's position is that Terraform is too slow, warnings and all. So the 1.0 tiles/min in the table below is a floor nobody is defending, and Raze should not be tuned down toward it.

The neighbours, so nothing here is tuned in a vacuum. Reference HP: rabbit 40, deer 80, wolf 80, bear 200.


  

TWO THINGS THIS POWER NEEDS THAT DO NOT EXIST YET, named here so the art review is not the only thing that comes out of this page. server/core/terraform.js is the game's only runtime map write and its transform table has exactly one row today, grass → forest. The Fist needs two more: forest → grass, which is passable to passable and safe, and mountain → grass, which changes passability — but in the freeing direction, turning an impassable tile passable, which frees creatures rather than stranding them. That is the safe direction of a dangerous transform and it wants its own test saying so out loud.