OpenFront In-Match Gold Donation: When to Send Gold Instead of Troops

Direct answer: send gold to a living ally who can spend it, troops to one who can hold it

Donate gold to a friendly teammate when that teammate is alive, is a human, and has a specific thing to buy with the gold in the next few seconds — an expansion, a City, a Factory, a Port, or the workers that keep their income flowing. Donate troops when the teammate is losing a border and needs bodies, not money. The two actions share the same radial menu and the same 10-second per-target cooldown, but they fix different problems. The core decision is which ally and which resource, not whether to give at all. If you can name the purchase the gold will fund, send gold; if you cannot name it and the ally is bleeding, send troops instead. A teammate who is already dead, a bot, or an enemy cannot receive either one, so the menu entry is disabled and the question never arises. The 10/25/50/75/100 presets exist so you decide the share of your own balance in one glance, which matters more than the exact number.

The reason this is framed as a decision about who and what rather than how much is that the number is the easy part and the target is the expensive part. A perfect 50% gold donation to the wrong ally is worth less than a sloppy 25% to the right one, because the gold only pays off if the recipient has a specific purchase it can turn into within the next few seconds. If you cannot name that purchase, the donation is usually a gift to the enemy, because the recipient either cannot spend it fast enough or dies before the income it was meant to buy. The whole guide is built around that one idea: a gold donation is a bet on the recipient’s next move, and a troop donation is a bet on their next ten seconds. Get the bet right and the preset barely matters; get it wrong and even the 100% button only accelerates the loss.

This is also why the two buttons should feel like different questions, not the same button with two labels. When you open the radial on an ally, ask yourself the troop question first: is this person about to be killed in the next ten seconds? If yes, troops, and the gold question never gets asked. Only when the answer is no do you ask the gold question: does this person have a named purchase that my gold would fund within the next few seconds? If both answers are no, the correct move is usually to send nothing and keep your balance liquid, because a donation with no target purchase is just your own expansion slowing down with a stranger’s name on it. The community threads that ask “why do teammates hoard” are almost always describing this exact absence of a named purchase, not greed, and the fix is to make the purchase explicit before you tap the preset.

Where the action lives and why so many players miss it

Both donations sit in the radial menu that opens when you select another player. There are two entries, donate gold and donate troops, each shown in the ally color and each disabled whenever the underlying canDonateGold / canDonateTroops check is false. Tapping one opens the shared send-resource modal, which lists your living allies, shows your current gold or troop balance as the basis, and offers the 10 / 25 / 50 / 75 / 100 % presets plus a fine slider for an exact figure. This is where the community problem starts: multiple Reddit threads describe players who “took a couple minutes of frantic searching to figure out how to send money or troops” because the action is tucked behind the player’s information panel rather than a hot key, and at least one player “had to watch a video before I knew that it was even an option.” The fix is to make the radial menu a reflex: select a living ally, open the radial, pick the resource, pick a preset, confirm. Because the presets are percentages of your balance, the same 50% button moves a different amount at minute three than at minute twelve, so you are really choosing “half of what I have right now,” which is the honest mental model.

Worth naming, because it changes how you practice: the modal shows your current balance as the basis, and the presets recompute from that basis every time you open it, so there is no hidden “last amount” state to remember. The slider is for the rare moment when you want an exact figure — usually when you know the price of the build the recipient is queuing and you want to match it rather than round to a preset. In a fast team game you will almost always be choosing the 25% or 50% presets and moving on, which is exactly why the feature works at all: it compresses a four-step calculation (balance, price, share, confirm) into a single glance and a single tap. The players who miss it are not missing it because it is hard to use once you find it; they are missing it because it is not where their attention already is. That is a habit problem, not a UI bug, and the practical fix is to build the reflex during the calm opening minutes — send a 10% gold preset to a teammate who clearly has room — so that by the time the front breaks, the action is already muscle memory instead of a search.

The rules that actually make a donation possible

