Four Islands Team Coordination: Routes, Roles, and Nuclear Timing

Direct answer: treat Four Islands as four jobs joined by a timetable

Direct answer: Assign one teammate to hold each starting theatre, one to own the first crossing, one to convert the landing, and one to preserve a fallback. Launch a Transport only when route, landing force, escort, and return are named. End the crossing when the new shore is autonomous, then move resources to the next bottleneck.

On Four Islands, a team wins by making separated land positions behave like one economy. Give each theatre one job, name the route that joins it to the next theatre, and assign a player to watch the route until the job is complete. Do not open with four players all building the same structure or all sending transports toward the nearest beach. The map is a 1,500 by 1,500 square with 517,506 playable land tiles in the official v0.33.12 manifest, and its special team spawn areas divide the map into two vertical halves for two teams or four quadrants for four teams. Those divisions are a planning aid, not a promise that every island has equal land, income, or defensive value.

The practical loop is simple. First, establish one safe core on the island your team actually owns. Second, decide which neighbouring island is the next objective: a vacant expansion, a port that opens a route, or a player whose defeat removes a dangerous crossing. Third, connect the objective with one transport or rail plan and one land-support plan. Fourth, stop investing when the route has done its job and move the same player, Gold, and ships to the next bottleneck. A route that is open but has no landing troops is not team progress; it is an exposed schedule.

Use this guide for a Team or custom Four Islands lobby when the question is coordination between separated islands. Use Island defense when one coast is already under a transport landing. Use Team Roles for the wider donation and role framework, and Nuclear Deterrence when a Silo or SAM is the shared constraint. This page owns the map-specific sequence: who secures which island, what the first crossing must accomplish, and when the team should stop treating every shoreline as an emergency.

Before the first expansion, say three facts in team chat: “Our home theatre is ___; our first crossing is ___; the fallback is ___.” Then add one invalidating event, such as a captured Port, an unreachable shoreline, or a new nuclear threat. This turns a vague promise to “help the left side” into a state that can be checked on the map. The team does not need a permanent captain, but it does need one current owner for each route and one person who can call that the route is finished.

The winning habit is therefore not speed alone. It is synchronized attention. A player who grows safely on one island can be more valuable than a player who launches a spectacular landing that nobody can reinforce. Four Islands rewards the team that converts distance into a sequence of small, verifiable commitments.

Read the official map geometry before assigning a side

The Four Islands manifest defines a 1,500 x 1,500 normal map and reports 517,506 land tiles. Its map4x representation is 750 x 750 with 127,769 land tiles, while map16x is 375 x 375 with 31,175 land tiles. These are source facts about the terrain representations, not a promise that a Compact or zoomed match preserves every shoreline detail in the same way. The manifest also names four Nation anchors: Korinthal at approximately (403, 1296), Lunareth at (1152, 1251), Sylvoria at (1328, 322), and Myrkwind at (114, 121). Nation anchors describe bot configuration. They are not guaranteed human spawn points and should never be used as a substitute for reading the lobby’s actual spawn markers.

The team spawn areas are the most useful coordination fact. For two teams, the map is divided into a left 750-pixel half and a right 750-pixel half, each covering the full height. For four teams, it is divided into four 750 by 750 quadrants. Treat those areas as initial ownership zones, then verify where players actually appear and which coastlines are connected by reachable water. A quadrant can contain a valuable port, a narrow beach, or a long interior route; equal rectangle size does not create equal economic value.

Make a quick geometry ledger before spending Gold. Record the island or quadrant each teammate occupies, the nearest safe City or core, the first shoreline that can receive a Transport, and the alternate shoreline if the first one is blocked. Mark which side of the water has a completed Port and which player can escort it. If a planned line crosses a map edge, impassable tile, or disconnected water component, replace the plan immediately. The official manifest does not promise that every visually close coast is a legal landing.

