Skip to main content
⌖ OF Intel

GUIDES

Cape of Good Hope Map: The 26-Nation Board, the Single Chokepoint, and Where to Spawn

A decision framework for Cape of Good Hope, the v0.35 African tip map. What the 26-nation, 36-overflow-name, 1,807,478-land-tile board actually looks like, why the single chokepoint and the large bay decide the match, how the land-driven lobby sizing rolls a 90-player lobby (one tier below Horn of Africa), and which side of the bay to commit to before the countdown ends.

Guide Difficulty · Advanced Published Nov 2, 2026 Updated Nov 2, 2026 Reviewed by OpenFront Intel editors #maps#v0.35#cape-of-good-hope#spawn#chokepoint#bay#nations#lobby-size

Direct answer. Cape of Good Hope is a v0.35 board with 26 spawn nations on 1,807,478 land tiles and a rotation frequency of 4, so under the new land-driven lobby sizing it rolls a 90-player large lobby (70 medium, 45 small) in FFA — one full tier below Horn of Africa’s 100. The match is decided by a single chokepoint where the Cape Peninsula narrows, with a large bay wrapping the headland and historical South African flags across the coast. Commit to one named anchor nation on the side of the bay you intend to hold, take its two land neighbours early, and secure the chokepoint before an opponent can contest it; treat the inland plateau nations as depth and the bay nations as trade-ship access rather than as separate fronts. Read the lobby tier first, because a 90-player bay board is a different game from a compact private one, and the chokepoint is the one position both sides reach for from the first minute.

Cape of Good Hope is the v0.35 map that puts a single named chokepoint and a large enclosed bay at the center of a land-heavy African tip. The board is 1928 by 1928 tiles with 1,807,478 of them land, which sits one tier below the 2,024,462-tile Horn of Africa and triggers the 90-player large lobby under the v0.35 land-driven sizing formula. The map is the southern tip of the Cape Peninsula: a headland that the Atlantic and the Indian Ocean pass on either side, with a broad bay wrapping around the land and a single narrow crossing where the peninsula pinches. The official v0.35.0 release describes it in one line as a large bay with one chokepoint, plus historical South African flags, added by RickD004. Because the land is wide but the crossing is narrow, the game is not about sprawling across the whole board; it is about choosing which side of the bay you belong to, anchoring on a named nation there, and deciding when to push the single crossing. This guide gives you a repeatable framework for the four decisions the map forces: which lobby tier you are dropped into, which side of the bay to commit to, which named nation to anchor on, and how to play the bay against the plateau interior rather than as a separate front.

Version boundary: what v0.35’s Cape of Good Hope actually is

The single most important thing to pin down before you plan a spawn is that Cape of Good Hope is a v0.35 map and it carries the two v0.35 behaviours that reshape every board it appears on. It shipped in the v0.35.0 formal release on October 16, 2026, and the OpenFront wiki’s Cape of Good Hope entry describes it in one line as a large bay with one chokepoint, plus historical South African flags, added by RickD004. The map carries the official new rotation category and a multiplayer_frequency of 4, which the v0.35.2 overview places below the frequency-5 regional maps like Horn of Africa, Madagascar and Bab el-Mandeb, and above the low-frequency draws like Canary Islands and Pulicat Lake. That frequency of 4 is what you should internalize: it is a real public draw you can expect to land on without forcing it, but it is the rarer of the two new African regional draws, so you should arrive with a plan instead of improvising, and you should not queue for a specific Cape game expecting it to fill a slot every time.

