Ommatrypta (v0.35.3): 34 Nations, the 13-Team Force, and the Water's Edge

Quick answer

Direct answer (40–80 words): Ommatrypta is a Halloween-only OpenFront map with 34 eye-pun nations and a large non-nukeable water body ringed by scattered land islets. In v0.35.3 its rotation weight rose from 10 to 19, a new team frequency of 13 was added, and a special team count of 13 forces a 13-team configuration 75% of the time in team and special games. The core decision is whether to race the densest islet cluster for early team-forming or take the water’s edge for a nuke-immune late-game hold.

That single decision — race the densest islet or hold the water’s edge — is the whole game on Ommatrypta, and the v0.35.3 change set directly reshapes it. The map shipped in v0.35.2 with a rotation weight of 10, no team frequency, and no special team count, which made it a low-priority Halloween addition that most players skipped. By v0.35.3 the weight is 19, the team frequency is 13, and the special team count of 13 means that when Ommatrypta appears in a team or special game, it is forced into a 13-team configuration with probability 0.75. This guide is built around that shift: it explains what changed between the two tags and why, walks through the actual spawn geometry that makes the islet cluster and the water’s edge the two value anchors, and gives you a four-step decision framework that tells you which opening to commit to based on the mode, the expected player count, and whether the 13-team force will trigger. By the end you should be able to look at any Ommatrypta lobby and pick the correct opening in under ten seconds. The guide also covers the failure modes that turn a good islet into a lost game, the mode-specific queue strategy that the new rotation values demand, and the exact version boundary — so you know which numbers hold for v0.35.3 and which will shift if a later patch re-tunes the rotation or re-opens the map after the Halloween window.

How to read the rest of this guide. If you only have time for one section, read the Decision framework: it is the four-step test that turns the lobby information into a single opening choice, and it is the section most players need before they lock a spawn. If you already know the framework and want to see it applied, jump to Scenario one and Scenario two, which run the framework through a low-player solo game and a 13-team special game and show exactly what wins and what loses in each. If you keep losing on Ommatrypta and cannot tell why, read Failure modes and countermeasures first, because most of the losses on this map are positional rather than tactical and they have a specific fix each. The Mode and map adjustments section closes with the queue strategy and the version boundary, so it is the right section to read if you are unsure whether what you are playing is actually v0.35.3. Every section is written to stand on its own, but they are sequenced so that the decision-making material comes before the failure analysis, which is the order in which you will need it in an actual lobby.

The v0.35.3 change set, verified against the tag

The single most important thing to understand about Ommatrypta is that it changed materially between v0.35.2 and v0.35.3, and the two versions are different enough that advice written for one does not transfer to the other. I verified every number in this section directly against the two map data files at the two tags, so you can trust that the differences below are real and not an artifact of a stale local copy.

In v0.35.2, Ommatrypta’s info.json carried a multiplayer_frequency of 10, no team_frequency field at all, and no special_team_count field. It was categorized as arcade and new, and it had two layers: an eyeland land layer and an eyewater water layer. The absence of both the team frequency and the special team count means that in v0.35.2 the map was a pure free-for-all with no team-size preference and no forced team configuration. It rotated in rarely — a weight of 10 is low by the standards of the v0.35.x arcade pool — and when it did appear it was almost always a small, uncoordinated scramble.

In v0.35.3, three things changed. First, the multiplayer_frequency rose from 10 to 19, which roughly doubles the map’s appearance rate and makes it one of the more common arcade boards you will see in the Halloween window. Second, a team_frequency of 13 was added as a new field. This is the weight that the playlist uses when it decides whether an Ommatrypta game will be a team game at all, and a value of 13 is a meaningful mid-range weight that makes team games on this map a realistic expectation rather than a rare edge case. Third, a special_team_count of 13 was added. This is the field that the playlist’s special-team logic reads, and it is the source of the map’s most consequential new behavior: when Ommatrypta is played as a team or special game, the playlist forces a 13-team configuration with probability 0.75. The other 25% of the time the playlist falls back to the normal random team-weight roll, which is dominated by the HumansVsNations weight of 20 and the smaller 2-through-7-team weights.