Distance must be interpreted as time and attention. A shoreline 80 tiles away may be strategically farther than one 140 tiles away if the shorter path crosses an enemy Port or a narrow beach watched by a Warship. Conversely, a distant open-water landing can be safe if the team has a screen and enough land troops to hold the arrival tile. Use map geometry to count choices, not just pixels. One route with a fallback is a manageable team assignment; three routes that each require a different escort are a coordination failure.

The map’s four-island identity also changes the meaning of “frontline.” Your teammate on another island may be safe from land attacks while still being the first player who can lose a Port, transport lane, or SAM. Ask which loss would disconnect the team rather than which player has the smallest territory. After every major capture, redraw the route ledger: ownership, water path, safe landing, reserve, and next switch signal. This five-line update is faster than arguing from the opening screenshot and keeps the plan valid when a shoreline changes.

Assign four jobs, then let the jobs move with the map

Start with four jobs even when the lobby has only two players per team. The anchor secures the home island and keeps a protected City or core. The bridge owns the first crossing, including Port placement, Transport timing, and the landing tile. The pressure player turns a successful landing into a real enemy problem with land troops or a second route. The reserve player watches the teammate who can lose the most valuable structure and holds Gold or troops for the next irreversible event. These labels are not classes and provide no engine bonus. They are a short way to state who acts next and what ends the assignment.

Each job needs a switch signal. The anchor changes job when the home border is stable and the core can survive without immediate reinforcements. The bridge changes job when one Transport has landed safely, the route is cut, or the Port is no longer connected. The pressure player switches when the target retreats behind a prepared defence or when a second island becomes a greater threat. The reserve becomes an anchor or bridge when the first emergency is resolved. Without a switch signal, a player can spend the whole match protecting a route that stopped mattering ten minutes ago.

Use a compact status board in chat or a shared note. Write HOME, CROSSING, TARGET, RESERVE, and one number beside each: current troops, useful Gold, route distance, or remaining timer. A teammate does not need your entire hidden state; they need the fact that changes the next action. “Bridge has 90,000 Gold and a Port; landing needs 140,000 troops” is actionable. “I am preparing navy” is not. Update the board after a capture, a Port loss, a large donation, or a nuclear launch.

The first job is usually more valuable than the most dramatic one. If an anchor leaves a safe home island to chase a target, the team may gain territory while losing the only player who can rebuild a City or hold a return landing. If the bridge launches before pressure troops are ready, the Transport becomes a moving investment with no conversion step. If the reserve spends everything on a distant attack, a local Silo or Port may fall without a response. The job framework exposes these failures early because each action must name its owner and its follow-up.

Two-player teams should combine jobs deliberately. One player can be anchor plus reserve while the other is bridge plus pressure, but the combination must be visible. Four-player teams can rotate the bridge after the first landing and let the original bridge become a reserve for the new theatre. In a lobby with donations enabled, the donor is still a moving job; check capacity and cooldown before promising a transfer. This map guide does not replace Team Roles, it makes that framework concrete on Four Islands.

Build the first crossing as a complete sequence

Do not call a crossing successful because a Port is built or a Transport is launched. Define completion before the first click: one reachable destination, one landing tile that can be held, one land force ready to expand, and one fallback if the defender appears. A Port provides a naval base and possible trade route, but it does not by itself convert water access into territory. A Transport can be a cheaper bridge than a full fleet, yet it still needs a valid shoreline and enough troops to survive the landing delay. A Warship screen protects the route only while it stays between the threat and the Transport; a ship chasing a distant target can leave the crossing open.

Use a three-check launch order. Route: confirm that the source and destination shores share reachable water and that the destination is not already owned or blocked in a way that invalidates the plan. Force: count the troops that will arrive, the troops already on the target island, and the reserve that can respond if the first tile is contested. Return: name the Port, coast, or land corridor that lets the team retreat or reinforce. If any answer is unknown, hold the launch for one observation cycle and spend attention on scouting rather than adding another ship.

The bridge should report a time window rather than a vague intention. “Transport leaves after the next 20 ticks; landing force is 180,000; pressure reaches the beach 15 ticks later” lets the anchor decide whether to hold or donate. These values are scenario assumptions, not universal game timers. The important property is that all players can test whether the landing force and support arrive in the same window. A crossing with a 60-tick gap between ship and troops is two separate fights, not one coordinated move.