The second v0.35 behaviour on the board is the land-driven lobby sizing, which replaced the flat player cap. Cape of Good Hope sits below Horn of Africa in the land tier, with 1,807,478 land tiles on a 1928 by 1928 grid, and the formula reads the land tile count to set the lobby tier, so the map rolls a 90-player large lobby in FFA, 70 in a medium setting, and 45 in a small setting. That tier is not a detail: it changes how many named nations are competing for the chokepoint at once, and it means the chokepoint is usually contested from more than one direction before the match is a few minutes old, even though the board is smaller than Horn of Africa. The third thing to note is the nation layer. The manifest lists 26 spawn nations and 36 overflow names, and it includes Cape Town, Simon’s Town, Hout Bay, Cape Point, Robben Island and Seal Island as named positions, which is why the board renders with a dense cluster of colored coastal regions around the bay. When you read the board, the 26 nations are the playable anchors and the extra colored regions are overflow names on the same land, not new opponents. The current stable line is v0.35.9, and the manifest for Cape of Good Hope is unchanged from v0.35.0 through that cursor, so the description in this guide is current as of that cursor. If you are playing on a version before v0.35.0, this map does not exist yet, and the lobby sizing and spawn-recovery rules described here do not apply to the older flat-cap boards.

Decision framework: read the tier, the side, the anchor, the chokepoint

The framework is a four-step read you run before the countdown ends and then re-check at the ten-minute mark. The first step is the tier, and the read is to confirm you are in the 90-player large lobby, the 70-player medium, or the 45-player small, because the number of nations reaching for the chokepoint changes how fast you must secure it. In the large lobby the chokepoint will be contested from several directions and you should assume you will not hold it alone, so your goal is to be the first nation across or to force the contest onto your chosen side of the bay. In the small lobby the chokepoint is a two-or-three-nation fight and holding it outright is realistic if you anchor early. The second step is the side, and the read is to decide whether you belong to the Atlantic-side land mass or the Indian-Ocean-side land mass of the bay, because the water sits between them and crossing to the other side later is a full naval commitment that most openings cannot afford. The third step is the anchor, and the read is to pick one named nation on your chosen side that has a deep land connection to at least one neighbour and a sea exit, because that combination lets you defend on land while the coast still feeds your trade ships, and because anchoring on a coastal nation with no plateau depth behind it is the single most common way the opening is lost on this board.

The fourth step is the chokepoint, and the read is to time when to push the single narrow crossing. The crossing is narrow enough that a small committed force with a transport line can hold it, but it is also the one position both sides want, so pushing it from a single coastal spawn with no plateau support behind you is how you lose the position you were reaching for. The rule is to push the chokepoint only after your anchor and one neighbour are stable, so the chokepoint has a defended line of communication behind it. To make the four steps concrete, here is the board read for the two halves of the bay:

ReadAtlantic-side land massIndian-Ocean-side land mass
Sea accessLong bay coast, short trade-ship hops to the chokepointBay coast plus the headland’s outer Atlantic coast
Land depthWide plateau interior feeding the inland nationsFragmented coastal strip between the bay and the outer sea
Chokepoint reachReaches the single crossing from the open bayReaches the single crossing from the headland side
Typical anchorA named coastal nation with an inland plateau neighbourA named nation that links the bay coast to the plateau interior
Main riskOver-extending toward the chokepoint from a thin coastThe fragmented coastal strip splits your neighbours into rival flags

That table is the whole decision in one glance. You pick the side that matches your plan, pick the anchor that the table says is a safe named nation on that side, and then the chokepoint becomes a scheduled push instead of a scramble. The framework holds in team mode too, where the read is the same except the side question becomes which half of the team owns the chokepoint and which half owns the plateau interior, and the anchor question becomes which team member owns which named nation so the chokepoint has a named owner.

Scenario A: 90-player FFA, commit to the chokepoint early

This is the primary scenario, because OFstats shows the map is played mostly FFA at mid-to-large lobby sizes, with the 90-player large tier as the common public draw and a live lobby advertised at the high-twenties-to-low-eighties slot. You spawn into the Indian-Ocean side of the bay, on a named nation that links the bay coast to the plateau interior, so you have both trade-ship access and land depth. Your opening is to take your anchor, then take the one inland neighbour that gives you the plateau line, before you spend anything on the coast. The reason is that the plateau is where the inland nations sit, and those inland flags are the most contested land on the map because they are the depth behind every coastal nation. By the time the first transport lines are heading for the chokepoint, you should have your anchor, your inland neighbour, and a trade-ship line already established, so the chokepoint push has a defended supply line behind it.

