Ledger v3 · C# · Godot 4.7 Get started
The cookbook

43 recipes and 22 concept pairs.

Copy the recipe nearest what you want into your game's content, then change its numbers and names, and its play with them.

Look here for a mechanic before forms.md. Each recipe in mechanics\ is a .ledger and its .play, lifted from one of the six game slices' committed content and cut to the one mechanic: it loads alone, its first comment names the slice and the file it came from, and its play's numbers are worked out from its content, each with its source. Every play passes in the kernel's gate. Four recipes came another way: the shield gate and the layer's rate (gate and rate) hold what no slice holds, from the owner's ask for the online shooter's layers, the party's fallen (fallen) from the raid's two witnesses in ledger-lab\raid\, and a caster's cast time (casting) from four more of them; the first comment of each names where it came from. ledger pipeline on any recipe shows its layers in the order a hit meets them.

The slices are the six games in ledger-lab\: the action RPG (arpg), tower defense (td), tactics, the card game (cards), the RTS (rts) and the shooter.

The backbonethe default way to write a build's affixes

Action RPG11 recipes

Tower defence9 recipes

Shooter6 recipes

Tactics5 recipes

RTS5 recipes

Raid4 recipes

Cards3 recipes

Concept pairsported from v2's cookbook

Left out, and why

A slice's way round a form the language lacks isn't the way, so it isn't here; nor is a rule a slice keeps in C#.

  • A drop on a death (ARPG, content\slice2.ledger, Drops): its loot belongs to no side by team = holder.team.team, since a create can't say no link (the slice's friction row 32).
  • The frost tower's slow, strongest holding (TD, content\towers.ledger): a helper stat Slow, since strongest keeps the largest term (row 4).
  • The frost tower's and the TD banner's auras (TD, content\towers.ledger): their reach written as a number beside a Reach stat, since an aura's reach that reads a value is refused (row 8).
  • A training queue (RTS, content\economy.ledger, Training): its next ticket found except holder (row 6).
  • The storm (RTS, content\seer.ledger): once a beat for each unit by a short-lived mark (row 7).
  • The siege's change of mode (RTS, content\siege.ledger): two effects at once, one applying the next at its end (row 11).
  • Secrets (cards, content\secrets.ledger): named twice, by tag and in a table, for the host to hide (row 6).
  • Kept in C#, so no recipe has them: the cleave's knockback (the game's space moves what the content requests), the waves' lists of foes (TD and the shooter), whose turn it is and the walks on the grid (tactics, cards), the fog and sight the spaces answer as facts (tactics, RTS), the units' standing orders (RTS), and the bearer's shield ended with its bearer (shooter).