OpenFront Quick Chat: Coordinate a Team Without Voice

Direct answer: send one problem, one target, and one next action

Use Quick Chat as a short operational contract, not a running conversation. Identify one visible problem, send the phrase that names the required action, attach the relevant player when the phrase supports a target, and wait for movement on the map. If nothing changes, send one clearer follow-up after the three-second recipient cooldown; if the state changes, cancel the old plan rather than repeating it.

That answer matters because OpenFront gives you a vocabulary, not shared judgment. “Attack,” “Focus,” “Defend from,” “Help defend,” “Build Warships,” “Need Gold,” and “Saving for MIRV” can align a team, but none of them transfers control, proves that the sender read the board correctly, or reserves the recipient’s resources. A message becomes useful only when the recipient can connect it to a visible map state and take one bounded action. “Attack Green” is a weak signal when Green has three fronts. “Focus Green, east border, after their current push lands” is a complete plan even though Quick Chat carries only the first two parts; the map supplies the border and timing. The sender must therefore choose a moment when the missing context is obvious.

Use the SCOPE protocol before every message. Scan the shared board for the single bottleneck that can change within the next few seconds. Choose one result: hold, push, stop, fund, build, or warn. Object the message by attaching the player who is the threat, target, or beneficiary whenever the phrase requires one. Pause for the cooldown and for a visible response. Evaluate the new board, then either confirm with one different message or abandon the request. SCOPE is intentionally smaller than the role framework in Team Roles: roles say who owns a class of work across the match; SCOPE decides what one player should understand now. It also begins after Team Spawn Formation has done its job, because the engine does not execute Quick Chat during the spawn phase.

Visible state	Best first signal	Required object	What counts as confirmation	Stop signal
One teammate is being collapsed	Help defend / Defend from	Teammate or attacker	Reserve turns toward the endangered border	Attacker breaks off or another front becomes worse
Enemy exposes a thin decisive front	Attack / Focus	Enemy player	Two friendly pushes begin on compatible sides	Enemy reinforces, route closes, or reserve floor is crossed
Team lacks the unit that opens a route	Build Warships / Need Gold	Usually none	Named player starts the build or preserves Gold	Water loses relevance or payer becomes threatened
A leader is near the finish	Number-one warning / Finish	Leader when supported	Team stops side projects and pressures scoring land	Threshold changes or a cheaper defensive route appears
Trade or nuclear plan has changed	Stop trading / Saving for MIRV / MIRV ready	Partner or target when supported	Spending and routes visibly change	Embargo, Silo loss, target death, or new urgent defense

The table is a decision aid, not a promise that the recipient will obey. A skilled teammate may reject the request because their view contains a constraint you did not see: a second attacker, a nearly completed City, an incoming warhead, a transport already committed, or an army cap that makes a donation wasteful. Treat non-response as information. Re-scan before sending again, and do not use greetings, complaints, or repeated danger messages to occupy the same communication window. The Threat Assessment guide helps decide whether the named player is actually the important threat; this page owns the narrower handoff from that decision to a teammate who cannot hear your voice.

The version boundary is v0.34.20, verified 27 September 2026. The tagged phrase catalogue contains help, attack, defend, greeting, miscellaneous, and warning families. Some phrases require a player object and some do not. The server records a separate outgoing cooldown for each recipient, so a message to one teammate does not lock messages to every teammate. The practical rule is still restraint: technical permission to contact three teammates rapidly is not evidence that three simultaneous plans are good. One plan with a named owner beats three alerts with no priority. Use Quick Chat to reduce ambiguity at the decision point, then let the units, Gold, borders, and timers show whether the team accepted the contract.

What Quick Chat actually sends, and what the cooldown changes

In the v0.34.20 source, Quick Chat is a direct exchange between one sender and one recipient. QuickChatExecution validates the recipient, checks whether the sender can message that recipient, records the cooldown, and displays the translated phrase to both sides. It can also carry an optional target player for phrases that require one. That is a much narrower channel than a global team broadcast. If you need two teammates to understand the same attack, each needs their own message, or one teammate must be able to infer the plan from the map. This directness is useful because it assigns ownership, but it also creates a failure mode: the unmessaged teammate may interpret two coordinated pushes as independent and spend against the wrong front.

