Clan Treasury Donations: Step-by-Step OpenFront.io Guide

Direct answer: the treasury is a one-way, member-gated donation

A clan treasury donation moves currency from your own account wallet into your clan’s shared balance, and it is permanent: the API “never credits a clan balance back to a player,” and the dialog tells you the same thing in plain words — “Donations are permanent and non-refundable. Currency given to the clan can never be returned to you.” You open the overlay from the clan screen, pick one of two separate pools, type a whole number, and confirm. The two pools are soft, the amber caps you earn by playing, and hard, the green plutonium that is premium currency you typically buy with real money. Each pool has its own balance on the clan card and the clan modal, and each donation is recorded in a members-only history you can read at any time. The action is gated: if you are not a member of the clan, the request returns a 403 and the dialog shows “You must be a clan member to donate.” You do not need to be an officer, you only need to be inside, which means the gate is a membership gate, not a role gate.

This is the part of the answer that changes the decision most, because most players hit the overlay thinking of a different feature. The treasury is not the in-match ally donation that hands gold or troops to a teammate inside a game lobby. Those are different strings, different screens, and a different decision entirely, and the community mixes them up constantly. The treasury overlay is labeled “Move currency from your account to the clan treasury”; the in-match strings are “Donation,” “Send 100,” “Send 500,” “Max.” If you are deciding whether to press the treasury button, the facts that matter are four, not one: it cannot be undone, it is idempotent so a dropped connection cannot double-spend you, the plutonium path carries an extra warning the caps path does not because plutonium is real money, and the amount is a whole number the overlay validates before you send. Put those four facts in your head before you look at the number you are about to type, because each one removes a different kind of regret: the no-undo fact kills the “I will change my mind later” plan, the idempotent fact kills the “did that double-charge me” panic, the plutonium warning exists to slow down the real-money path, and the whole-number validation exists to stop you from sending a value the ledger cannot represent cleanly. The rest of this guide exists to put the right numbers in front of you so you make that decision deliberately, in one currency you can afford to lose, rather than by reflex.

What the treasury actually is, and what it is not