Before any of the decision-making, the engine enforces four hard gates, all in canDonateGold and canDonateTroops in PlayerImpl. Human-to-human only: the config comment is explicit that donations are configured for humans only, so a human cannot donate to a bot and a bot’s donation does not move; bots also start at zero gold, so there is nothing to receive. Both alive: the modal computes its basis as zero the instant the sender or the target is dead, and the presets gray out. Friendly target: the recipient must share your team or be allied; you cannot donate across a hostile border. Per-target cooldown: each (donor, recipient) pair keeps its own 100-tick timer for gold and a separate one for troops, so after giving gold to the frontline anchor you can immediately give gold to a second feeder — the cooldown is per recipient, not global. The game runs at ten ticks per second, so 100 ticks is exactly ten seconds. These gates are not optional and not mode-dependent the way some switches are; they are the shape of the feature, and understanding them tells you exactly when the button is grey and why.

The practical consequence of these gates is that a donation is only ever a transfer between two living human teammates, and the moment one of them dies the button grays out for everyone. This is why the timing of a donation is almost as important as the target: you cannot pre-queue a gift to an ally who is about to die, and a troop donation you sent seconds before they died is spent on a nation that no longer exists. It is also why the per-target cooldown is the part that rewards experience. Because the timer is per (donor, recipient) pair and separate for gold and troops, an experienced player keeps a mental rotation of two or three recipients and never wastes a full ten seconds waiting on the same ally when another one is now the one who needs help. The human-only rule is the one that surprises new players most, because the game happily fills a team with bots in the meantime, and the instinct to “help” a bot is exactly the one the engine refuses. If the radial entry is grey on a specific player, the cause is almost always one of these four gates, and checking them in order — alive, friendly, human, cooldown — takes less than a second and prevents the wasted hunt for a button that is correctly hidden.

The decision framework: who gets gold and who gets troops

Use a four-question call in order, because answering them in a different order produces the most common mistakes. One: is the ally alive and friendly? If no, stop — the action is disabled. Two: what do they need in the next ten seconds? If they are losing a border to more troops than they have, they need troops; if they are alive and safe but stuck (no workers to fund income, no City to unlock the next tier, no Port for a water lane), they need gold. Three: can they actually spend it before it is wasted? A feeder sitting on a huge gold balance who already has full workers cannot “use” more gold income, so a gold gift there is pure storage; a frontline player with no gold cannot buy a defensive post, so a gold gift there is a delay, not a fix. Four: what is the opportunity cost of your own balance? Your donated gold is gone and your own expansion slows; the presets exist so you can keep 75% of your balance (the 25% preset) when the team is still early and the 100% preset when you are committing to a final push. The frame that changes the call most often is gold funds production, troops hold territory: a gold donation buys the ally’s future income, a troop donation buys their current survival. Send gold to the player who will convert it into more troops and land over the next minute, and troops to the player who will be overrun in the next ten seconds.

One more refinement that keeps the framework honest: the four questions are a filter, not a ranking. A teammate can pass the first three (alive, friendly, has a named purchase) and still be the wrong target if the fourth says your own balance is the team’s critical resource right now — for example, you are the one who can buy the Factory that unlocks the whole backline, and spending that gold on a feeder means the backline never builds. In that case the correct move is to keep your gold and let the feeder survive on a smaller 10% top-up. The framework is there to catch the two failure directions at once: giving gold when troops are needed, and giving anything when the right move is to keep it.

The numbers that shape the call: cooldown, presets, and unlimited gold