The phrase catalogue exposes six families. Help includes requests for Troops, frontline Troops, Gold, no attack, an apology, an alliance, help defending a named player, and trade partners. Attack contains attack, MIRV, focus, finish, and build Warships. Defend contains defend a player, defend from a player, do not attack a player, ally with a player, and build Defense Posts. Greetings carry social feedback and trust language. Miscellaneous includes go, strategy, team up against a named player, build closer, and coastline. Warnings include strong or weak players, MIRV timing, the number-one warning, stalemate, allies, betrayal, dangerous bases, saving for MIRV, ready MIRV, snowballing, cheating, and stop-trading messages. The catalogue tells you what can be said; it does not tell you which statement is true.

The important numerical rule is the cooldown. The official test advances through quickChatCooldown(), documented there as 3 * 10 = 30 ticks, before the same sender can message the same recipient again. At the normal 100 ms simulation tick, that is roughly three seconds. The cooldown is directional and per recipient. If Blue messages Red, Blue cannot immediately message Red again, but Red can still message Blue, and Blue can still message Yellow. This lets a caller notify separate owners without waiting nine seconds, but it also means the engine does not enforce a global message budget. Your own protocol must provide the budget: no more than one live request per recipient, and no follow-up until you can state what changed since the first.

Those three seconds are a diagnostic window. For an attack request, watch whether the recipient’s troop line turns toward the target, whether their reserve starts falling, and whether the enemy begins moving to answer. For defense, watch whether friendly troops or ships move toward the threatened player, not whether the recipient replies with “Thanks.” For Gold or construction, look for the structure, donation, or spending delay that demonstrates the request was understood. A social reply can acknowledge receipt, but only board state confirms action. The pause prevents a sender from replacing evidence with volume.

Targeted and untargeted phrases should be chosen differently. A targeted phrase is best when identity is the uncertainty: which enemy to focus, which teammate needs defense, which player is becoming strong, or which trade partner should stop. An untargeted phrase is best when the requested capability is the uncertainty: build Warships, build Defense Posts, need Gold, need frontline Troops, or find trade partners. Do not attach a convenient enemy just to make an untargeted shortage feel specific. Conversely, do not send “Go” when three enemies are visible and expect the recipient to guess which border you mean. The object is not decoration; it is the part of the message that prevents two rational players from choosing different plans.

Quick Chat does not execute during the spawn phase. The implementation explicitly returns false from activeDuringSpawnPhase(). That boundary changes opening coordination. A team must use visible placement, team colors, and the map geometry during the countdown; the first Quick Chat contract begins only after the simulation leaves spawn. Do not design a formation that depends on sending “coastline” or “build closer” before positions lock. Instead, enter the game with a simple visual fallback: leave independent expansion lanes, avoid stacking every player onto one pocket, and use the first post-spawn message to repair the most obvious mismatch. Team Spawn Formation owns that placement decision; Quick Chat starts where placement ends.

There is also a distinction between Quick Chat and the target marker described in older team guidance. A Quick Chat phrase is a direct translated message, optionally carrying a player. It is not a shared vision effect, it does not reveal hidden units or Gold, and it does not order an ally’s army. A recipient can accept the analysis and still decline the action. Design every call so that refusal does not destroy the team: keep your own reserve, do not launch a one-way Transport before support moves, and do not spend the MIRV budget because another player was told to donate. Coordination reduces uncertainty; it does not transfer risk away from the player who clicks.

Two worked scenarios: defense first, then a timed finish

Scenario one, 4v4 continental Team match at 8:00. Assume your eastern anchor has 420,000 Troops, is facing an opponent with 610,000 committed on a broad border, and has another enemy with 300,000 one corridor away. You hold 540,000 in the center. A western teammate owns 780,000 but is expanding into neutral land, and the fourth teammate has 2.6 million Gold reserved for a Factory level. The wrong call is to message everyone “Attack East.” It hides the immediate problem: the anchor needs enough reserve to avoid collapse before any counterattack can matter.

Run SCOPE. Scan: the eastern border is the only failure that can remove a teammate within seconds. Choose: hold, not attack. Object: message the central helper with “Help defend” targeting the eastern anchor, and message the western player with “Defend from” targeting the 610,000-Troop attacker. These are two direct messages to two recipients, so their cooldowns are independent. Pause: do not spend your 540,000 yet. Watch for the western expansion to stop and for the helper’s line to turn. Evaluate: if 250,000 friendly Troops begin moving east and the attacker drops below 400,000 after contact, the contract succeeded. Your next action is a limited counterpush or “Focus” on the attacker, not another defense alert. If nobody moves after three seconds, send one clearer targeted defense request to the player who actually has the reserve, then commit only enough of your own center to preserve a fallback line.