Place the first landing where the team can widen. A narrow beach next to an enemy Port may look valuable because it is close, but it can trap the arrival under a Warship or Defense Post. A slightly farther coast that reaches an interior City gives the pressure player room to form a core. The island defense guide explains how a defender screens a landing; use that perspective to predict the counter. Ask where the enemy will retreat, not only where the Transport will appear.

After a successful arrival, stop the bridge job when the landing has a self-sustaining result. That may be a connected City, a captured Port, a safe route for the next Transport, or a forced retreat by the defender. Do not keep buying ships because the first one survived. Move Gold to the next bottleneck, leave one escort if the route remains contested, and mark the old crossing as open, unsafe, or closed. This prevents the common Four Islands failure in which every teammate protects the same first lane while a second island becomes the decisive theatre.

Scenario one: two teams split by the centre water

Assumptions: a two-team lobby uses the official left/right spawn-area split. Your team has one player on each half, a completed Port on the left, 180,000 troops ready near a safe beach, and a second player with 220,000 troops defending the home City on the right. An enemy Port is visible across the centre water, but the route has not yet been screened. These numbers describe one replay state; they are not a required opening build or a prediction of win probability.

The anchor’s first call is to protect the right City and hold enough reserve to survive one land push. The bridge checks whether the left Port can reach a destination that widens the team rather than simply touching the nearest shoreline. The pressure player waits until the bridge confirms the landing tile and the reserve player records the enemy Warship or Port that could cut the return. If the bridge launches immediately because the enemy Port looks weak, the team may trade 180,000 troops for an isolated beach while the home City becomes the easier target.

Suppose the route ledger says: source Port is safe, destination shore is 90 water tiles away, enemy Warship is 120 tiles from the likely lane, and the pressure force can arrive 15 ticks after the Transport. Launch one Transport, keep the escort between it and the enemy, and do not split the pressure force into two beaches. The anchor remains home until the landing is confirmed. The reserve player keeps enough Gold for a City or emergency defence rather than spending it on a second Port.

At the landing check, three outcomes are possible. If the beach is empty and the pressure force reaches the first interior tile, mark the crossing open and transfer the bridge to the next theatre. If the enemy contests the beach with a comparable force, delay the second Transport, keep the home reserve intact, and ask whether a different coast creates a better route. If the enemy Warship forces the escort away before the landing, mark the route closed, retreat what can safely return, and move the bridge job to a new shoreline. The team loses less by abandoning one route than by feeding three identical transports into a watched beach.

The opponent’s counterplay is to attack the anchor while the bridge is committed, threaten the Port rather than the Transport, or show a false Warship route that pulls the escort away. The correct response is not to chase every signal. Re-run the five-line ledger: who can lose a core, which route still has a landing, how many troops arrive together, what reserve remains, and what objective the crossing protects. If the home City is now the only condition that keeps the team alive, cancel the distant pressure and reinforce home. A Four Islands crossing is successful only when it improves the team’s next decision, not when a ship reaches an attractive pixel.

Scenario two: four teams and a late nuclear bottleneck

Assumptions: a four-team custom lobby uses four 750 by 750 spawn quadrants. Your team controls the lower-left quadrant and a small upper staging coast. You have a 300,000-troop home force, 150,000 troops on the staging coast, one Port, and 2,000,000 Gold. An opponent has a completed Silo near the centre and a SAM that covers its own core. The team can fund either another Port-and-escort plan or a defensive SAM, but not both immediately. The figures are deliberate assumptions for a decision test, not official Four Islands thresholds.

Begin by naming the shared bottleneck. The enemy Silo changes the value of every island route because a concentrated Port, City, or bridge can become a nuclear target. The reserve player therefore measures structure density and escape paths before the bridge player orders a crossing. If one SAM can cover the home City and Port, building it may protect the route that makes every later landing possible. If the core is spread across two quadrants and the enemy can reach only one with a useful shot, a second crossing may create more value than a rushed launcher. The answer depends on coverage and timing, not on a fixed “build SAM at minute five” rule.