Three concrete numbers do most of the work here. The cooldown is 100 ticks, or 10 seconds, per recipient and per resource, so with two or three living teammates you can keep a rotation going — anchor, feeder, edge — and each gets a full donation roughly every ten seconds while you cycle. The presets are 10 / 25 / 50 / 75 / 100 % of your current balance, which means the same button is a trickle in the mid-game and a commit in the late game; the slider lets you dial an exact figure when you are matching a known price. Gold has no recipient capacity cap — the modal’s own comment says “Internal capacity only for troops; gold is unlimited” — so you can empty your balance into a single ally, whereas a troop donation is clamped by the recipient’s troop capacity and the surplus is lost. This asymmetry is the whole reason the two buttons exist: troops are a buffer the ally might not have room for, gold is liquid the ally can always absorb. Practical reading: if you are unsure, a 25% gold preset to a feeder costs you a little expansion speed and buys them a worker or a small build now; a 100% troop preset to a maxed-capacity ally silently throws most of it away. Check the recipient’s headroom before you confirm a troop transfer, and lean on gold when you cannot check quickly.

A useful way to internalize the cooldown is to think of it as a rotation budget, not a penalty. Ten seconds per recipient means that with three living teammates you can complete one full cycle of donations roughly every thirty seconds, which in a normal team game is plenty of time to keep the front supplied and the backline funded without ever feeling rushed. The trap is treating the cooldown as a reason to send everything to one ally as fast as possible; the cooldown exists precisely so you do not, because a single ally who receives 100% of your output twice in a row is usually a single point of failure. The presets compound this: because they are percentages, the later you are in a match the more a 25% gold preset is actually worth, so a feeder who receives 25% at minute four gets a trickle and one who receives 25% at minute twelve gets a build. That is the intended reading — early game donations should be small and frequent, late game donations should be large and committed — and the 10/25/50/75/100 spread is the tool that makes both halves of that sentence true at the same time.

Scenario A — the protected feeder who should pump one steamroller

Assume a six-player Team game on a large map, minute eight. One teammate (the “anchor”) holds the front against two enemy players and is at about 30,000 troops against a combined ~45,000 pressing in. Two of your teammates are safe in the back with strong gold income but low troop counts; one of them (the “feeder”) has 90,000 gold and full workers but only 8,000 troops. The anchor is alive, friendly, and losing. Call it: the anchor needs troops now, not gold, because the threat is in the next ten seconds — so you open the radial on the anchor and send the 50% troop preset, which at your current balance is roughly 12,000 troops, and repeat after the 10-second cooldown. The feeder does not need troops yet; the feeder needs to convert that 90,000 gold into more troops and a Factory to keep up the rotation. So you send the feeder a 25% gold preset to nudge their worker ratio and let them queue a Factory, which raises the ceiling of every future troop donation you can make. You never dump your own gold onto the anchor mid-fight, because the anchor’s problem is bodies and gold there only delays the fix. The rotation is: anchor gets troops on a 10-second cadence, feeder gets a small gold top-up to keep the pipeline, edge player keeps expanding to deny the enemies a second front. This is the “pump a single player into the designated steamroller” shape that good team games repeat, and the gold goes to the player doing the pumping.

Notice what the gold is not doing here. It is not rescuing the anchor, it is not even directly buying the anchor’s next troop burst — the anchor’s burst comes from the feeder’s own income, which the feeder now has more of because a Factory is being queued. The gold is an accelerator on the pipeline, not a fix for the immediate front. That distinction is the whole reason this scenario works: the immediate front is solved by troops (50% preset, repeated on the cooldown), and the medium-term front is solved by gold (25% preset, one time, into the Factory). If you reversed it — dumping gold onto the anchor and leaving the feeder at 8,000 troops — the front would hold for the next thirty seconds and then collapse, because the feeder never built the Factory that makes the next thirty seconds possible. The “designated steamroller” reading from the community threads is exactly this: one player becomes the team’s main threat, and the other players exist to keep that player alive and funded, which is a different job than the steamroller’s job of being the threat. Gold goes to the players doing the different job.

Scenario B — the ally about to be overrun: gold or troops, fast