The assumption matters. If the western player’s 780,000 is already marching across a long front, its displayed total is not an available reserve; the map invalidates the apparent answer. If the fourth player’s 2.6 million Gold is one tick from a Defense Post that covers the anchor, cancelling that spend may be worse than donating. Quick Chat cannot express those constraints, so a sender must phrase the request around the visible outcome and accept that the recipient may have better local information. The stop signal is concrete: once the attacker breaks contact, falls below the anchor’s surviving force, or a different enemy threatens the center, the old defense plan ends.

Scenario two, Ranked 2v2 at 13:30 with a fifteen-minute room finish. Assume your team controls 68% of eligible land, the opponent controls 32%, and the opposing leader holds a narrow 9% peninsula behind one Defense Post. You have 1.9 million Troops and 4.4 million Gold; your teammate has 1.2 million Troops, a Warship screen, and a Transport already halfway toward the peninsula. The opponent’s partner is pushing a low-value island. You have ninety seconds, but a simultaneous full-send can still expose your own core. “Attack” alone is too broad, and “Finish” sent too early may cause both players to dump their reserves before the Transport establishes the second angle.

Run SCOPE again. Scan: the peninsula is the only route that can add decisive durable land before time. Choose: synchronize, then finish. Object: send “Focus” with the peninsula owner as target when the Transport is close enough that the defender can see both threats. Wait for your teammate’s landing line to appear. Then send “Finish” to the teammate, again targeting the same owner, only after your land push can arrive within the same window. Because both messages go to the same recipient, the three-second cooldown is a useful minimum separation; the board condition, not the clock alone, determines the second send. Keep at least 600,000 Troops at home under this assumption, because losing your core can erase more team share than the peninsula gains.

If the Defense Post survives and the defender reinforces to 2.3 million, cancel the finish. The correct follow-up is not a third “Finish” after the cooldown. It is either “Build Warships” if the Transport is being intercepted, “Need Gold” if a specific defensive purchase opens the route, or no message while both players switch to preserving the 68% lead. If the room uses a live territory threshold rather than a hard timer, the same visible numbers require a different decision. Team Victory Threshold owns the exact finish arithmetic; Quick Chat owns the moment when that calculation becomes a shared action.

A smaller coastal example shows why message selection matters. Assume three teammates each have a Port, but enemy Warships are capturing every Trade Ship in one strait. “Need Gold” treats the loss as a funding problem. “Build Warships” identifies the missing capability. “Stop trading” targeting the exposed partner identifies the immediate loss control. The best sequence is stop the route first, ask the safest coastal owner for Warships second, and restore trade only after the screen exists. Team Trade Coordination explains whether the route should return; SCOPE merely prevents three players from buying more Ports while the same strait remains lost.

Failure modes, opponent counterplay, and mode or map adjustments

The first failure is message flooding. Because cooldowns are per recipient rather than global, a caller can technically send several teammates different requests in quick succession. That does not make the plan coherent. Flooding creates multiple “current” targets, forces recipients to guess priority, and makes later corrections indistinguishable from impatience. Counter it with one live request per recipient and one team priority per decision window. If you must contact two players, give them complementary jobs: one defends the anchor while one pressures the attacker. Do not tell both to attack different enemies and then assume the combined result is strategy.

The second failure is an unnamed or stale object. “Attack” without a player asks the recipient to infer a target; “Focus Blue” remains wrong after Blue allies, retreats, or loses the relevant border. Opponents exploit stale plans by showing weakness on one front, reinforcing after the call, and counterattacking the home reserve that already started moving. Re-run Scan and Evaluate when an alliance changes, a player dies, a Warship closes the route, a MIRV becomes ready, or the win timer changes. A three-second cooldown is not a guarantee that a request stays valid for three seconds. State can invalidate the request immediately.

The third failure is treating communication as proof. “MIRV ready” does not prove the launch path beats the SAM screen. “Saving for MIRV” does not reserve another player’s Gold. “Weak” does not prove the target is cheap after defense density, terrain, and third-party benefit are considered. Use Which Nuke to Commit for weapon choice, Land Combat for an active border, and Threat Assessment for the third party. Quick Chat should transmit a decision that survived those checks, not replace the checks.

