No. 2 ·

The rules on one page: islands, troops, capture

Inkisle's whole rule set on one page: how islands produce troops, how fleets fly, how capture is calculated, and how a match ends. Starting values, before testing.

Islands with troop numbers and dotted routes where fleets travel between them.

Good strategy games can be explained in a minute. This is our attempt at Inkisle's rules, on one page. Every number here is a starting value from the design document. We expect to change some of them after testing.

Islands make troops

The numbers below are for the normal island. There are four kinds of island in all, and the starting values of the other three are: a small island makes 1 troop every 1.6 seconds with a cap of 25; a big island makes 1 troop every 0.6 seconds with a cap of 80; a fortress makes 1 troop every 2 seconds with a cap of 60 and a defense multiplier of 1.5.

Sending fleets

Drag from one of your islands to another island and let go. A bar at the bottom picks the share: 25, 50, 75 or 100%. You send the floor of troops times the share, at least 1. At 100% you send "all minus one", so the island never becomes empty and stays yours.

A fleet flies in a straight line at 2.5 map units per second. A neighboring island 4 to 8 units away takes about 1.6 to 3.2 seconds, and crossing the whole map takes about 11 seconds. Fleets do not fight on the sea; they pass each other. That keeps the arrival preview honest, and the genre's tension remains: a long trip is a risk, because the target keeps growing while you travel.

Capture, calculated at arrival

Two examples. A fleet of 18 arrives at a fortress of 10. The requirement is ceil(10 × 1.5) = 15, so you capture it with 3 left. A fleet of 12 arriving at the same fortress leaves it with 2.

If several fleets arrive in the same tick, they resolve one by one in the order they left.

How a match ends

One engine for real time and turns

The game state depends only on the starting map, a seed and a list of commands, with no clock and no randomness inside the engine. The same input gives the same result on every device. That is what lets the same engine run in real time now and in networked turns later, and it makes replays and bug reports a matter of saving a command list.

← All journal posts