Now the same map, minute twelve. A teammate (the “edge”) has drifted onto a corner with no exit, is at 4,000 troops facing 60,000 enemy troops across two borders, and has 15,000 gold with workers at 20%. The honest read is that this ally is losing and a gold donation will not save the border in the next ten seconds — the gold can buy one worker or a small post, not a 56,000-troop deficit. The call is troops, large and repeated: 75% of your troop balance to the edge, then the 100% preset after the cooldown, accepting that some of it is lost to capacity if the edge is already near full. If you can also name a future purchase the edge will make the moment the front stabilizes — a Port on the coast behind them, or a City to raise the income — then after the troops have bought the ally time, a 25% gold preset to that edge funds the rebuild instead of letting them sit at 20% workers forever. The failure this scenario prevents is the “save them with money” reflex: when the deficit is in troops, gold is a delay fee, not a rescue. The reverse failure is equally real — if the edge’s problem were only that they had no workers and no income, then troops alone would bleed out as their income stayed at zero and the gold-to-workers call would have been the right one. Decide which number is the deficit, and the resource follows from it.

The reason the “which number is the deficit” question matters is that the modal does not do the arithmetic for you. The 10/25/50/75/100 presets are percentages of your balance, not percentages of the recipient’s deficit, so the same 75% troop preset is a rescue on a small deficit and a gesture on a 56,000-troop deficit. That gap between preset and need is exactly where experienced players out-rotate the rest of the team: they are estimating the deficit in real time and choosing the preset that closes it, or knowing the preset is insufficient and sending a second one after the cooldown. The 10-second per-recipient cooldown is the only thing that keeps this from becoming a flood, and it is generous enough that a correct read of the deficit, a first preset, and a second preset on the next tick all fit inside a single wave of enemy pressure. The trap is the opposite one: a player who sees a small deficit and still sends 100% because “they’re losing,” which empties your own balance into a recipient who needed 10% and leaves you with nothing when the next — larger — deficit appears on a different ally. In other words, the gold/troops call and the preset size are two separate decisions, and both have to be right, which is why the guide treats them as two steps rather than one.

Failure modes and the counter that undoes each one

The first failure is feeding a doomed ally with gold: you hand 50% of your balance to a player who is about to die, the gold vanishes with the nation, and your own expansion stops. The counter is the one-second test — if the ally’s troop deficit is larger than what your gold can buy workers for, send troops or do not send at all, and redirect the gold to a safe feeder. The second failure is capacity waste on troops: you send 100% troops to an ally already at troop capacity and the surplus is discarded, so the donation did nothing while your own front thinned. The counter is to check the recipient’s headroom and prefer the gold preset, which has no cap, when you are unsure. The third failure is cooldown tunneling: you give everything to one ally, wait ten seconds, and discover the second ally is now the one being overrun; the per-target cooldown exists so you can cycle, and the counter is to keep a mental rotation of two or three recipients rather than a single favorite. The fourth failure is opportunity cost blindness: you empty your balance so fast that you cannot fund your own City or Port and become the next ally who needs saving; the 25% and 50% presets exist to keep you liquid, and the counter is to treat 75–100% presets as commits you make only when the team’s endgame is clear. The fifth failure is misreading the human-only gate: you try to “help” a bot teammate and find the button grey, which wastes a moment in the moment that mattered; the counter is to remember that bots cannot receive, so every donation targets a human.

Each of these five failures has the same underlying shape, which is worth naming because it predicts the sixth: you optimized for the visible number (your balance, their deficit) instead of the invisible one (whose income, in the next ten seconds, the gold actually moves). The first failure optimizes for “they’re losing” without checking what losing means in troops versus workers. The second optimizes for “send the most” without checking that the most can be received. The third optimizes for “help my favorite” without checking the rotation. The fourth optimizes for “empty my balance now” without checking that the empty balance becomes the next deficit. The fifth optimizes for “help someone” without checking that someone is a human. The sixth, which the first five almost guarantee, is the donation that looks correct from your own screen and is a pure loss from the team’s screen: you saved a player who was about to die but in doing so you became the player who is now about to die, and the team’s total troop count is lower than before you started giving. The only counter to that sixth failure is the one the whole guide keeps returning to — keep a 25% or 50% reserve and only commit 75–100% when the team’s endgame is already decided, so that a donation can never be the thing that turns you from the team’s helper into the team’s problem.