Opponent counterplay is mostly deception and timing. An enemy can begin a visible attack to attract a defense call, recall it, and hit the reserve’s original front. A player can expose a Port to provoke Warship spending, then move the real fight inland. A leader can let a smaller ally appear weak so your team focuses the wrong color while the leader approaches the threshold elsewhere. The answer is not silence. It is to attach a cancellation condition to every call: defend until the hostile stack turns; focus until the target reinforces; build one screen, not an unlimited fleet; stop trade until one safe arrival proves the corridor. A bounded request is harder to exploit because the team knows when to stop following it.

Mode changes the meaning of the same phrase. In a fixed Team game, direct messages are operational coordination between teammates, and SCOPE can assign complementary work. In Ranked 2v2, the short clock makes confirmation especially important: a request that receives no visible response cannot consume half the remaining match. In 1v1, most messages are diplomacy, warning, or bluff rather than team command; keep your tactical plan independent. In public FFA, in-game alliances and messages can support a temporary live relationship, but prearranged teaming before the match is prohibited by the game’s own reminder. Do not use Quick Chat to recreate an external pact or coordinate hidden permanent collusion. Keep FFA requests tied to an observable current threat and accept that the recipient remains an opponent when the alliance ends.

Map shape changes which phrase carries the most information. On an open continent, a targeted “Defend from” or “Focus” usually beats a generic construction request because multiple land fronts are visible. On an island map, “Build Warships,” “Coastline,” “Help defend,” and “Stop trading” can describe the capability or route that land totals hide. On a narrow strait, name the player on the far side; two nearby colors can share the same water. On compact maps, the three-second cooldown is relatively long because troops cross borders quickly, so send before the collapse is complete and set a smaller goal. On huge maps, travel time is the constraint; do not request a rescue from the teammate whose reserve cannot arrive before the fight ends.

This guide applies to v0.34.20: Quick Chat remains direct, does not execute during the spawn phase, and tracks an approximately three-second cooldown separately for each sender-recipient pair. If the interface, phrase catalogue, or cooldown changes, recheck those details; one bottleneck, one owner, one visible confirmation, and one exit remain the durable contract. Continue with Team Roles for long-lived ownership, Team Trade Coordination for a shared economic lane, and Team Victory Threshold when the call is about ending the match.

Choose the recipient by reach, capacity, and opportunity cost

Selecting the phrase is only half the call. The more important choice is often the recipient, because Quick Chat is direct rather than team-wide. Do not automatically message the player with the largest displayed army. Ask three questions. Can they reach the problem in time? A million Troops across an ocean or behind an impassable corridor may be less useful than 200,000 on the neighboring border. Do they have usable capacity? A player at troop cap can donate, but a player whose army is already inside an attack cannot treat the displayed total as reserve. What do they give up by acting? A rear player may be the only person holding Gold for a Silo, a Defense Post, or a route repair. Moving them can solve one emergency and create a larger one.

Use those questions to rank candidates rather than broadcasting. For a land rescue, prefer the living player with the shortest legal route, a real reserve, and no more urgent contact. For Gold, prefer a player whose current purchase can safely wait and whose balance is visible through their recent behavior, not merely the player who looked rich thirty seconds ago. For Warships, prefer the owner of a protected Port on the relevant water component. For a finish, prefer the player whose troops can add durable scoring land without exposing a larger friendly share. The player with the biggest number is often the wrong recipient because that number may represent an active commitment, not free capacity.

The recipient and the [P1] object are separate identities. If you send a reserve owner “Help defend [Frontline],” only the reserve owner receives that direct exchange; the frontline player named in the sentence does not receive a third copy. If both players need to know the plan, send each a separate appropriate message or use the target marker for an allies-wide map signal. This distinction prevents a common three-player failure: the rescuer starts moving, the frontline assumes nobody responded and retreats, and the two actions miss each other. One short confirmation to the frontline after the rescuer moves is more valuable than another plea to the rescuer.

Opportunity cost also sets the stop condition. If a player must cross two fronts to help, tell yourself in advance what event makes them turn around. If a donor gives 1.5 million Gold, name the purchase that justifies it and do not ask again until that purchase resolves. If a coastal owner builds one Warship screen, prove the lane with a completed arrival before requesting another level. These limits let the recipient reject a bad request without breaking team trust. A useful caller selects the person most able to change the bottleneck, not the person most likely to obey.