The v0.35.3 release body describes this as “both now prefer higher team counts,” and that is exactly what the special_team_count of 13 does: it makes a large-team configuration the expected default for Ommatrypta team and special games rather than an exception. The practical implication is that if you queue for Ommatrypta in v0.35.3 and you get a team or special game, you should expect up to 13 teams on the board, not the 2-to-7 teams that the normal weight roll would otherwise produce most of the time. This is a huge difference for the opening decision, because a 13-team board changes the value of the densest islet cluster relative to the water’s edge, and the decision framework below is built around that 13-team expectation.

The map’s core design: why the water’s edge and the islet cluster are the two value anchors

Ommatrypta’s layout is a large water body — the eye motif that gives the map its name — ringed by a scatter of small land islets rather than a single contiguous landmass. This is the defining structural feature, and it is the reason the whole game compresses into two value anchors: the densest islet cluster, where early team-forming happens, and the water’s edge, where the late-game hold happens. Understanding the layout is not optional background; it is the premise on which every decision in the guide rests, so I want to walk through the actual geometry and the two layers before I get to the framework.

The first thing to internalize is the layer split. Ommatrypta has exactly two layers: eyeland, a land layer that is nukeable, and eyewater, a water layer that is not nukeable. The nukeable attribute on a land layer means that a nuclear strike destroys that layer’s territory; the water layer, by contrast, is never nukeable, so a nuke that lands on the water does nothing to the water layer itself. This is not a cosmetic detail. It means that any player holding the water’s edge is effectively immune to nukes as a positional matter: a rival cannot nuke the water away from under them, so the only way to dislodge a water-edge holder is to reach them by land contact, which requires a boat or a land bridge that the scattered-islet layout does not reliably provide. The water’s edge is therefore the single most durable late-game position on the map, and it is the reason the late-game hold is a real strategy rather than a desperate fallback.

The second thing to internalize is the islet scatter. The land is not one big continent; it is a collection of small islets scattered around the water. This has two consequences. First, the densest cluster of islets — the group of islets that are closest together and most connected by short land bridges — is where early team-forming is easiest, because players who spawn there can reach each other quickly and form a team without crossing open water. Second, the scatter means that the largest single islet is not necessarily the most valuable, because value on this map comes from connectivity to other islets, not from raw land area. A medium islet that sits in the middle of the densest cluster is more valuable than a large isolated islet, because the cluster’s connectivity is what makes early team-forming and mid-game expansion possible.

The 34 nations are all eye puns — I Dont Know, I See You, Intensive Care Unit, Iris Istable, Pupil, Eye Spy, Eye Candy, Iconic, Blinky, Stare, Winky, Lash Out, Peeker, Lens Armstrong, Opti-Mystic, Spectra Ray, Focuz Finley, Eye-van, Eye See You, Iris you were here, Eye Sore, Eye Conquered, Cant Even, Eye-roll, Looking Good, Spec-tacular, Eye-Opening, Focus, Eye Scream, The Nerve, Sore Eyes, Tigers Eye, and Private Eye. The thematic uniformity is deliberate, but it means the roster does not give you a layout-specific advantage: every nation spawns on the same islet scatter and faces the same water layer. The nation choice on Ommatrypta is therefore almost entirely a matter of personal preference, and the layout-specific decisions belong to the framework, not to the nation pick.

Decision framework: islet cluster vs. water’s edge

The framework is a four-step test that you run before you lock a spawn. It takes the three pieces of information you can see in the lobby — the mode, the expected player count, and whether the 13-team force will trigger — and turns them into a single opening choice: commit to the densest islet cluster, or commit to the water’s edge. The framework is the section most players need, so I will state each step precisely and explain the reasoning behind it.