Mode and map adjustments

In Team mode every one of the above applies, which is the default context. In modes that do not put you in a shared team, the friendly-target gate means there is no one to donate to and the question disappears, so this guide is about the multiplayer team shape. On small maps the per-target 10-second cooldown matters less, because allies die faster and the rotation is short and brutal — lean on troops and short 25–50% gold top-ups, and do not over-commit a 100% preset early. On large maps with a protected backline, the feeder model from Scenario A is the whole game: a safe player with strong gold income converts gold into troops over minutes, and the gold donations there are about accelerating the conversion (a Factory, a Port, a worker burst) rather than about the emergency. On island or strait maps, a Port is often the single most valuable gold purchase a teammate can make, so the gold donation that matters is the one that lets the coastal ally buy that Port and open the water lane; the troop donation is the one that protects the land bridge while the Port is built. The decision is the same either way — name the purchase or the deficit — but the purchase that wins the game changes with the topology, so Map Strategy is the reference for which component the gold should buy on your specific map.

One mode-specific note that the community threads keep returning to is the lobby default: whether donations are on at all is decided by the game configuration, and the in-match action is only as useful as the toggle that enabled it. In practice this means that the same team of players behaves differently in a lobby that has donations on versus one that does not, because the rotation, the feeder model, and the “pump one steamroller” plan all assume the action exists. If you are hosting, the toggle is part of the game you are offering, not a cosmetic setting; if you are joining, reading the lobby’s donation state before the match is the difference between a team that can coordinate a front and one that can only react to it. This is also the setting that the “my teammate hoarded and I couldn’t help” complaints are about, so if a community thread complains about a missing donation, the first question is whether the lobby had the action enabled in the first place. The rest of the guide assumes it is on, because every scenario depends on the radial entry being live.

What this guide does not cover, and what to read next

This guide owns the in-match gold donation decision: who gets gold, who gets troops, how the 10-second per-target cooldown and the 10/25/50/75/100 presets shape the call, and how to stop feeding a doomed ally. It deliberately does not cover the Clan Treasury, which is a stored pool you contribute to and draw from between matches — a different system with its own rules — or the general donation switch and cooldown framing that the team-roles page uses when describing role handoffs. If you want the stored, between-match pool, read Clan Treasury Donations. If you want the broader role and logistics framing — who feeds whom, who anchors, when to mark targets — read Team Roles. For the economic side of what your donated gold should actually buy — workers, Cities, Ports, and the income they produce — read Team Economy and Space. For the moment after the donations have bought you time, First Match covers how to convert the early position into a stable opening. The in-match gold donation has done its job when a living human teammate spends your gold on a purchase you could name before you sent it, and the next ten seconds got better for the team.

A final note on why the “read next” list is ordered the way it is: the four linked pages answer the four questions that follow directly once you have mastered the in-match call. The Clan Treasury page answers “what do I do with the gold I bank between matches,” which is the other half of the gold economy that the in-match button cannot touch — the treasury is a stored pool with its own rules, and the two systems only interact in that a strong in-match economy is what lets you bank enough to matter. The Team Roles page answers “who is the feeder, who is the anchor, who is the edge,” which is the question your gold is implicitly choosing every time you pick a target: a donation is a vote on a role, and a team where everyone votes for the same role ends up with one steamroller and no one to protect it. The Team Economy and Space page answers “what should the gold actually buy,” because a gold donation that lands on a teammate with no idea what to build with it is a donation that buys nothing, and the worker/City/Port arithmetic on that page is the reference for the purchase you are supposed to be naming before you tap the preset. The First Match page answers “what do I do with the position the donations just bought me,” because a front held by a 50% troop preset is only as good as the opening that follows it, and the early-game conversion from a temporary advantage into a stable map position is a different skill from the donation itself. The in-match gold donation is the bridge between those four skills, and it is only as good as the skills on both ends of the bridge, which is why this guide ends by pointing at all four rather than pretending it covers the whole team economy on its own.