On large teams, create an informal routing order. Contact the adjacent owner first, the central reserve second, and the economic rear only if the first two cannot solve the problem. On small teams, contact the player whose move complements yours: if you can hold, ask them to pressure; if you can pressure, ask them to hold; if neither can do both, stop the plan. This approach turns direct delivery from a limitation into a strength. Each message reaches a player chosen for one reason, and every other player remains free from an alert that does not belong to them.

Sequence messages as phases instead of stacking commands

A plan can contain several good commands and still fail because they arrive in the wrong order. “Stop trading,” “build Warships,” “send Troops,” and “finish” may all be correct over one minute, but they conflict when sent together. The route owner cannot preserve Gold, build a fleet, donate a reserve, and full-send at once. Sequence the plan into phases with a visible transition. Phase one contains the action that prevents immediate loss. Phase two creates the missing capability. Phase three spends the saved position on the objective. A new message begins only when the map proves the previous phase completed or failed.

For a collapsing coast, the sequence is loss control, screen, proof, scale. First send “Stop trading” to the exposed partner so new ships stop feeding captures. Next ask the safest Port owner to “Build Warships.” Then wait for the enemy fleet to move or for one friendly Trade Ship to complete a route. Only after that proof should the team restore trade or add a second ship. Sending all four ideas at once hides causality: if the lane recovers, nobody knows which action mattered, and if it fails, everyone has already paid.

For a land focus, the sequence is pin, angle, commit, cancel. One player holds enough pressure that the defender cannot leave. A second player approaches a distinct border. The caller sends “Focus” only when both angles can matter together. The heavy push follows after the defender moves, and the plan cancels if reinforcement closes the cheaper angle. “Finish” belongs at the commit phase, not at the first sight of weakness. The three-second recipient cooldown provides a natural gap between phrases but does not define these phases. A Transport may need twenty seconds to arrive; an exposed border may disappear in one. Board state is the clock.

For a nuclear plan, the sequence is reserve, verify, fire, exploit. “Saving for MIRV” tells one recipient why Gold should remain liquid; it does not prove a launch. Before “MIRV ready” or a targeted MIRV instruction, verify the Silo, current price, target value, likely SAM coverage, and land force that can exploit the strike. After launch, communication switches from weapon to territory: the team must know who captures, who guards the home reserve, and what ends the push. A nuclear message without an exploitation owner produces spectacle rather than control.

Use acknowledgments sparingly. The best acknowledgment is the requested movement. If a textual answer is needed, make it change the plan: “Thanks” can close a rescue request, “Need Gold” can reveal the chosen helper lacks the required resource, and “Build closer” can explain why a route cannot yet work. Do not create an acknowledgment loop where both players spend every cooldown proving they saw the other. One request, one board response, and at most one closing signal preserves attention for the game.

When a phase fails, do not leap forward. If trade has not stopped, more Warships may subsidize the same leak. If the second land angle never appears, a finish call becomes a solo full-send. If the Gold reserve disappears, MIRV planning returns to ordinary defense. Sequencing makes these failures cheap because the team has not prepaid later phases. It also makes public teammates easier to read: even without voice, each completed action narrows what the next message can reasonably mean.

Separate Quick Chat, Emoji, and the allies-wide target marker

OpenFront offers several social signals, and treating them as interchangeable causes avoidable errors. Quick Chat sends a fixed translated phrase directly to one recipient, sometimes with a third player named inside it. Emoji are compact social signals whose meaning depends heavily on context. The target marker is the shared map signal that the official help describes as visible to all allies. Choose the channel based on the uncertainty you need to remove. Use Quick Chat for an action or warning assigned to one person. Use the target marker when every ally needs to see the same map priority. Use Emoji for tone, acknowledgment, celebration, or diplomacy when ambiguity is acceptable.

The community’s emoji discussion shows why a heart cannot carry a rescue plan. It may mean friendship, thanks, mercy, manipulation, or desperation. The same ambiguity can be useful in diplomacy because it leaves room for interpretation, but it is harmful when a border will fall in five seconds. A fixed “Help defend [Player]” phrase narrows the action and identity. It still cannot express the route, quantity, or stop condition, so the map supplies those. The correct lesson is not that Quick Chat is perfectly precise; it is that it removes one more layer of uncertainty than an icon.