Step one: identify the mode. If the lobby is a solo free-for-all, the 13-team force does not apply and the normal weight roll decides the team count, which is almost always a small number. If the lobby is a team or special game, the 13-team force applies with probability 0.75, so you should plan for a 13-team board. This is the first and most consequential branching point, because a solo game and a 13-team game have different value anchors.

Step two: estimate the player count. A low-player game — under roughly 12 players — has fewer rivals competing for the densest cluster, which raises the value of the cluster because the competition for it is weaker. A high-player game has many rivals converging on the same cluster, which lowers the cluster’s value because the first-come grab is more likely to be contested and the water’s edge becomes the safer late-game fallback. The player count estimate is a judgment call from the lobby fill, but it is the input that the framework uses to weigh the two anchors against each other.

Step three: check whether the 13-team force will trigger. In a team or special game, the force triggers with probability 0.75, so the expected default is a 13-team board. If you are in a solo game the force does not trigger and you are back to the normal small-team expectation. This step is where the v0.35.3 change set bites: in v0.35.2 the force did not exist at all, so a team game on Ommatrypta was a normal small-team game. In v0.35.3 the force makes the 13-team configuration the expected outcome for team and special games, and that changes the value of the cluster relative to the edge.

Step four: make the choice. If the game is a low-player solo, commit to the densest islet cluster, because the competition for it is weak and the early team-forming is the whole game. If the game is a high-player solo, the choice is closer, but the water’s edge is the safer late-game fallback, so you commit to the cluster only if you are confident you can grab it before a rival does. If the game is a 13-team team or special game, commit to the densest islet cluster for the team-forming, because the 13-team board is too fragmented for any single team to hold the water’s edge early, and the team-forming is the priority. The water’s edge is the late-game target, not the opening.

The framework’s output is a single opening, and the scenarios below show it applied to a low-player solo and a 13-team special game. The key principle is that the choice is made before you lock a spawn, based on the lobby information, not after you are in the game reacting to rivals. Players who lose on Ommatrypta almost always lose because they locked a spawn before they ran the framework, and then found themselves in the wrong anchor for the game they were actually playing.

Scenario one: low-player solo, islet cluster

Scenario one is a low-player solo game on Ommatrypta, the most common case when the map first appears in a fresh lobby. The lobby has eight players, the mode is solo free-for-all, and the 13-team force does not apply because this is not a team or special game. I want to walk through the framework step by step and show exactly what the correct opening is and why the alternative loses.

Running the framework: the mode is solo, so step one gives no team-force expectation. The player count is eight, which is low, so step two raises the value of the densest islet cluster because the competition for it is weak. Step three confirms that the 13-team force does not trigger. Step four therefore says: commit to the densest islet cluster.

The correct opening is to spawn in the densest cluster, the group of islets that are closest together and most connected by short land bridges. The reason is that with only eight players, the cluster is almost certainly uncontested in the first ten seconds, and the early team-forming is the whole game on a scattered-islet map. You form a team with the other players in your cluster, expand along the short land bridges, and by the mid-game you control the cluster and the bridges that connect it to the rest of the map. From there you have two options: you can push toward the water’s edge for the late-game hold, or you can hold the cluster and force rivals to come to you. Either way, the cluster is the value anchor that made the game winnable.

The alternative opening is to spawn at the water’s edge in the first seconds. This looks attractive because the water’s edge is the nuke-immune late-game position, but in a low-player solo the water’s edge is a trap in the opening: with only eight players, nobody else is contesting the cluster, so by the time you have established at the water’s edge, a rival has already formed a team in the cluster and is expanding toward you. The water’s edge is a late-game position, and in a low-player solo the late game arrives later, which means you have a long mid-game in which you are isolated at the edge while the cluster team expands. The cluster wins because it controls the mid-game, and the mid-game is where the game is actually decided on a scattered-islet map.

The scenario’s lesson is that the low-player solo is a cluster game, and the water’s edge is the late-game target you reach after you have won the cluster, not the opening you start from. Players who spawn at the water’s edge in a low-player solo are making the late-game position their opening, which inverts the order of the game and loses the mid-game that decides it.

Scenario two: 13-team special game, fragmented board

