Ideas & systems

How an action runs

Every act of the Maker has a beginning and an end. Between them is a wait, and sometimes a loop.

Still being forged

Parts of this aren't finished yet. What doesn't work yet is listed below.

  • A machine that runs out of what it needs stops, and starts again only while the game is open. While the game is closed nothing resumes. The next time it loads, the game catches up on up to 24 hours of rounds.
  • One way to start an action by itself, when a component is destroyed, is listed but does not work yet.
  • What the player sees when a machine stops depends on how it runs: a repeating run that cannot pay for its next round says so by name ("<name> stopped: not enough inputs to keep running. It starts again by itself when they are back."); otherwise the player sees the warning that names what is missing (the Mill's Grind shows this one).

What it is

An action does not just happen. When a player taps it, the game runs it in two parts: a start and a finish. Between the two, a timed action waits. This page follows one run from tap to reward, and then shows how a machine can run again and again by itself.

How it works

  1. The start. The game checks everything the action needs: costs, skills, research, tools and stats. It checks all of them before it takes anything. If one is missing, the player is told, and nothing is lost.
  2. The cost is taken. Only the costs marked used up are taken, and only now.
  3. The wait. A timed action waits for its duration. The player sees a progress bar and nothing else. An action with a duration of 0 skips the wait.
  4. The finish. The action gives what it gives, converts what it converts, changes the stats it changes and passes on its events. With Auto Award on, this happens by itself. Without it, the player taps Collect! on a Structure that makes things, or Activate! on anything else.
  5. After. A cooldown, if the action has one, keeps the player from starting it again for a while.

Running again by itself

An action with Auto Exec on ("Start the next round by itself when it can") starts its next round the moment a round finishes. The first round is still a tap. Nothing starts when the thing is merely placed.

If the next round cannot be paid for, the action stops. It starts again by itself once the game is open and the player has what it needs. A player who taps it first just starts it.

To stop a running action, tap it and answer the question "A process is currently active. Do you want to cancel it and proceed?" A stopped run never restarts by itself.

In Vespera

In Vespera: nails and flour Play it

A single run. The Tinker's Bench has the action Make nails, which takes 10 seconds. At the start it uses up 1 Scrap Iron from the place. After the wait it gives 2 Iron Nails into the place, and adds 1 XP to the player. Auto Award is on, so the nails arrive without another tap.

A loop. The Mill's Grind takes 15 seconds, and Auto Exec and Auto Award are both on. The player taps it once. It needs at least 2 Wheat Sheaf in the bag. Each round converts half of the bag's wheat into Flour and adds 20 XP to the Fields. A bag of 12 ran three rounds, one after another, with no further taps.

The pause. After round 3 the bag held 1 Wheat Sheaf, which is under the 2 the Mill needs. The Mill stopped. The game showed a Warning dialog that said the Wheat Sheaf quantity must be at least 2 in the inventory. When the player picked up more Wheat Sheaf from the Fields, the Mill started a new round by itself, with no tap on it.

Good to know

  • Real time or turns. In a turn-based game the action waits for turns, not seconds.
  • A loop needs a way to stop. A machine that can always pay for the next round never stops. Give it a cost that runs out.
  • The stop is not a failure. The machine did nothing wrong. It waited for stock.
Under the hood
  • The game reads one duration for each game mode: seconds in a real-time game, turns in a turn-based one. The other never delays anything.
  • An action with a duration of 0 starts and finishes at once.
  • Auto Award is read only when a timed action finishes. An action that runs at once pays out at once whatever it says.
  • Auto Exec works only with Auto Award on and a duration above 0. The window refuses to save it otherwise.
  • A cooldown starts when an action finishes. It is kept per target, and the server and the game both enforce it. A restart of the server clears the server's copy.
  • A player who stops an action by hand cancels it. A cancelled run never comes back by itself.
  • When the game loads it catches up: it pays the rounds that would have run, as many as the player could afford, with the time capped at 24 hours.
  • When several machines share one scarce item, which runs first is not specified.
  • A system trigger starts an action when a component is earned. It hides the action's button from the player.