The cleanest way to avoid the single most common mistake is to separate the treasury from the in-match donation, because both use the word “donate” and the community conflates them in nearly every thread that mentions “donating to the clan.” The treasury is an out-of-match, persistent feature. It shipped in v0.34.0 (commit 0a4302a0, PR #5041) and is still unchanged in the current release v0.34.16, which is a telemetry-only patch that touched none of this. It has a dedicated overlay, a members-only donation history, and a balance that the clan card and the clan modal both display. The balance is stored as a decimal string rather than a number, and the schema flags this explicitly because the value can exceed the largest integer JavaScript can represent safely; it is "0" when the clan has nothing pooled. That detail is not trivia: it is why you should read the balance field rather than try to do arithmetic on it in your head.

The in-match donation is the other feature. It is the donateGold and donateTroops actions in the in-match radial menu, the ones a team-game guide tells you to spam for a frontliner or a backliner. Those move gold or troops between players inside one game lobby, they reset the moment the lobby ends, and they have nothing to do with the treasury balance on the clan card. The i18n strings make the split unambiguous, which is the whole reason to be careful: when a post says “I donate to the clan,” you now have to ask which of the two it means, because the answer changes the entire decision you are making. The in-match donation is a lobby economy move with a short half-life; the treasury is a persistent contribution to a shared balance that outlives any single match.

A second, subtler distinction is between the balance and the donation ledger. The donations endpoint lists only donations that players made. The schema comment is explicit that the clan’s win-share cut, admin adjustments, and refund reversals are separate ledger reasons that endpoint excludes, which means the sum of the donation list is not the clan’s actual balance. The real balance is the softBalance and hardBalance fields on the clan info object. In practice this matters for exactly one thing: do not hand-add up the donation history to figure out how much the clan has pooled. Read the balance fields, and treat the ledger as a record of member contributions, not a running total.

Feature	Treasury donation	In-match ally donation
Where it happens	Out of match, clan screen overlay	Inside a game lobby, radial menu
What moves	Your account’s caps or plutonium	Gold or troops between players
Persistent?	Yes, until spent	No, resets when the lobby ends
Member-gated	Yes (`403` if not a member)	No, any lobby teammate
Currencies	`soft` caps / `hard` plutonium	Gold / troops
Reversible?	Never, non-refundable	Not “reversed,” just ends with the lobby
Double-spend on retry	No, idempotent per dialog open	N/A
Balance displayed as	Decimal string (BigInt)	Plain in-match counters

When donating is the right call

The treasury only makes sense inside a clan that is real and ongoing, so the first filter is not the currency, it is the clan. A clan that is one or two players who added each other, that has no Discord, and that disappears from the leaderboard the week you stop playing, is the wrong container for a one-way donation, no matter how much idle surplus you are sitting on. The community threads make this concrete: the durable clans are the ones that run through a Discord server, the ones whose leaderboard rank is a win/loss ratio rather than a point total you can farm, and the ones where you can name the other members and know they are still playing. If your clan clears that bar, the next filter is the currency, and this is where the decision actually branches, because the two pools have very different cost structures.

Caps donations are the safe default, and they should be most of your donations. Caps are the earned, amber currency; you generate them by playing, and donating a block of them is a transfer of surplus that costs you nothing you could not earn back. The whole-number input and the “insufficient balance” 400 error are the only real guardrails on the caps side, and the downside of a bad caps donation is a slightly slower personal economy, not a hole you cannot refill. A reasonable caps rule is to donate only the surplus you would otherwise let sit idle — the caps you are not going to spend on your own upgrades this week — and to do it in a single deliberate number rather than a stream of small ones. One clean whole number is easier for the clan to account for and easier for you to justify than a dozen tiny transfers that blur the line between “donating” and “wasting.”

Plutonium donations are a different animal, and the UI is honest about it: the hard-currency path carries a warning the caps path does not, “Plutonium is premium currency. Once donated it cannot be refunded, withdrawn, or moved back to your account.” Plutonium is the green currency you typically buy with real money, so a plutonium donation is spending money you already paid for, into a pool you cannot get back, in a clan that may not outlive your patience. The only defensible plutonium donation is a small, deliberate, one-time top-up to a clan you have already verified is durable — a contribution you are genuinely willing to lose entirely if the clan dissolves next month. If you are on the fence, the decision resolves itself: when in doubt, donate caps, not plutonium, because caps are replaceable and plutonium is not. The decision rule is not “is a donation good,” it is “which currency am I willing to lose, and is this clan worth losing it.”

Version boundaries and what is verified

Being precise about the version boundary is part of the decision, because the treasury is new and a large share of community content predates it. The donate overlay, the donateToClan API, and the members-only donation history all shipped together in v0.34.0, and the current release v0.34.16 is a telemetry-only patch that made no change to any of it. The practical consequence is a hard line: if you are on anything v0.34.0 or newer, you have the full feature and everything in this guide applies to your client; if you are on v0.33 or earlier, you do not have this overlay at all, and there is no treasury to donate into on that build. The high-view community tutorials are v27, v28, and v31, which is exactly why none of them cover the treasury — they were recorded before it existed. That gap is not a coincidence, it is the version boundary doing its job, and it is also the reason you should not trust a “treasury” video that predates v0.34.0 as a source for how the feature behaves today.

Within v0.34.x, the verified mechanics are the ones in the open-source client, and they are the load-bearing facts of this guide: the one-way non-refundable transfer, the idempotent retry, the soft/hard split, the members-only 403, the whole-number validation, and the 400 on insufficient balance. What is not present in the open-source repo at v0.34.16 is the server-side spend path — the code that actually consumes the pooled treasury balance for something. The client defines how you deposit and how the balance displays, and the schema even names the other ledger reasons (win-share cut, admin adjustments, refund reversals), but the open repo does not expose what the clan does with the pooled currency in-match. This is the one thing this guide will not assert for you, and it is the honest gap in the feature’s documentation.

So “exactly what does the treasury buy the clan in a match?” is the single question you should confirm with your clan leader or in the live game, rather than assume from a guide. That does not make the treasury useless or the donation pointless — it makes it a social and economic commitment first, with the in-match effect being the part you verify locally. Everything else in this guide is pinned to a version you can check in the source, and the one open question is the one you should close by asking the people in your specific clan, because the pooled balance is only as clear as the clan that holds it. Treat the version boundary as a filter and the spend path as a question, and you will not make a donation on the basis of a tutorial that predates the feature.

Scenario 1: a durable ranked clan, surplus caps, no plutonium to spare

Assume the situation the community threads describe as the healthy end of the clan spectrum: you are in a clan with eight named members, a Discord, and a leaderboard rank you can see moving up over a stretch of about two hundred games. The ratio is steady, the members are real people you can name, and the leader answers when you ask. You have roughly six thousand caps sitting idle — more than you will spend on your own upgrades this week — and you have zero plutonium you are willing to lose. You open the treasury overlay and the question is what to do with the idle block.

The decision is straightforward and you should make it fast, because a healthy surplus of the earned currency is the exact condition the treasury was built to absorb. You donate the surplus caps in one whole number, not in drips. The whole-number input exists for exactly this: a single deliberate transfer is easier for the clan to account for than a dozen small ones, and the idempotent design means that if the connection drops the moment you hit send, the retry “replays the original 201 without moving more currency,” so you cannot accidentally donate the six thousand twice. You do not touch the plutonium pool, because you have nothing to donate there and, more importantly, because the decision rule is the same whether or not you have plutonium — when you have a healthy surplus of the earned currency, that is the currency you pool. The caps donation costs you a slightly slower personal economy next week, which is fine, because those caps were idle surplus anyway, and the cost is recoverable by playing.

The concrete check before you hit send is: is this the surplus I will not spend this week? If yes, donate the whole block. If you find yourself hesitating about the number, drop it by a quarter and donate the rest next week — the treasury is a recurring decision, not a one-time event, and a slightly smaller first donation is the safer way to calibrate your sense of what the clan actually uses over a stretch of play rather than what you think it will use. The failure to avoid in this scenario is the opposite of under-donating: it is treating the treasury as a place to dump caps you actually needed for an upgrade, so that the “idle surplus” was not idle at all. If the six thousand was load-bearing for a planned upgrade, donate the amount you will genuinely not spend, and leave the rest where it is. The treasury absorbs true surplus; it should not create a deficit. A useful way to test the surplus is to ask whether the upgrade you are tempted to buy with those caps is time-sensitive this week — if it is, keep the caps; if it can wait a week, the surplus is real and the donation is safe.

Scenario 2: a new, unproven clan, and you are tempted to donate plutonium

Now assume the other end of the spectrum: you just joined a clan you found through the Discord recruitment channel. It has three or four members, no real track record on the leaderboard yet, and the leader has mentioned pooling plutonium for something. You have a small amount of plutonium — the green, real-money currency — and the temptation is to “prove your commitment” by donating a chunk of it early, before the clan has earned the trust that would make that donation safe.

This is the exact situation the UI is warning you about, and the right move is to slow down deliberately. The plutonium warning is not decoration; it is the feature telling you that this is the one pool where “non-refundable” has real money attached to it, and a new clan is the worst possible container for a real-money donation because the durability you are donating into has not been proven yet. The community threads are full of clans that vanish from the leaderboard when their players stop playing official games, and a plutonium donation to a clan you have not yet watched play a meaningful number of matches is a donation you are making to a future that has not been shown to exist. The cost of being wrong here is not a slower economy, it is real money, permanently out of your account, into a pool that may dissolve next month.

The concrete rule: do not make a plutonium donation to a clan before you have watched it hold a stable membership and a stable rank over a real stretch of play. Make your first contributions in caps, where the worst case is a slower personal economy that you can recover by playing. If the clan earns its durability over the coming weeks and the leader makes a specific, concrete case for pooling plutonium, that is the moment a small, deliberate plutonium top-up becomes defensible — and even then, the size should match the proof, so a clan with two weeks of stable play gets a smaller top-up than a clan with two months of it. The failure here is not donating plutonium in principle; it is donating it early, to an unproven container, on a commitment reflex rather than on evidence. The treasury rewards the player who lets the clan earn the right to receive the premium currency, not the one who front-loads it on a first impression.

Failure modes and how to counter each one

The treasury has a small number of ways to go wrong, and most of them are avoidable with a habit rather than with a setting, because the failure surface is the player’s judgment, not the UI. The first is the double-pay fear, and the design has already handled it for you: one idempotency key is minted when the dialog opens and is reused for every submit in that open, so a retry after a dead connection replays the original request rather than moving more currency. The counter is simply to trust the retry — if you get “Request failed” and resubmit, you have not doubled the donation, and you do not need to cancel and reopen the dialog to be safe, because reopening is the only thing that would mint a fresh key and risk a second, distinct transfer.

The second failure is the insufficient-balance 400, where you typed a number you do not actually have in the wallet you selected. The overlay validates the shape of the input, but the real constraint is your wallet, and the counter is to read your own balance in the correct pool before you type, because the caps and plutonium balances are separate and an error in the other pool is exactly the kind of confusion this feature invites. The third is the not-a-member 403, which the community hits because they are trying to donate to a clan they are not actually in, or whose membership has lapsed; the counter is the precondition check, because you must be a member first, and joining is usually a Discord step rather than an in-game button, so a 403 often means the social step was skipped.

The fourth failure is the currency confusion, and it is the most consequential: donating plutonium when you meant to donate caps, or spending idle caps on the treasury when you actually needed them for your own upgrade, are both real and both cost you, and the counter is the hard rule from the decision section — caps by default, plutonium only when deliberately chosen and the clan is proven. The fifth failure is the ledger confusion, where a player sums the donation history to get the clan balance and gets a number that is wrong by design; the counter is to read the softBalance and hardBalance fields instead, because the donation list is a record of member contributions, not a running total, and the schema says plainly that other ledger reasons are excluded from it. The sixth failure is the version error, trusting a pre-v0.34.0 tutorial that cannot document a feature that did not exist when it was recorded. Every one of these is a habit, not a bug, and the habit is to treat the treasury as a deliberate, small, recurring, caps-first decision rather than a big one-time gesture.

Modes, maps, and where the treasury sits in clan life

The treasury is mode-agnostic in the narrow sense that the overlay is the same screen in every game mode, but the decision of how much to pool is not, because the value of a pooled balance depends on what the clan is actually doing in-match. In FFA, where the community’s core frustration is that same-clan and same-flag players team up and the leaderboard is a ratio, the treasury is most useful as a signal of a clan that coordinates — a pooled balance that is visible and maintained is a mark of a clan that plays together rather than one that just farms FFA. In Humans versus Nations and the team modes, where the in-match ally donation is the dominant economy mechanic, the treasury takes a back seat: the pooled balance is less the lever and more the community bond, because the in-match gold and troop donations are what actually swing a lobby, and the treasury is the standing commitment behind the lobby.

Map conditions matter less for the treasury itself than for the surplus you are willing to pool, because the treasury is an out-of-match transfer and the map never changes the overlay. What the map does change is your caps income, and therefore the surplus you can afford to hand over. On maps and in modes where you clear quickly and stack caps, the idle surplus you can afford to donate is larger, so a bigger whole-number donation is sustainable. On maps and in modes where you die early and generate little, the surplus is small, and the correct donation is small too — a whole number you can genuinely spare, not a number that hollows out your own economy. The mode and map are not inputs to the treasury UI, but they are inputs to the number you should type into it, and the discipline is to let your actual surplus, not the mode’s hype, set the donation.

The community signal rounds the picture out, because the treasury is a community feature before it is an economy one. The threads that last are the ones where the clan is run through a Discord and the leaderboard is treated as a ratio to hold; the threads that die are the ones really about FFA teaming and “what’s the point of clans,” and those are the threads where a treasury is the wrong answer, because the problem there is not a lack of pooled currency, it is a lack of a shared reason to keep playing. The recruitment threads reinforce the precondition that getting into a real clan is a Discord-first step, and the high-view tutorials make the version boundary visible by simply not covering a feature that post-dates them. The takeaway is that the community has documented the conditions under which a clan is worth the one-way donation — durable membership, a Discord, a ratio to hold, a shared reason to keep playing — and the treasury is the thing you do once those conditions are met, not the thing that creates them.

Clan Treasury Donations: Move Your Caps and Plutonium Into the Clan