The number that makes this scenario a decision instead of a guess is the chokepoint timing. In a 90-player board the chokepoint is usually first touched around the five to seven minute mark, and the nation that arrives there with a defended line of communication holds it, while the nation that arrives as a single coastal probe is pushed back. So the play is to have your anchor and neighbour stable by minute four, to launch your first chokepoint probe at minute five with a transport line behind it, and to be willing to hold the probe as a forward base rather than a permanent position if the contest is too hot. The failure to watch for is over-extending: if you push the chokepoint and then your inland neighbour is grabbed by a third party, your chokepoint base becomes an island with no supply, and it will be cut off. The counter is to keep one inland nation as your reserve, so the chokepoint always has a second line of communication, and the reserve is what lets you fall back from the forward base without losing the position entirely, which is the difference between a temporary setback and a lost front. When the chokepoint is held, the payoff is that every trade ship crossing the bay between the two land masses is now under your control, and that is the income advantage that wins the large-lobby match, because the board is wide enough that no one holds the whole thing and the chokepoint is the one place where the bay and the land meet.

Scenario B: 45-player small lobby, hold the chokepoint outright

This is the secondary scenario, a compact board where the chokepoint is a two-or-three-nation fight and holding it outright is realistic. You spawn into the Atlantic side of the bay, on a named coastal nation whose inland neighbour points toward the plateau interior rather than toward the fragmented Indian-Ocean coastal flags. Your opening is the same shape but at a smaller scale: take the anchor, take the inland neighbour, establish the trade-ship line, and because there are fewer nations, you can afford to commit more of your force to the chokepoint from the start. The difference from the large lobby is that in the small lobby you do not have to settle for a forward base; you can put enough force through the crossing to actually hold it and deny the opposing side of the bay the crossing.

The decision here is how much force to commit. In the small lobby the chokepoint is worth a real standing force because it is the one position that controls the bay axis and the board is small enough that holding it is sustainable. The number to watch is the size of the opposing force that reaches the chokepoint: if it is a single nation, you hold with a small force and keep the rest in reserve for the plateau, and if it is two nations, you hold with a larger force and you should be prepared to fall back to the forward-base posture from the large-lobby scenario if the contest gets too heavy. The failure to watch for is the opposite of the large-lobby failure: in the small lobby the risk is not over-extending, it is under-committing, because if you hold the chokepoint with a token force and the opposing two nations combine, they break your position and take the crossing you were supposed to own. The counter is to commit enough to the chokepoint to deny the crossing even if you lose the position, so that even a failed hold leaves the opposing side paying a real cost for the crossing. When you hold the chokepoint in the small lobby, the payoff is even more direct than in the large lobby, because the board is small enough that the chokepoint controls a larger share of the total trade traffic, and the income advantage from that share is enough to out-build the nations that did not contest it, so the single most important early decision in the small lobby is committing enough to the chokepoint to make the crossing costly for anyone who tries to take it.

Failure modes and counterplay

The first failure is committing to the chokepoint before your anchor and neighbour are stable, and it happens because the chokepoint is the most obvious high-value position on the board, so players reach for it early and arrive without a line of communication behind them. The counterplay for the opponent is to hold the inland neighbour you were trying to use as your supply line, so your chokepoint base has no second line and gets cut off, and the read for you is to not push the chokepoint until the anchor and one neighbour are both in hand, which is what the framework’s fourth step enforces. The second failure is anchoring on a coastal nation with no plateau depth, and it happens because the coast is the attractive side of the map and the trade-ship access is visible, but the plateau is where the real land depth is, and a coastal anchor with no depth gets out-flanked from the plateau interior. The counterplay for the opponent is to take the inland nation that your coast depends on and turn your coast into a position that can be denied, and the read for you is to anchor on a nation that the table says links the coast to the plateau, not on a pure coastal nation.