The target marker solves a different problem. If four allies must pressure the same leader, sending four direct “Focus” messages assigns four private tasks and consumes four attention events. A visible allies-wide target can establish the shared object once, after which direct messages assign complementary jobs to the specific players who need them. Mark the leader, tell the adjacent player to hold, tell the naval player to threaten the coast, and leave the economic rear unmessaged unless funding becomes the bottleneck. Shared marker for priority, direct phrase for ownership is the clean division.

Do not confuse interface controls either. The official settings bind AltLeft to the Emoji menu, not to a dedicated Quick Chat shortcut. Quick Chat is reached through the player interaction flow: right-click or touch a player, open player Info, then Chat, or use the Player Panel Chat action. That interaction cost matters. On a compact front, opening a modal after collapse begins may be too slow; send the request at the first clear signal rather than at the final tile. On mobile, select the correct player carefully because the recipient, the player named as [P1], and the player focused when clicking the event can be different roles.

There is a useful escalation ladder. Start with the least disruptive channel that can remove the uncertainty. Use an Emoji when only tone matters. Use a target marker when all allies need one shared object. Use direct Quick Chat when one player needs an action or warning. Use visible unit movement as the final confirmation. Do not escalate merely because the recipient has not replied in text. If their army turns, the request succeeded. If the board cannot show the requested action, one direct clarification is justified; after that, redesign the plan around non-response.

This separation also protects trust. Social warmth does not become a command, a marker does not become proof that everyone committed, and a direct request does not pretend to be team consensus. Players can disagree without interpreting every icon as betrayal. In a public team, where no shared voice or prior plan exists, that clarity is more valuable than message volume. Each channel does one job, and the map remains the common source of truth.

Practice the protocol with a one-minute decision drill

The fastest way to improve Quick Chat is to rehearse the decision before a high-stakes match. Use a replay, spectator view, or a low-pressure Team game and run a one-minute drill without trying to call everything. For the first fifteen seconds, identify the single border, route, or timer that can change the team’s outcome soonest. For the next fifteen, list the players who can reach it and eliminate anyone whose displayed resources are already committed. In the third block, choose one phrase and one object. In the last fifteen seconds, state the visible confirmation and cancellation condition before sending. If you cannot name both, the call is not ready.

Score the drill on five binary checks. Problem: could another viewer point to the same bottleneck? Recipient: can that player physically and economically act in time? Phrase: does it remove the important uncertainty instead of merely expressing urgency? Object: when required, is [P1] the threat, beneficiary, or objective rather than the recipient by habit? Exit: can you name the map change that ends the request? Four out of five is usable. Three or fewer means hold the message and keep scanning. The score is an editorial training tool, not an in-game mechanic, but it turns vague “better communication” into repeatable review.

After the match, inspect only three moments. First, find the earliest frame where the bottleneck was visible. If you sent later, the communication problem may actually have been recognition. Second, find the first map response after the message. If you assumed agreement before that frame, the problem was confirmation. Third, find the moment the plan stopped being valid. If you continued repeating it, the problem was cancellation. This review fits naturally with Replay Review, but it focuses on the message lifecycle rather than the whole match.

Keep a compact checklist beside the SCOPE framework: one priority, one responsible recipient, one named object, one confirmation, one exit. Do not add a sixth item for “send again.” Repetition is an outcome only when the first delivery failed technically, and the official execution gives no read receipt that proves such failure. In normal play, a second identical phrase after three seconds is more likely to add noise than information. A follow-up should reflect a changed map: defend became focus, stop trade became build Warships, saving became ready, or finish became cancel.

The drill also reveals when Quick Chat is the wrong tool. If the action needs a precise troop count, coordinate, time, or multi-step contingency that the shared map cannot supply, the fixed phrase catalogue cannot carry it. Simplify the operation until one visible action is enough, use the allies-wide target marker for the common object, or avoid a plan that depends on strangers reproducing hidden detail. Public-team strategy should degrade gracefully when communication is incomplete.

Finally, judge success by decisions changed, not messages sent. One early defense request that preserves an anchor is better than twenty reactive warnings. One trade stop followed by a proven Warship screen is better than constant requests for Gold. One synchronized finish is better than repeated calls against every weak color. Quick Chat is strongest when it disappears after doing its job: the team sees the same bottleneck, acts, confirms the new state, and moves on.