Suppose the team chooses the SAM first. The anchor keeps the 300,000 troops around the protected core, the bridge uses the existing Port for scouting and one cheap escort, and the pressure player prepares the 150,000 staging force without launching. The team now has a clear switch: when the SAM is complete and the enemy has not changed targets, the bridge can spend the next Gold on a Transport; if the enemy launches or moves the Silo, the bridge remains a reserve and the pressure player protects the new target. A defensive purchase has value because it changes the number of safe future routes.

Alternatively, suppose the enemy Silo is exposed, the home core already fits inside the current SAM, and the only route to the Silo is a narrow water crossing. The team can use the Port to move the 150,000 staging force, escort it with a Warship, and hold enough Gold for a response. The crossing is not a blind nuclear rush. The target caller must confirm whether the strike or land push removes the Silo, whether the enemy SAM can intercept the chosen weapon, and whether the team can defend the new edge after capture. Nuclear Deterrence owns those weapon-specific checks; this guide owns the Four Islands handoff between water and land.

The four-team counter is coalition pressure. Two opponents can attack the same Port from different quadrants, force the escort to choose a lane, or wait until the team spends its Gold on a launcher. Keep one fallback City and one route that does not depend on the contested Port. If the staging coast becomes a liability, withdraw before it is surrounded; preserving 150,000 troops can be worth more than holding a disconnected beach. The scenario’s completion test is observable: the team can name its protected core, one active crossing, one nuclear response, and the exact event that transfers the bridge job to another quadrant.

Failure modes and the counters that actually work

The first failure is four-way urgency. Every island appears to need help, so every teammate opens a separate front. The counter is a single current objective and a second objective in reserve. If the team cannot say which route changes the next ten seconds, it should hold Gold and scout. A quiet island is not automatically safe, but it is often less urgent than a Port that can disconnect three players.

The second failure is transport without conversion. A ship arrives, but no land force can hold the beach or reach a City. The counter is to make the pressure force part of the launch condition. Count the troops that arrive together, the distance to the first stable tile, and the reserve that can answer a defender. If the answer is “we will send troops later,” the first crossing is an expensive signal rather than an operation.

The third failure is escort fixation. A veteran Warship keeps chasing a visible enemy ship while the main Transport uses a different lane. The counter is a named escort job with an end condition: protect this crossing until the landing is stable, then return or switch to the next lane. Warship veterancy and repair decisions belong in Warship veterancy, but Four Islands adds a map rule: a ship that is technically alive can still be in the wrong theatre.

The fourth failure is centralized structure risk. A team puts its Port, City, Silo, and SAM on one island because that island feels safe. A single nuclear strike or land push then removes income, capacity, and response together. Spread critical functions when the route can support them, and keep a fallback tile that another teammate can reach without the original Port. This is not a demand to build every structure twice; it is a demand to know which loss ends the team’s plan.

The fifth failure is stale ownership assumptions. A teammate says “our northern beach” after an enemy has captured the approach, or a player uses a route remembered from the opening before a shoreline changed. Recheck owner, connected water, Port status, and reachable landing after every major capture. The official manifest supplies the map geometry, not the live ownership graph. The live graph always wins.

Opponents have equally clear counters. They can threaten two ports, split the team’s escort, attack the anchor while the bridge is away, place a Defense Post behind the beach, or use a nuclear threat to force a premature retreat. Do not answer with more of the same investment. Change the job owner, shorten the route, choose the fallback, or stop the crossing. A team that can abandon a low-value lane without blame preserves enough attention for the decisive island.

Mode, map, and lobby adjustments

In a two-team Four Islands match, the left/right spawn-area split makes the centre water a natural bridge, but it also creates predictable pressure. Keep one player responsible for each half until the home cores are stable. A bridge can then move across the centre while the anchor preserves the team’s original depth. Do not interpret the rectangle as a guarantee that both sides have equal beaches; inspect the actual land and Port positions.