The third failure is treating the fragmented coastal strip as one opponent when it is several flags, and it happens because the Indian-Ocean side renders as a string of small coastal nations, so a player reads the strip as a single block when it is actually a set of rival flags that can be split. The counterplay for the opponent is to grab one of the coastal flags adjacent to your anchor and turn it into a hostile neighbour, so the strip you were relying on as a front becomes a second front you have to defend. The read for you is to know that the 26 named nations are playable anchors and the 36 overflow names are extra pool positions on the same land, and that the flags adjacent to your anchor are the ones you either take early or have to watch, and the read for the chokepoint is that the inland contest is what decides whether your chokepoint has a supply line behind it. The fourth failure is the small-lobby under-commitment, and the counterplay is the combined force from the opposing nations, so the read is to commit enough to the chokepoint to deny the crossing even in a failed hold. The meta-counterplay that wins the match in both scenarios is the same: be the nation that owns the chokepoint with a defended supply line, because the board is wide enough that no one holds the whole thing and the chokepoint is the one position where the bay and the land meet, so whoever holds it with depth behind it controls the income axis that the rest of the match is played over.

Reading the spawn nations and the overflow names

The spawn table is the part of the board most players misread on this map, so it is worth stating plainly. The manifest lists 26 spawn nations and 36 overflow names, and the 36 overflow names exist because the game pads the spawn pool past the visible nation count so that late joiners and re-rolls have a named place to land. That means when you open the map you will see more colored regions than there are spawn nations, and the extra regions are not additional nations but the same land rendered once more for the overflow pool. The two places this matters most are the dense bay cluster and the headland, where the manifest names Cape Town, Simon’s Town, Hout Bay, Cape Point, Robben Island and Seal Island as distinct positions: the tip of the peninsula is not one solid block but a set of small named flag positions sitting on top of a few nations’ land, and Robben Island and Seal Island are the offshore positions that decide whether a player has a second sea exit or is trapped on the headland.

The read this gives you has three parts. First, the tip looks more contested than it is in the spawn sense, because the named headland flags are all on the same few nations’ land, so a fight that looks like a five-way scramble over the headland can actually be a two-nation contest with a lot of coastal texture. The counter you should make is to treat the tip as a two-front problem, one front against the plateau interior and one against the bay coast, and to pick the front that your anchor can actually reach. Second, the named positions are the positions that decide supply, because a chokepoint base is only as strong as the flag behind it, and if the flag behind your chokepoint is one of the small headland positions rather than a deep plateau nation, your chokepoint has thin depth and the opponent can deny it by holding the next flag in. Third, the overflow pool is a timing tool, because the 36 overflow names come up in a defined order as the lobby fills, so a player who reads the table knows which headland flags will be taken early and which stay open late, and the read for the opening is to take the flag that both links your anchor to the chokepoint and leaves at least one open flag behind you as a fallback, rather than grabbing the most central headland flag and finding that every flag behind you is already hostile.

The concrete version of this is to pick your anchor from a nation that the table shows linking the coast to the plateau, take one headland flag that keeps your chokepoint supply line open, and leave a second headland flag open as the fallback position you can reach if the first front collapses. Do that and the headland stops being a wall of colors you have to improvise against and becomes two fronts you can read by name, which is the difference between a board you are guessing at and a board you are playing on a plan. The historical South African flags are a readability aid, not a gameplay signal: they tell you which named nation owns which piece of coast, so you can read the board by name before the countdown ends, which is the whole point of anchoring on a named nation instead of a shape.

Mode and map adjustments