Scenario two is a 13-team special game on Ommatrypta, the case that the v0.35.3 change set makes the expected default for team and special games. The lobby is a special game, the 13-team force has triggered with its 0.75 probability, and the board has up to 13 teams. I want to walk through the framework and show how the 13-team expectation changes the opening relative to the low-player solo.

Running the framework: the mode is a special game, so step one applies the 13-team force. The player count is high — up to 13 teams — so step two lowers the value of the densest islet cluster because the competition for it is intense. Step three confirms that the 13-team force has triggered. Step four therefore says: commit to the densest islet cluster for the team-forming, but understand that the 13-team board is too fragmented for any single team to hold the water’s edge early.

The correct opening is to spawn in the densest cluster and form your team there, but the reason is different from the low-player solo. In a 13-team game, the cluster is contested — all 13 teams want the best team-forming position, and the first team to grab a good islet in the cluster gets a real advantage. The team-forming is the priority because a 13-team board is too fragmented for any single team to establish a water’s edge hold early: with 13 teams spread across the islets, no single team can reach the water’s edge and hold it against twelve rivals. The team-forming is therefore the mid-game priority, and the water’s edge is the late-game target that only the team that wins the cluster will realistically reach.

The 13-team force is what makes this scenario different from the low-player solo. In the solo, the cluster was uncontested and the team-forming was easy. In the 13-team game, the cluster is contested and the team-forming is a fight. The 0.75 force chance means that when you queue for a special game on Ommatrypta, you should expect the 13-team board most of the time, and you should plan your opening for a contested cluster, not an uncontested one. The scenario’s lesson is that the 13-team force changes the cluster from an easy grab into a contested position, and the opening decision has to account for that contest.

The failure mode in this scenario is to treat the 13-team game like the low-player solo and spawn at the water’s edge in the opening. With 13 teams, the water’s edge is unreachable in the opening because the islets are too fragmented and the crossing is too long, so a player who spawns at the edge is isolated and loses to the team that wins the cluster. The counter is to commit to the cluster, fight for the team-forming, and treat the water’s edge as the late-game target that you reach only after you have established your team in the cluster.

Failure modes and countermeasures

Most losses on Ommatrypta are positional rather than tactical, and they cluster into four specific failure modes, each with a specific countermeasure. I want to name each one precisely because the failure is usually obvious in review but invisible in the moment, and the countermeasure is a change to the opening decision, not a change to the in-game play.

Failure one is spawning at the water’s edge in a low-player solo. This is the most common mistake, and it inverts the order of the game: the water’s edge is the late-game position, and by making it your opening you lose the mid-game that decides the game. The countermeasure is to run the framework before you lock a spawn: in a low-player solo, the framework says commit to the cluster, so you commit to the cluster and reach the water’s edge later, after you have won the cluster. The failure is a framework error, not a tactical error, and the countermeasure is to actually run the framework.

Failure two is misreading the team-count force. In a team or special game, the 13-team force triggers with probability 0.75, so the expected default is a 13-team board. A player who assumes a small-team game and commits to the water’s edge on the expectation that the board will be small loses to the team that races the cluster on the 13-team expectation. The countermeasure is to check the mode and the force probability before you commit: in a team or special game, plan for the 13-team board, not the small-team board. The failure is a lobby-reading error, and the countermeasure is to read the lobby before you lock a spawn.

Failure three is the silo trap. A player who builds a silo on an islet and assumes they are safe from nukes is wrong about the water’s edge: the silo on the islet is safe from nukes, but the player is still reachable by land contact from a rival who dislodges them from the water. The silo gives nuke immunity on the islet, but it does not give positional immunity at the water’s edge, and a rival who reaches the edge can dislodge the silo holder. The countermeasure is to understand that the silo is a positional tool, not a positional guarantee: it keeps you safe from nukes while you hold the islet, but it does not keep you safe from a rival who reaches the water’s edge. The failure is a layer-semantics error, and the countermeasure is to remember that the water layer is non-nukeable, which is exactly why the water’s edge is the durable position.

