GUIDES
Rio de Janeiro Map: The 30-Nation Board, the 75-Player Lobby, and Where to Spawn
A decision framework for Rio de Janeiro, the new v0.35 map. What the 30-nation, all-Brazilian board looks like, what the land-driven lobby formula does to its 75-player size, how the 2-team west/east split and the Guanabara Bay river fix change where you expand, and which side of the map to commit to before the countdown ends.
Rio de Janeiro is the new v0.35 map that gives every lobby a single all-Brazilian nation set of 30 real neighbourhood names, and it plays at a 75-player base because its 1,491,794 land tiles round the formula to a 75 base. In two-team mode the 1.5× team multiplier is capped at that 75 limit, so teams run 75/75/60 by tier rather than a bigger board, and compact mode thins every figure to a quarter (18/13/10 FFA, 18/18/15 teams). The spawn layer is a hard west/east split at x=744 on the 1488-wide map, with the bay islands sitting between the halves, and a v0.35.5 river fix now drains the west-side rivers into Guanabara Bay instead of dead tiles. The decisions that matter are: which mode you queue (FFA density versus team side-selection), which half you spawn into, and whether a compact board suits your map. Pick your side before the countdown ends and you keep the bay-pivot choices that the other side loses.
Version boundary: what the v0.35 Rio de Janeiro map actually is
Rio de Janeiro is a new map that ships in the v0.35 series, and the version boundary is the first thing to pin because it decides which facts are real and which are carried over from an older patch. The map is absent at tag v0.34.25, the last release of the previous series, and it is present at v0.35.0, the first release of the new series, where its manifest already carries 1,498,664 land tiles. By v0.35.9, the latest formal release, the count has settled at 1,491,794 land tiles on a 1488-by-1680 canvas, which is a 0.5% adjustment to the coastline between the beta and the final tag. The v0.35.9 release body lists it explicitly under “New maps” with the line “Rio de Janeiro: Guanabara Bay, 30 nations from Rio’s neighbourhoods and municipalities,” which is the first-hand statement that this is a v0.35 addition and not a rename or a port of an older map. That sentence also carries two other facts that the rest of this guide leans on: the map has a 2-team spawn layout, and the historical v0.35.5 entry records the river fix for rivers that were “cut off from the ocean.”
Every number in this guide is taken from the v0.35.9 tag source, not from the beta or from community recollection. The manifest at that tag reports 1,491,794 land tiles out of a 2,500,160-tile canvas, which is a 59.7% land fraction — denser than a pure ocean map and close to a full land map, which is exactly what a city-and-bay map should be. The same manifest reports 30 nations, every one of them carrying the Brazilian flag, so there are no unflagged overflow names the way a sparse map would have; the entire board is a named civic layer. The map also ships three pre-baked resolutions (full 1488-by-1680, a 4x map at 744-by-840 with 368,670 land tiles, and a 16x map at 372-by-420 with 90,245 land tiles), and the 4x resolution is the one that matters for the 2-team layout because it is exactly half the width of the full map, which is how the game splits the board down the middle. The map is tagged with the “new” category and the “south_america” theme, and its in-game translation key is map.riodejaneiro, so the name you see in the lobby list is the one that resolves to this manifest.
The practical consequence of pinning to v0.35.9 is that any guide or video that quotes a Rio lobby from the v0.35 betas may be off by a tile-count or a formula change, and the only safe statement is the one that comes from the final tag. This guide does not carry over any Rio-specific number from an earlier build, and the version boundary is the reason the lobby table below uses the v0.35.9 formula exactly as it is written in the tag source. If a future v0.35.x patch moves the land count or the formula, the numbers in this guide will need to be re-derived, and the version line in this frontmatter is the marker that tells you which build they were derived from. Until then, the v0.35.9 tag is the reference, and every claim in the body below is traceable to the manifest, the lobby formula, or the release body at that tag. This is the same version-pinning discipline the other v0.35 map guides use, and it is the reason the next section can state the lobby size as a hard number rather than a range.
The lobby size the land formula hands you
The single most important number on this map is the lobby size, because it decides how many players you actually face and how dense the nation layer is. The live formula in the v0.35.9 tag source, in the file that handles the multiplayer playlist, derives a base player count from the land-tile count with the expression “max of (the land tiles divided by one million times fifty), rounded to the nearest five, floored at five.” For Rio’s 1,491,794 land tiles, that expression evaluates to a base of 75, because one million times the ratio is 74.59 and rounding to the nearest five gives 75. That base of 75 is the large-FFA number, and it is the ceiling for every other figure on this map, which is the first thing to understand before you look at the rest of the table.
From that base, the game builds three rolled tiers: the large tier is the base itself at 75, the medium tier is the base times 0.75 rounded to the nearest five, which is 55, and the small tier is the base times 0.5 rounded to the nearest five, which is 40. The roll is 30 percent toward large, 30 percent toward medium, and 40 percent toward small, so a small board is the most common lobby you will actually land in. Free-for-all mode uses the rolled tier directly, which gives you the 75, 55, and 40 figures. Two-team mode is where the cap matters: the formula multiplies the base by 1.5 and rounds up, but then clips that result at the large-FFA tier. So a 75 base gives a team figure of min(ceil(112.5), 75), which is 75, and the 55 and 40 small tiers give min(ceil(82.5), 75) and min(ceil(60), 75), which are 75 and 60. That is the counterintuitive result: on this map, two-team mode does not produce a bigger board than free-for-all, it produces a board capped at the same 75. Compact mode then shrinks each figure to a quarter, floored at a minimum of three players, which gives 18, 13, and 10 in FFA and 18, 18, and 15 in teams.
| Rio de Janeiro | Large (30%) | Medium (30%) | Small (40%) |
|---|---|---|---|
| FFA | 75 | 55 | 40 |
| 2-Team | 75 | 75 | 60 |
| Compact FFA | 18 | 13 | 10 |
| Compact 2-Team | 18 | 18 | 15 |
The reason the cap clips the 1.5× multiplier is that the multiplier is applied to the base and then compared against the large-FFA tier, and on a map whose base is already 75, the multiplier’s result (112) is always above the 75 ceiling. On a smaller map the multiplier would not be clipped, but on Rio it is, which means the team-mode board is bounded by the same 75 that bounds the FFA board. This is the single most-misquoted number on the map, and it is the reason a guide that tells you “team mode gives you 150 players on Rio” is wrong for this map. The full derivation, with the formula written out and the rounding rules explained, lives in the lobby-size guide, which is the reference for how the land-tile count becomes a player count across every map in the game. The table above is the Rio-specific instance of that derivation, pinned to the v0.35.9 tag, and it is the number set that every scenario in this guide is built on. If you want to understand why a 75-player board is the right size for a 30-nation map, the map-strategy guide covers the general density logic, and the compact-mode guide covers how the quarter-shrink works and when you should deliberately queue a compact board instead of a full one.
The nation layer: 30 Brazilian names with no overflow pool
The nation layer on Rio is the reason the map feels different from a generic flag-pool map: every one of the 30 spawn names is a real Rio neighbourhood or municipality, and every one of them carries the Brazilian flag, so the map presents a single national identity that the players themselves subdivide. There is no overflow pool of unflagged names, no generic “Nation 17” slot, and no mixed-flag board. The 30 names are Copacabana, Ipanema, Leblon, Flamengo, Méier, Tijuca, Niterói, São Gonçalo, Magé, Itaboraí, Maricá, and the rest of the municipal list, plus the three bay islands Ilha do Fundão, Ilha do Governador, and Paquetá. The consequence of a 30-name, all-Brazilian board is that the nation layer is a civic mosaic rather than a military one, and the strategic question is not “which nation is stronger” but “which of these 30 names do I take and which do I leave for someone else.”
The 30 names split across the two spawn halves in a way that matters for side selection. Using the nation coordinates from the manifest and the 744-pixel split line, 16 names sit on the west half and 11 on the east half, and the three bay islands (Ilha do Fundão and Ilha do Governador in the west, Paquetá in the east) straddle the line close enough to the middle to act as the pivot between the two team zones. The west half is the dense city-and-beach corridor: the downtown names (Glória, Flamengo, Méier, São Cristóvão, Penha) cluster in the centre, the beach strip (Copacabana, Ipanema, Leblon, São Conrado) runs along the bottom edge, the two bay islands (Ilha do Fundão, Ilha do Governador) sit in the water, and the names further north (Campos Elyseos, Belford Roxo, São João de Meriti, Duque de Caxias) fill out the western coast. The east half is the longer north-and-south coast: Niterói and São Gonçalo sit in the north, Magé, Guapimirim, and Itaboraí run down the eastern shore, Maricá anchors the far south-east corner, Paquetá floats in the bay, and the rest (Suruí, Imbariê, Guia de Pacobaíba, Neves, Sete Pontes, Itambi, Cafubá) fill the eastern and southern periphery. The 16-versus-11 split means the west half has a denser nation layer, which is why the west is the more contested side in two-team play: more names in the same half means more neighbours to fight over, and the beach choke points are where those fights concentrate.
The density of the nation layer relative to the player count is the second key number. With 30 names and a player range of 40 to 75, the average FFA board is roughly 1.3 to 2.5 players per name, which means a full 75-player board leaves about ten names unclaimed at the start and a 40-player board leaves almost twenty. Those unclaimed names are the early game of the map: they are the expansion targets, the free captures, and the reason a Rio FFA does not feel like a 75-player brawl the way a smaller map does. The compact board changes the ratio to roughly one player per two names, which thins the layer enough that expansion into a neighbouring municipality becomes a free move rather than a fight, and that is the mode where the 30-name layout is at its most open. The population-growth guide covers how the nation layer fills up over the course of a match and what an unclaimed name is worth in the midgame, and the v0.35 new-maps overview covers how the 30-nation layout fits into the broader v0.35 trend of denser, more named maps. The point of this section is that the nation layer on Rio is a real, countable, 30-name civic board with no overflow, and the 16-versus-11 west/east split is the first fact you need before you choose a side.
The two-team west/east split and the river fix
The two-team spawn layout on Rio is a hard vertical split at the x=744 line on the 1488-wide map, which divides the board into two 744-by-1680 halves: the west half from x=0 to x=744 and the east half from x=744 to x=1488. This is not a random line; it is the horizontal midpoint of the full canvas, and it is the line the 30 nation coordinates cleanly straddle (the western names end at x=688 and the eastern ones begin at x=851, leaving the midpoint in open water). The practical consequence is that every nation falls on exactly one side of the line, and the 16 west names and 11 east names from the previous section are the two team zones. In two-team play, your side is the half you spawn into, and the split line is the boundary you are fighting over for the whole match. The bay islands — Ilha do Fundão and Ilha do Governador in the west half, Paquetá in the east half — sit close enough to the middle that they are the pivot: whoever controls the bay islands controls the water route between the two halves, and the bay itself is the contested zone that the split line does not cleanly divide.
The river fix in v0.35.5 is the second fact that changes how the map plays. The release body lists “Fix rivers cut off from the ocean on United States and Rio de Janeiro,” and on Rio the fix matters because the map’s geography revolves around Guanabara Bay: the west-side rivers drain into the bay, and before the fix some of them ended at a dead tile instead of the water, which meant a river-adjacent nation had no clean path to the coast. After the fix, the west-side rivers now drain into the bay, which means a nation on the western river corridor has a water route back to the coast that it did not have before, and that changes the value of the western river names (Méier, São Cristóvão, Penha) as expansion and retreat options. The bay is the centrepiece of the map for the same reason: it is the water body that the 30 names wrap around, and controlling the bay means controlling the water routes between the west and east halves. The coastal-boat-defense guide covers the general logic of defending a water choke point, and the naval-stalemate guide covers how a bay that both sides can reach becomes a stalemate if neither commits a fleet, so the river fix and the bay geometry are the two physical facts that make Rio a water-control map as much as a land map.
The decision this section supports is the side choice in two-team mode, and the split gives you two distinct sides with different geometries. The west half is denser, closer to the beach choke points, and home to the downtown cluster, so it is the side you want if you plan to fight for the bay islands and the beach. The east half is longer and more spread out, so it is the side you want if you plan to expand along the coast and use the water as your retreat route rather than your attack route. The team-spawn-formation guide covers the general logic of which spawn side to take when the halves are asymmetric, and the choose-your-spawn guide covers the spawn-choice decision tree that applies across maps. The point of this section is that the split is a real, countable, 16-versus-11 boundary with a bay pivot in the middle, and the river fix is the v0.35.5 change that makes the western river corridor a legitimate expansion route. Both facts are pinned to the v0.35.9 manifest and release body, and both are the physical basis for the side-choice decision in the scenarios that follow.
Decision framework: pick your side and your mode before the countdown ends
The decision that decides a Rio match is the one you make before the countdown ends: which mode you are in, which side of the split you are on, and which of the 30 names you are going for. The framework has three layers, and you work them in order. The first layer is mode, and the choice is between the FFA density game and the team side-selection game. Free-for-all on Rio is a 40-to-75-player board with 30 names, which is a density game where the unclaimed names are the early game and the bay is the midgame pivot. Two-team on Rio is a capped 75/75/60 board with a hard 16-versus-11 split, which is a side-selection game where the west/east geometry is the early game and the bay islands are the contested centre. If you want to play a density game where you pick your own name and expand freely, queue FFA. If you want to play a side-selection game where the map hands you a zone and you fight for the pivot, queue two-team. The lobby-size guide and the map-strategy guide cover the general logic of when density versus side-selection is the better game for your playstyle.
The second layer is side, and it only applies in two-team mode. The west half is the denser, beach-choke side with 16 names and the downtown cluster, and the east half is the longer, coast-side with 11 names and the water retreat route. The west is the side you want if you plan to fight for the bay islands and the beach strip, because those choke points are in the west half and the islands are the pivot. The east is the side you want if you plan to expand along the coast and use the bay as your retreat, because the longer geometry gives you more room to build before you have to commit. The choose-your-spawn guide covers the spawn-choice decision tree, and the team-spawn-formation guide covers which asymmetric side to take when the halves are not equal. The third layer is name, and it applies in both modes. With 30 names and a 40-to-75 player count, you will be competing for a subset of the names at the start, and the names you leave unclaimed are the expansion targets for the rest of the match. The population-growth guide covers how the nation layer fills and what an unclaimed name is worth, and the v0.35 new-maps overview covers the 30-nation layout in the context of the v0.35 trend.
The framework resolves to a simple rule: pick the mode that matches your preferred game (density versus side-selection), pick the side that matches your preferred geometry (beach choke versus coast retreat), and pick the name that gives you the best early expansion without forcing an early fight. The countdown is the hard deadline, and the names you do not lock before it ends are the names someone else locks, so the framework is a pre-countdown decision, not a mid-match one. The scenarios below apply this framework to two specific boards, and they show how the same three layers resolve differently on a full 75-player FFA and on a compact 18-player team board. The map-strategy guide is the general reference for the framework, and the compact-mode guide covers when a compact board is the better choice for the same map.
Scenario one: a full 75-player FFA on the west beach
The first scenario is a full 75-player free-for-all on the west half, which is the densest board the map produces and the one that most clearly shows what the 30-name layer does at maximum density. You spawn into the west half, which has 16 names and the downtown cluster plus the beach strip, and the board is at the large-FFA tier of 75 players. The player-to-name ratio on this board is 75 divided by 30, which is 2.5 players per name on average, but the distribution is not even: the west names are contested and the east names are open, so the west half runs closer to 3 players per name and the east half closer to 2. The practical consequence is that the west names (Copacabana, Ipanema, Leblon, Flamengo, Méier) are the contested names, and the east names (Niterói, São Gonçalo, Magé, Itaboraí, Maricá) are the open names. Your first decision is whether to take a contested west name and fight for it, or to take an open east name and expand without a fight.
If you take a contested west name, you are buying density: you have the beach choke point, you are next to the downtown cluster, and you are close to the bay islands that control the water route. The cost is that two or three other players are in the same name or the adjacent names, and the first five minutes are a fight for the name itself. The beach choke points (Copacabana, Ipanema, Leblon) are the names where the fight is sharpest, because they are the names with the most neighbours and the most water access. If you take an open east name, you are buying expansion: you have the longer geometry, you are far from the downtown fight, and you can build without an early commitment. The cost is that you are far from the bay pivot, and reaching the bay islands means crossing the split line into the contested zone. The cross-water-commitment guide covers the cost of committing to a water route, and the early-expansion-rhythm guide covers the timing of when to push from an open name into a contested one.
The midgame of this scenario is the bay. By the ten-minute mark, the west names are consolidated, the east names are partially claimed, and the bay islands (Ilha do Fundão, Ilha do Governador, Paquetá) are the unclaimed names that everyone is eyeing. The bay is the pivot: whoever holds the islands controls the water route between the two halves, and the river fix means the west-side rivers now drain into the bay, so the west river names (Méier, São Cristóvão, Penha) have a water route back to the coast that they did not have before. The naval-stalemate guide covers how a bay that both sides can reach becomes a stalemate if neither commits a fleet, and the water-nukes guide covers the endgame option of using a water nuke to clear the bay pivot. The endgame of this scenario is the density itself: at 75 players, the board is dense enough that the last few names are worth more than the early names, and the player who holds the bay islands at the twenty-minute mark is the player who controls the endgame. This scenario is the density game, and it is the one you play when you want to fight for the contested names and the bay pivot rather than expand freely.
Scenario two: the compact 18-player team board
The second scenario is a compact two-team board at the 18-player tier, which is the thinnest board the map produces and the one that most clearly shows what the 30-name layer does at minimum density. The compact tier is a quarter of the full figure, floored at three players, so the compact FFA board is 18/13/10 and the compact two-team board is 18/18/15. In the 18-player two-team board, the player-to-name ratio is 18 divided by 30, which is 0.6 players per name, meaning the board is sparser than the nation layer: there are more names than there are players, and almost every name is open at the start. The practical consequence is that the 30-name layout is at its most open in this mode, and the expansion into a neighbouring municipality is a free move rather than a fight. You spawn into your half (west with 16 names or east with 11 names), and the first decision is not “which name do I fight for” but “which direction do I expand.”
In the west half, you have 16 names and the beach choke points, and the compact density means you can take a west name and expand into the beach strip without an early fight. The west names are the dense names, and the compact mode thins them enough that the downtown cluster (Glória, Flamengo, Méier) is open, so you can take a downtown name and expand along the beach without a commitment. In the east half, you have 11 names and the longer geometry, and the compact density means you can take an east name and expand along the coast without a fight. The east names are the spread names, and the compact mode thins them enough that the north-and-south coast (Niterói, São Gonçalo, Magé, Itaboraí, Maricá) is open, so you can take a coast name and expand along the water without a commitment. The compact-mode guide covers the quarter-shrink in detail and when a compact board is the better choice for the same map, and the map-size-compact-mode guide covers the general logic of how the 4x and 16x resolutions change the board.
The midgame of this scenario is the split line. By the ten-minute mark, the west and east names are partially claimed, and the split line at x=744 is the boundary you are fighting over. The bay islands (Ilha do Fundão, Ilha do Governador, Paquetá) are the pivot, and in the 18-player board they are the unclaimed names that the two sides are both eyeing. The bay is the contested centre, and the river fix means the west-side rivers drain into the bay, so the west river names have a water route back to the coast. The team-spawn-formation guide covers the general logic of which side to take when the halves are asymmetric, and the team-trade-coordination guide covers how the two sides coordinate the bay push. The endgame of this scenario is the sparseness itself: at 18 players, the board is open enough that the last few names are the expansion targets, and the player who holds the bay islands at the twenty-minute mark is the player who controls the endgame. This scenario is the side-selection game at minimum density, and it is the one you play when you want to expand freely and fight for the pivot rather than fight for the names.
Failure modes and opponent counterplay
The failure modes on Rio are specific, and they cluster around three traps that the 30-name layer and the capped team mode create. The first trap is the density trap in a full 75-player FFA: you take a contested west name and fight for it, but the density is high enough that you lose the name to a two-player team that outnumbers you, and you are left without a beach choke point and without the downtown cluster. The counter is to take an open east name instead and expand without a fight, or to take a west name and commit to the bay islands rather than the beach, because the islands are the pivot and the beach is the trap. The early-expansion-rhythm guide covers the timing of when to push from an open name into a contested one, and the stack-vs-spread guide covers the general logic of when a dense board favours spreading out over stacking up.
The second trap is the cap trap in two-team mode: you queue two-team expecting a bigger board than FFA, but the cap clips the 1.5× multiplier at the 75 limit, so the team board is the same size as the FFA board, and you are in a side-selection game without the player advantage you expected. The counter is to understand the cap before you queue, and to choose two-team for the side-selection game rather than for the player count. The lobby-size guide covers the formula and the cap in detail, and the team-victory-threshold guide covers how the victory threshold changes when the board is capped. The third trap is the sparseness trap in a compact board: you queue compact expecting a thinner board, but the 30-name layer is so open that the expansion is free for everyone, and the match becomes a race to the bay islands rather than a fight for the names. The counter is to understand the sparseness before you queue, and to choose compact for the free-expansion game rather than for the density fight. The compact-mode guide covers the quarter-shrink in detail, and the map-size-compact-mode guide covers the general logic of how the resolution changes the board.
The opponent counterplay on Rio is the bay. Whatever your failure mode, the opponent’s counter is the bay islands, because the islands are the pivot and the water route between the two halves. If you lose a west name, the opponent takes the bay islands and controls the water route. If you lose the cap, the opponent takes the split line and controls the land route. If you lose the sparseness, the opponent takes the bay islands and controls the endgame. The naval-stalemate guide covers how a bay that both sides can reach becomes a stalemate if neither commits a fleet, and the water-nukes guide covers the endgame option of using a water nuke to clear the bay pivot. The coastal-boat-defense guide covers the general logic of defending a water choke point, and the trade-route-chokepoint guide covers how the bay islands are the trade-route choke point that controls the water route. The point of this section is that the three failure modes are specific, the counters are specific, and the opponent’s counter is always the bay. If you understand the three traps and the bay pivot, you understand the map.
Mode and map adjustments
The mode and map adjustments on Rio are the specific changes that make each mode work, and they are the final layer of the framework. In free-for-all mode, the adjustment is the density management: at 75 players, you manage the 30-name layer by taking open names and expanding, and at 40 players, you manage the 30-name layer by taking contested names and fighting. The density management is the FFA adjustment, and it is the reason the FFA board is a density game rather than a side-selection game. The ffa-midgame-strategy guide covers the midgame density logic, and the ffa-endgame-commit guide covers the endgame commitment that the density game requires. In two-team mode, the adjustment is the side selection: at 75 players, you select the west side for the beach choke or the east side for the coast retreat, and the side selection is the team adjustment, and it is the reason the team board is a side-selection game rather than a density game. The team-spawn-formation guide covers the side-selection logic, and the team-economy-space guide covers the economy management that the side selection requires.
In compact mode, the adjustment is the sparseness management: at 18 players, you manage the 30-name layer by expanding freely and racing to the bay, and the sparseness management is the compact adjustment, and it is the reason the compact board is a free-expansion game rather than a density game. The compact-mode guide covers the quarter-shrink in detail, and the map-size-compact-mode guide covers the resolution logic. The map adjustments on Rio are the bay geometry and the river fix: the bay is the water body that the 30 names wrap around, and the river fix is the v0.35.5 change that makes the western river corridor a legitimate expansion route. The map-layers-space-terrain guide covers the terrain logic that the bay geometry depends on, and the map-strategy guide covers the general map-adjustment logic that applies across maps. The mode and map adjustments are the final layer of the framework, and they are the specific changes that make each mode work on this specific map.
The mode and map adjustments are also the reason the scenarios in this guide are specific: the 75-player FFA scenario is the density game with the density management, the 18-player team scenario is the side-selection game with the side selection, and the compact scenario is the free-expansion game with the sparseness management. The mode and map adjustments are the bridge between the framework and the scenarios, and they are the reason the framework resolves to a specific set of decisions rather than a general set of principles. The lobby-size guide, the map-strategy guide, and the compact-mode guide are the three references that cover the mode and map adjustments in detail, and the v0.35 new-maps overview covers the 30-nation layout in the context of the v0.35 trend. The point of this section is that the mode and map adjustments are the final layer of the framework, and they are the specific changes that make each mode work on this specific map. If you understand the mode and map adjustments, you understand how to play each mode on Rio.
What to take into your next match
The summary of the Rio de Janeiro map is the set of decisions that you carry into your next match, and they are specific because the map is specific. The first decision is the mode: free-for-all is the density game with a 40-to-75-player board and 30 names, and two-team is the side-selection game with a capped 75/75/60 board and a hard 16-versus-11 split. Pick the mode that matches your preferred game, and understand that the team cap means two-team is not a bigger board than FFA on this map. The second decision is the side: the west half is the denser, beach-choke side with 16 names, and the east half is the longer, coast side with 11 names. Pick the side that matches your preferred geometry, and understand that the west is the contested side and the east is the open side. The third decision is the name: with 30 names and a 40-to-75 player count, the unclaimed names are the expansion targets, and the names you leave unclaimed are the early game. Pick the name that gives you the best early expansion without forcing an early fight.
The fourth decision is the bay: the bay islands (Ilha do Fundão, Ilha do Governador, Paquetá) are the pivot, and the bay is the contested centre that the split line does not cleanly divide. Whoever controls the bay islands controls the water route between the two halves, and the river fix means the west-side rivers now drain into the bay. The fifth decision is the compact option: the compact board thins every figure to a quarter (18/13/10 FFA, 18/18/15 teams), and the 30-name layer is at its most open in compact mode. The version boundary is the final decision: this map is a v0.35 new map, pinned to the v0.35.9 tag, and every number in this guide is traceable to the manifest, the lobby formula, or the release body at that tag. The v0.35 new-maps overview covers the 30-nation layout in the context of the v0.35 trend, the lobby-size guide covers the formula and the cap in detail, and the map-strategy guide covers the general framework that this guide applies to Rio.
The Rio de Janeiro map is the v0.35 map that gives every lobby a single all-Brazilian nation set of 30 real neighbourhood names, and it plays at a 75-player base because its 1,491,794 land tiles round the formula to a 75 base. The two-team cap, the west/east split, the bay pivot, and the river fix are the four physical facts that make the map a water-control and side-selection game, and the 30-name layer is the civic mosaic that the players themselves subdivide. The decisions that matter are the mode, the side, the name, the bay, and the compact option, and they are the specific decisions that you carry into your next match. The version boundary is the marker that tells you which build these decisions were derived from, and the v0.35.9 tag is the reference until a future patch moves the land count or the formula. This guide is the Rio-specific instance of the general framework, and it is the reference for how to play the new v0.35 map that gives every lobby a 30-name Brazilian board and a 75-player base.
Related content
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.
- OpenFront AFK Teammate Takeover: Absorb a Disconnected Ally for Zero Troop Loss
A Team-mode decision guide for what a teammate's disconnect does to your win/loss position, when absorbing their land is free, when it is a trap, and what the 30-second mark and the ranked 2v2 rules actually change.
Sep 23, 2026
- How Nations Aim Their Nukes: Smarter Targeting, No Wasted Blasts
A strategy guide for the upcoming AI Nation nuke targeting change: Nations now compute how much of a blast hits enemy land before firing (atom 25%, hydrogen 40% minimums), they skip a spot where another player's nuke is already landing, and they never nuke a target that would hit friendly land. What changes in your decision, the coverage gate, the anti-double-nuke rule, the failure mode and the mode/map adjustments.
Oct 8, 2026
- Alliance-Break Timing: When 30 Seconds Is Worth the Trade
Decide whether to break a live alliance now, wait for it to expire, or renew it, using the 30-second traitor window, the 0.5 defense and 0.8 speed debuffs, and the -100/-40 relation drops in OpenFront v0.34.
Sep 30, 2026