In a four-team match, the quadrant split creates more possible coalitions. A crossing that looks like a direct attack may expose a third team behind it. Count who benefits if two teams fight on one island and who can reach the Port after the battle. The Threat Assessment guide provides the whole-board scan; this page adds the Four Islands route ledger and job handoff. If the map becomes a three-team endgame, merge the bridge and reserve jobs around the one crossing that still changes territory.

Compact or reduced-resolution settings require a fresh read. The manifest’s map4x and map16x representations report fewer land tiles than normal, but they do not authorize a player to scale distances or assume every small beach survives. Recheck the first landing, the interior City path, and the number of usable ports. On a compact map, a 50-tick construction or travel window can be a larger share of the fight; on a spacious map, the same window may be safe if the reserve can arrive.

If the lobby disables Ports, Warships, Trains, or nukes, remove those jobs from the status board. Do not leave a bridge assigned to a Port that cannot be built. When nukes are disabled, put the reserve player’s Gold into capacity, land defence, or a second route. When transport access is limited, choose a land objective reachable from the team’s current island and treat the sea as observation rather than expansion. Custom alliance duration can change diplomacy timing, but it does not change the need to name a route owner and a fallback.

Map adjustments also include player behaviour. A team with reliable voice communication can use shorter status updates; a team communicating only through pings should write the objective and invalidating event explicitly. A public FFA game on Four Islands is not covered by this team guide: use Map Strategy and Island Defense for independent threat and landing decisions. The guide’s facts remain useful, but the ownership and role assumptions change.

Decision table, replay checklist, and next reading

Use this table before each crossing or major handoff. The values marked as assumptions belong to the replay, while the geometry values come from the official v0.33.12 manifest.

Signal	Verified or assumed value	Team decision	Stop or switch when
Normal map grid	1,500 x 1,500 (verified)	Keep a route ledger instead of comparing screenshots	The live shoreline or ownership changes
Normal playable land	517,506 tiles (verified)	Treat island size as a resource, not a victory guarantee	A smaller island controls the only safe Port
Two-team spawn areas	Two 750-wide vertical halves (verified)	Keep one anchor on each half until cores are stable	One half can survive without immediate help
Four-team spawn areas	Four 750 x 750 quadrants (verified)	Assign one job per quadrant and watch coalition pressure	A new team becomes the outside beneficiary
Example landing force	180,000 or 150,000 (assumed)	Launch only when the force and support share a window	The defender can isolate the beach
Example route gap	15 ticks between Transport and pressure (assumed)	Call the crossing one operation and track its owner	The gap grows into a separate fight
Nuclear budget	2,000,000 Gold (assumed)	Choose SAM, Silo pressure, or route based on core coverage	The enemy changes target or the core is exposed

Replay the sequence in six sentences: identify the home theatre; name the first crossing; state who owns the bridge job; report the landing force and reserve; name the fallback shoreline; state the event that ends the job. If a teammate cannot repeat those sentences, the plan is not ready. After a capture, Port loss, nuclear launch, or major donation, repeat them with current values. This is deliberately lighter than a fixed build order because Four Islands punishes plans that survive only in the opening screenshot.

The most common wrong conclusion is “we need more ships.” The better question is “which missing condition prevents the next team result?” It may be a safe City on the destination island, troops with enough capacity, an escort that stays on the lane, a SAM covering the Port, or a reserve that can defend the home quadrant. Build the missing condition, then stop. A second identical structure is justified only when it protects a different route or removes a different bottleneck.

For follow-up reading, use Island Defense for landing screens and coastal fallback, Land Combat for the fight after the Transport arrives, Team Roles for donations and rotating responsibilities, and Nuclear Deterrence for weapon and SAM choices. Use Map Strategy when the next match has a different topology. The official map facts for this article come from the v0.33.12 Release and the Four Islands manifest. If a later formal release changes the manifest, re-run the route ledger and replace assumptions with a fresh replay.