Golden HarbourGames

Harbour log

Vladivostok Fortress ·

Vladivostok Fortress is being rebuilt as a battle

We have reopened Vladivostok Fortress as an action strategy game about a landing that never happened. The first alpha looked fine and nobody knew what to do in it. What we kept from the old game, and what the second alpha does differently.

Vladivostok Fortress is our slowest game: a narrative strategy about an engineer officer who lands in 1899 and builds a fortress with money he does not control. It is still there and still playable. But this week we reopened the fortress as a different kind of game, and since we build in the open, here it is, early and unfinished. There is nothing to play yet.

A landing that never happened

The real fortress was shelled once from the sea, in 1904, and never stormed. The working title of the new game is The Landing, and its question is what would have happened in 1905 if someone had tried. You command the whole fortress, on one board, for the length of a siege.

Nothing of the research was thrown away. The old game left us the real works, the real relief of the hills, the maps and the officers. The new board is built from actual height data of the peninsula and of Russky Island.

The sea approaches in the second alpha: a fort and a coast battery, landing boats coming in under a cruiser’s guns, a torpedo boat going out
The sea approaches in the second alpha: a fort and a coast battery, landing boats coming in under a cruiser’s guns, a torpedo boat going out

The look came from one picture

Our first idea was a flat staff map: contour lines, pencil arrows, the way an officer would have seen it. It was dropped the moment a better picture turned up: a painted relief model seen from above. Sculpted green hills with soft shadows, pale concrete forts on the hilltops, turquoise shallows going to deep teal, ships with long wakes. "I like this style." That is the look now.

The first alpha: "unclear"

The first design split the fortress into small sector battles. It was rejected in a sentence: "It was designed to be one big thing." So the second draft is one board for the whole fortress, and a day that is replayed from its morning if you lose it.

The first alpha gave every work a card with three postures: shelter, fight, sortie. The enemy bombards, storms or saps, and you answer. On paper that is a clean game of rock, paper, scissors. In the hand it was this: the works sat in shelter, nothing fired, and the player did not know what he was supposed to do. His verdict was "looks not bad" and, about the rest, "unclear", with a stronger word attached.

We asked what his hands should be doing in a game like this: shoot, build, move forces or give orders. He picked all four.

The whole board: the peninsula and all of Russky Island, with the reach of one battery drawn on the water
The whole board: the peninsula and all of Russky Island, with the reach of one battery drawn on the water

The second alpha: hands on the map

So the cards are gone, and the second alpha, built the same day, puts everything on the map.

  • Select a fort or a battery and right-click a ship: it fires.
  • Spend supplies to place a field battery, mines, wire or a trench where you think the boats will come in.
  • Move battalions, Cossacks and torpedo boats.
  • Tell a work to hold fire, fire at will or take cover.
  • The first day is guided: nine steps, with a pointer on the map, so that nobody sits wondering why nothing shoots.
The peninsula from higher up
The peninsula from higher up

Shells, men and time are the three things you never have enough of. That part of the design has survived both alphas.

What is not decided

Most of it. The second alpha has not had its verdict yet. The pictures on this page are from a test scene, not from a finished battle. It may change shape again, and if it does we will say so here. If you know the fortress, or you just like games where a coast battery matters, write to us: contact@goldenharbourgames.com.

Play Vladivostok Fortress

Devlogs

Far East hackathon, day 2: the day of "no" Forty-two hours into the 72-hour Far East hackathon. Both games changed more on day two than on day one, and almost all of it began with the human saying no: to the interface, to the roubles he asked for yesterday, to boarding drawn as three bars. More clips and a new film. Read the devlog Far East hackathon, day 1: one human, one machine, two games We are in the Far East game hackathon run by FEFU in Vladivostok: 72 hours, the history and culture of the Far East. We are building two games at once, a pirate sandbox on the Sea of Japan in 1220 and a tycoon about the Green Corner car market in 1992. This is how a person and an AI actually split the work on day one, with pictures, clips, and the parts that went wrong. Read the devlog Orbital Jump Reloaded: a 2021 game, taken apart and put back together Orbital Jump came to us as the source code of a 2021 phone game. Eight days later its rebuild was on Google Play and the App Store. What broke on the way, what had been switched off for five years, and what we would do differently. Read the devlog