In team mode the read is the same four steps with two substitutions. The tier read changes because team mode scales the lobby up, so the chokepoint is contested by two teams instead of a loose set of nations, and the read is to assign the chokepoint to the team half with the stronger sea force and the plateau interior to the other half, because the chokepoint needs a naval owner and the interior needs a land owner. The side read changes because the side question becomes which team owns which half of the bay, and the read is to pick the side that gives your team the named anchor it needs, which is usually the half with the deeper plateau, because the fragmented Indian-Ocean coastal flags make that half the one that needs more coordination and the Atlantic half the one that is easier to hold. The anchor read is unchanged in shape, but the anchor becomes a team member’s named nation instead of a single player’s, and the read is to make sure the chokepoint has a named owner on each team so the contest has a clear front instead of a scramble.

The chokepoint read in team mode is the timing of when the two teams commit to the single crossing, and because there are two owners instead of a loose set, the crossing tends to become a defined front line that holds for the middle of the match, and the read is to treat that front line as the match’s main axis and to build the economy around holding it. On the map axis, the adjustment is that the chokepoint is the same physical crossing in every setting, but the bay matters more in the larger lobbies, because the broad bay gives the Atlantic half a second water route that the larger boards use to bypass the chokepoint, and the read is that if you hold the chokepoint but the opposing side builds the bay route, your chokepoint hold is partially bypassed, so the chokepoint and the bay are the two sea positions to watch, not just the chokepoint. The mode and map adjustments boil down to one line: in team mode assign the chokepoint to the naval half and the plateau interior to the land half, and on the map axis watch both the chokepoint and the bay, because the board is wide enough that holding one sea position while the other is open is how you lose the income axis.

What this guide is and the systems it feeds

This guide is the single main answer for the Cape of Good Hope board, and it answers the question of where to commit before the countdown ends on a v0.35 land-heavy map with a single chokepoint. The version boundary is that it describes the board as of the v0.35.0 release and the current v0.35.9 cursor, where the manifest is unchanged, so the 26 nations, 36 overflow names, 1,807,478 land tiles, 1928 by 1928 grid, and frequency 4 are all current. The decision framework is the four-step read of tier, side, anchor, and chokepoint, and the two scenarios are the 90-player FFA that pushes the chokepoint early with a defended supply line and the 45-player small lobby that holds the chokepoint outright. The failure modes are the four ways the match is lost, the chokepoint push before the anchor is stable, the coastal anchor with no depth, the fragmented strip read as one opponent, and the small-lobby under-commitment, and the counterplay is the one way the opponent wins, holding the supply line behind your chokepoint. The mode and map adjustments are the last piece, which is that team mode assigns the chokepoint to the naval half and the map axis watches both the chokepoint and the bay.

For the broader systems this opening feeds into, the lobby-size map-driven guide covers the land formula and the tier table that this guide applies to Cape of Good Hope, the v0.35 new maps overview covers the full set of v0.35 additions including the other African regional maps, the map strategy guide covers connected land and water networks on any board, which is exactly the bay-and-chokepoint system on this map, and the naval stalemate and blockade guide covers how to hold a crossing when the enemy is trying to deny it, which is the chokepoint fight in both scenarios. Bring those into the same decision and the Cape of Good Hope opening stops being a guess about which side of the bay looks central and becomes a plan about which side, which anchor, which chokepoint timing, and which bay route you are committing to before the countdown ends, which is the only time the whole thing is still in your hands. The board is wide enough that a wrong side is recoverable for a short while, but the chokepoint makes the correction a crossing, and crossings cost time and a unit that you may not be able to afford if you have already burned your early game on a bad start, which is why the players who win on this map are usually the ones who read the tier and the side carefully and committed to a named anchor with a named chokepoint timing and a named bay route, rather than the ones who picked the familiar side by instinct and then had to improvise the crossing.

Related content

Continue reading
Adaptive Build Order: Spend the Next Gold on the Constraint

Use OpenFront v34.3 costs, troop growth, route payback, and stop signals to choose City, Port, Factory, defense, or a liquid reserve without copying a fixed script.