Failure four is over-boating. Boating is the most underused tool on Ommatrypta and the most overused. A player who commits to boating in the opening is slow and exposed during the crossing, and on a scattered-islet map the crossing is long and the rival can contest it by land. The countermeasure is to boat only when the water is large and the land is fragmented enough that a land player cannot easily reach the boat, which on Ommatrypta is true in the late game but not in the opening. The failure is a timing error, and the countermeasure is to boat late, after you have established your team in the cluster and the rival’s land positions are fixed.

The four failures are positional, and the four countermeasures are all changes to the opening decision, not to the in-game play. The common thread is that the failure happens before the game, in the lobby, when the player locks a spawn without running the framework. The countermeasure that fixes all four is the same: run the framework, read the lobby, and commit to the anchor that the framework says is correct for the game you are actually playing.

Mode and map adjustments, version boundary, and further reading

The mode and map adjustments are the last thing you need before you queue, and they are the section to read if you are unsure whether the guide’s numbers apply to the game you are about to play. The version boundary is the most important of the three, so I will state it first and then close with the queue strategy and the further reading.

The version boundary: every number in this guide is verified against the v0.35.3 tag, and the v0.35.2 numbers are different. If you are playing v0.35.2, the map has a rotation weight of 10, no team frequency, and no special team count, so the 13-team force does not exist and the guide’s team-count logic does not apply. The v0.35.2 water geometry is also different from the v0.35.3 “better water” pass, so the water’s edge position is not identical between the two versions. The two columns below are the verified values pulled from map-generator/assets/maps/ommatrypta/info.json at each tag; every field that changes is a field the 13-team force and the rotation weight depend on, so if you are reading a lobby built on v0.35.2 you are playing a different map from the one this guide describes.

Field (info.json)	v0.35.2	v0.35.3
Nation count	34	34
multiplayer_frequency (rotation weight)	10	19
team_frequency	(absent)	13
special_team_count	(absent)	13
Special-team force chance (MapPlaylist)	n/a	0.75
Land layer (eyeland)	nukeable	nukeable
Water layer (eyewater)	non-nukeable	non-nukeable, “better water” pass

If you are playing v0.35.3, every number in this guide holds: the 19 rotation weight, the 13 team frequency, the 13 special team count, the 0.75 force chance, and the two-layer split with the non-nukeable water. The version boundary is the reason I verified the numbers against the tag rather than against a stale local copy, and it is the reason the guide’s freshness summary points to the two tags.

The queue strategy: during the Halloween window, queue for team and special games on Ommatrypta to maximize your exposure to the 13-team configuration, because that is the case that the v0.35.3 change set makes the expected default. If you want to learn the low-player solo, queue for solo free-for-all and let the rotation give you the low-player case. If you want to learn the 13-team case, queue for team and special games and let the 0.75 force give you the 13-team board. The queue strategy is the same as the framework: choose the mode that gives you the case you want to learn, and let the force do the rest.

The map’s future: Ommatrypta is a Halloween-only map, which means it will not appear in the public rotation after the Halloween window closes. If you want to learn the map’s mechanics, learn them now, during the window, because you will not see the map in the public rotation after the window. The water’s edge hold and the islet-cluster spawn are the two core skills that transfer to other scattered-islet maps, and they are learnable now.

Further reading: the v0.35.3 new maps overview covers the full Wernicke’s Area wave and the context for where Ommatrypta sits in it. The Brain Rot guide covers the other Halloween map from the same wave and its 50-to-19 rotation change, which is the companion case to Ommatrypta’s 10-to-19 change. The v0.35.3 AI alliance behavior guide covers how teams form and coordinate, which is the input that the 13-team force feeds into. The choose-your-spawn guide covers the general spawn framework that this guide’s framework is a specialization of. Read the overview for the wave context, read the Brain Rot guide for the companion map, and read the AI alliance behavior guide for the team-forming input, and the four guides together give you the full picture of the v0.35.3 map wave.