GUIDES
Reading the Clan Top Donors Leaderboard
How to read the clan top donors leaderboard that shipped in v0.35.9: what each row and each time window actually measures, why the list is an acknowledgment tool rather than a payout, and how to use it to spot who is genuinely funding your clan before you donate or promote.
What v0.35.9 added: a leaderboard, not a second treasury
Version 0.35.9 added a top donors leaderboard inside the clan donations view. It sits alongside the treasury you already know and, in the upstream implementation, the new top-donors component renders next to the existing donation panels in the same clan screen. The feature is a reading tool: it surfaces which members are contributing the most to the clan treasury over a chosen time window and ranks them, so a leader or an interested member can see contribution at a glance instead of piecing it together from donation events one by one.
That framing matters because it changes what the feature is for, and it is the single most important idea in this guide. It is not a second treasury, a second balance, or a place where gold or resources are held. It is a derived, read-only ranking computed from the donation activity that the treasury already tracks. If you are opening the leaderboard expecting to deposit into it, withdraw from it, or configure payouts from it, you will be looking in the wrong place: nothing in the feature changes the treasury balance, and nothing about it creates a new resource pool. The treasury remains the single source of truth for what the clan actually has; the leaderboard is a lens over the contributions that flowed into it, and it can be opened, closed, and re-read without ever touching the real balance.
This distinction also sets the boundary of what the guide covers, and it prevents the two most common first mistakes players make. The mechanics of donating into the treasury itself — when donating is the right call, what it does to your own caps and plutonium, and how the treasury spends what it collects — are the subject of the companion clan treasury donations guide. This guide takes the opposite vantage point: you are not deciding whether to donate; you are trying to understand the leaderboard that another member, or the game itself, is showing you. By the end you should be able to read any row, explain why the order is what it is, and know exactly what the list can and cannot be used to decide. If you remember nothing else from this page, remember that the leaderboard observes the treasury rather than holding to it, because every rule that follows flows from that single fact, and it is the reason the feature is safe to read without ever risking a real resource.
What each row actually measures — and the three numbers to watch
Each row on the leaderboard is one member, and the numbers next to that row are an aggregate over a time window, not an instantaneous balance. When you see a member’s name followed by a contribution amount, that amount is the sum of the donations that member made to the clan treasury during the period the list is currently displaying. It is not how much gold the member currently holds, not how much they are worth, and not a score the game assigns to them. It is a backward-looking total: “this is how much this member put into the clan treasury during the window you are looking at,” and nothing more, which is a much narrower claim than the number on screen tends to suggest.
Three numbers matter on the row, and confusing them is the most common way players misread the list. The first is the member identifier — the name, or the clan-relative reference, of the person the row is about, which lets you tie the number back to a real person you know or need to know before you trust the number at all. The second is the aggregate amount, the summed contribution for the window; this is the number that actually orders the list, because the leaderboard sorts its rows by it, so the rank you see is simply a function of this one figure. The third is the time window the amount is computed over, which is the one number the list hands you that most people skip, and which determines everything the other two mean. A member showing 1,000 in a short window is a very different signal from a member showing 1,000 in a long one, even though the printed number on the screen is identical in both cases.
Because the value is an aggregate and not a balance, the number can be large even when the member has donated nothing recently — it may be carrying weight from earlier in the window — and it can be small even for someone who just made a big single donation that has not yet accrued meaningfully inside the total you are looking at. Treat the figure as “total flow through this member over this period,” the same way you would read a running total on a statement rather than a balance printed at the bottom of the page. That single reframe — flow, not stock — is the foundation for every decision the rest of this guide walks through, and it is the first thing to internalize before you act on what you see, because once you stop treating the number as a balance you will stop making most of the errors that the next few sections describe, and you will be able to read a stranger’s screenshot the same way you would read your own.
Why the list is an acknowledgment tool, not a payout
The most important thing to lock down before you act on the leaderboard is that it is built to recognize contribution, not to compensate for it. The feature ranks members so the clan can see who is funding the treasury, and in the upstream design the top-donors view is a recognition surface inside the clan screen rather than a transactional one. There is no automatic reward, no claimable token, and no balance that moves when a member climbs the list. If a member is first, the game has not paid them anything; it has simply made their contribution more visible to everyone who opens the screen, which is a social effect, not an economic one, and it is the whole of what the feature does.
This matters practically because it removes a whole category of decisions the leaderboard cannot drive on its own, and leaning on it to do so is where bad calls start. You should not treat a high rank as an entitlement to a reward, a promotion, or a share of treasury output, because none of those is wired into the feature and the game will not produce any of them from a rank. Promotion, officer appointments, loot splits, and reward policies are all human clan decisions that may reference the leaderboard as one input, but they are not triggered by it, and a leader who reads the list as a set of automatic obligations will be confused when nothing happens. The list earns visibility; it does not earn anything else, and building a reward policy on the assumption that it does is the wrong direction to put the burden.
It also matters defensively, because the reverse misuse is just as common and just as wrong. Do not assume that a low or absent rank means a member is being shortchanged, or that a member who is not on the top list is somehow being penalized by the system. Being off the top of a window simply means the member’s contributions in that window ranked below the others; it is not a flag, not a demotion, and not a negative mark that the game is keeping on them. The safe mental model is “the leaderboard tells you who contributed most in the window you selected,” and everything beyond that — what the clan does with that knowledge, who it rewards, who it promotes — is a separate decision made by people, not by the list, and keeping that boundary clean is what keeps the feature honest, and it is what stops a tool built for recognition from being quietly turned into an unenforced promise.
The one number that changes the reading: the period window
The single most decision-relevant number on the leaderboard is the time window the list is showing, because it is the variable that decides whether a row is describing recent behavior or accumulated history. The same member, the same printed amount, and the same rank can mean opposite things depending on how long the window is, which is why the period is the first thing to read, not the last, and why you should confirm it before you trust a single row. In a short window the figure describes recent, sustained output: who has been putting money into the treasury consistently right now, over the last days rather than the last months. In a long window the same figure describes a cumulative total: who has contributed the most over many weeks, which can be dominated by one or two big older deposits that are still being counted.
Concretely, the period window changes which player behavior the list is rewarding, and the two behaviors are not the same, even though they both look like “a big number.” A short window favors consistency — a member who donates a moderate amount every day climbs it, while a member who makes one enormous donation and then stops falls off quickly, because the recent flow is what the short window sums. A long window favors cumulative mass — a member who made a few very large deposits earlier in the window can still sit near the top even if their most recent activity is modest, because the total is still counting those big earlier contributions. If you are trying to answer “who is actively funding us this week,” you want the short-window reading; if you are answering “who has been our most important backer over the season,” you want the long-window reading. Using the wrong window to answer the question is the fastest way to reach a wrong decision, and the decision is wrong even though the numbers on screen are all correct and the list itself did nothing unusual.
This is also the window you must check before comparing across lists or across screenshots, and it is the check that stops the most common cross-comparison error. If one member shared a top-donors image in a short window and another shared theirs in a long window, the two lists are not measuring the same thing and must not be ranked against each other as if they were. Always establish the period before you compare, exactly the way you would confirm two bank statements covered the same dates before comparing the balances printed on them. The amount column is only meaningful once you know the window it was computed over, which is why this guide returns to the period in every section that follows, and why the next worked example makes the window the whole point of the comparison rather than a footnote you are expected to remember.
| Window | Best answers | Watch for |
|---|---|---|
| Short / recent | Who is actively funding us right now | Hides big early donors who have since slowed |
| Long / multi-week | Who has been our most important backer over time | Can reward one large one-off deposit |
| Cumulative | Who gave the most over the whole season | Older or inactive veterans dominate |
A worked example: two members, two windows, two different answers
Imagine a ranked clan with two members you are deciding between. Member A donates a steady, moderate amount every single day, never a lot but always something, which is the profile of a member who treats the treasury as an ongoing responsibility rather than a one-time statement. Member B makes one very large donation near the start of the season and then donates only small amounts or nothing since, which is the profile of a member who made a big early gesture and then went quiet. You open the leaderboard and want to know who you can reliably count on going forward, and the answer depends entirely on which window you are reading, not on which member is “better,” and that is the whole lesson in miniature.
In a short window, for example the most recent days, Member A is at or near the top, because their recent daily flow is what the list is summing and it is steady and present. Member B’s large early donation is outside the window and does not appear in the short-window total, so B may rank low or not appear at all. Read in the short window, the list is telling you “A is the one actively funding us right now,” which is the correct conclusion if your question is about ongoing reliability and about who you can lean on next week. In a long window, for example many weeks, Member B can sit at the very top, because that one large deposit still sits inside the cumulative total and dwarfs A’s smaller, steadier contributions summed over the same period. Read in the long window, the list is telling you “B contributed the most total value over the whole season,” which is a true statement, but it is a different statement from the one the short window makes, and treating the two as the same statement is the error this example exists to prevent.
Now the decision fork, stated with the assumption made explicit so you can audit it rather than assume it. Assumption: you are choosing who to rely on for future funding, not rewarding past totals, because the point of the decision is what happens next, not what already happened, and the two questions point in different directions. Under that assumption, the short-window reading is the one that answers your question, and the correct read is that A is your more reliable ongoing backer, even though B may hold a higher long-window total and may be the bigger name in the clan’s history. If instead your assumption were “reward the single biggest historical contribution,” the long window would be the right tool and B would win, and that would also be a correct read, just for a different question. The leaderboard did not change in either case — you changed the window, and therefore the question it was answering, which is the whole discipline of reading the list: pick the window that matches the decision you are actually making, and let the other window be context rather than the answer you are about to act on.
The five failure modes — and how to counter each
Misreading the leaderboard is predictable, and each failure mode has a concrete counter, so the goal is not to avoid error but to recognize the error the moment it happens and apply the matching fix before it becomes a decision. Failure one: reading the amount as a balance. A large number looks like the member holds that much gold, so you treat them as wealthy and make decisions about them on the assumption that they are rich. The counter is the reframe from section two: the figure is a flow over a window, not a stock, and before you infer anything about a member’s wealth or standing you ask what window the total covers and what exactly it summed, which is a question you can answer from the screen itself.
Failure two: ignoring the period window and comparing across it. You compare a short-window rank from one screenshot against a long-window rank from another and conclude that one member “beat” the other, when the two numbers were measured over different periods and cannot be ranked against each other at all. The counter is to never compare two rows unless you have confirmed both come from the same window, and to state the period out loud, or in text, before you rank anyone against anyone else, so the comparison is auditable by you and by anyone who reads your note later.
Failure three: treating rank as a reward or an entitlement. You assume a top rank means the member is owed a promotion, a share of loot, or some payout, and then feel wronged when the clan does none of those things. The counter is the recognition-not-payout rule: the list authorizes visibility only, and every reward is a separate human decision that the list may inform but never triggers, so a rank is an input to a decision, not a decision by itself, and expecting the game to settle an account it never opened is the mistake.
Failure four: reading absence as a negative signal. A member is not on the top list for the window, and you read that as them slacking, being flagged, or being penalized by the system in some way. The counter is to remember the list shows only the top contributors in the selected window; absence means “below the others in this window,” nothing more, and it says nothing about the member’s earlier or later behavior, their loyalty, or their standing in the clan beyond that single axis, so a missing name is not a verdict.
Failure five: using the wrong window for the question. You answer “who can I count on next week” with a long cumulative total, or you answer “who was our biggest backer this season” with a short recent slice, and in both cases the number you used is the wrong instrument for the question you asked. The counter is the worked example’s rule: match the window to the decision, with reliability questions using the short window and cumulative-recognition questions using the long one. If you catch yourself using a long-window total to make a forward-looking reliability call, stop and switch windows first, because the answer you are about to make is built on the wrong measurement, and no amount of confidence in the number fixes a number that was never measuring the thing you asked about.
How the reading shifts by mode and map
The leaderboard’s meaning also shifts with the context of the clan — the mode you play and the map you hold — because different contexts change what “funding the treasury” is actually buying, and therefore change what a high contributor’s rank is telling you about who is carrying the load. In a clan that plays the same high-spend mode on the same map repeatedly, the treasury’s output is predictable and the leaderboard is a stable instrument: a member who tops the list is reliably funding a well-understood sink, so their rank maps cleanly onto “this person is carrying our war effort on this map,” and you can trust the reading for as long as the context stays constant, which is the best case for the tool.
In a clan that rotates modes and maps, the same rank is noisier, and the noise comes from the context rather than from the members. A member who contributed heavily during a phase where the clan played a costly, high-spend map can top the list for that period even if their contributions in a lighter phase were modest, so the long-window total can be dominated by which phase the member was active in rather than by the member’s personal consistency. If your clan recently changed maps or modes, treat a freshly re-ordered leaderboard with caution, because part of the reordering is the context change, not a change in who is actually pulling their weight. The practical read is to favor the short window after any context change, because it reflects current behavior in the current map and mode rather than the residue of the previous one, and it is the only window that is measuring the present you are making decisions about.
This mode-and-map sensitivity also tells you when to discount the list rather than trust it, and it is the reason a long-window ranking is least reliable during a transition. If the clan is in a transitional window — mid-map-change, mid-mode-rotation, or just after a big member influx — the cumulative totals are a mix of two different contexts, and a long-window ranking is the least reliable you will ever see it, because the two halves of the total are answering different questions. In that situation, the short window is the honest instrument, and any major decision — promotion, who to recruit next, who to rely on for the coming ranked block — should be made from the short-window read, with the long window held only as background context about who the veteran backer is. Once the new context has settled and a full window of play has passed under it, the long window becomes trustworthy again, and you can return to using it for the cumulative questions it is best at.
The decision framework, limits, and version boundary
Bring it together into a single decision procedure you can run in under a minute, so the discipline becomes a habit rather than a lecture you have to re-read every time. Step one: identify the question you are actually answering — a forward-looking reliability question or a cumulative-recognition question — and say it out loud, or in a note, so you cannot be ambiguous about which one you mean when you reach a conclusion. Step two: choose the window that matches it — short for reliability, long for cumulative history — and confirm you are reading that window, not a leftover screenshot of another window from a previous conversation. Step three: read each row as a flow, not a balance, and tie the top names to real people you can verify before you treat the number as a fact about them. Step four: treat the result as input to a human decision, not the decision itself — the list informs promotion, recruitment, and reliance, but it triggers none of them, and absence from the top is never a penalty by itself. Step five: if the clan recently changed mode or map, prefer the short window and discount the long-window ranking until the new context has had time to settle.
Know the limits of what the leaderboard can support, because the strongest version of this tool is the one that does not overreach into questions it cannot answer. It tells you who contributed most in the window you selected, and nothing else: it is not a wealth statement, not a loyalty score, not a reward claim, and not a performance rating, and every one of those uses is a different question that this single axis cannot answer. It measures one thing — treasury contribution over a period — and decisions that depend on axes it does not measure (combat skill, map knowledge, leadership, consistency of play, willingness to carry when the treasury is not the sink) must not be made from it alone. The healthy posture is to use the leaderboard for exactly the one question it answers and to bring other evidence to every question it does not, which is the same discipline you would apply to any single metric in any system, and the same reason a good player checks the window before trusting the number.
Version boundary. The top-donors leaderboard and its time-window aggregation shipped in v0.35.9, and this guide’s claims are verified against the v0.35.9 release source, the upstream top-donors component, and the v0.35.9 release notes. The precise per-row period values the live UI displays, for example the exact number of days in a short versus a long window, were not confirmed against the running build in this pass, so treat the concrete window labels you see in the game as authoritative and use this guide’s window logic — which window answers which question — rather than assuming specific day counts. For the treasury mechanics themselves, the companion clan treasury donations guide and the clan membership guide cover the donating and membership sides this guide deliberately leaves alone, so read this page as the ranking half of the picture and those two as the rest, and use the three together when a decision needs both the ranking and the mechanics behind it.
Related content
Use OpenFront v34.3 costs, troop growth, route payback, and stop signals to choose City, Port, Factory, defense, or a liquid reserve without copying a fixed script.
- OpenFront AFK Teammate Takeover: Absorb a Disconnected Ally for Zero Troop Loss
A Team-mode decision guide for what a teammate's disconnect does to your win/loss position, when absorbing their land is free, when it is a trap, and what the 30-second mark and the ranked 2v2 rules actually change.
Sep 23, 2026
- How Nations Aim Their Nukes: Smarter Targeting, No Wasted Blasts
A strategy guide for the upcoming AI Nation nuke targeting change: Nations now compute how much of a blast hits enemy land before firing (atom 25%, hydrogen 40% minimums), they skip a spot where another player's nuke is already landing, and they never nuke a target that would hit friendly land. What changes in your decision, the coverage gate, the anti-double-nuke rule, the failure mode and the mode/map adjustments.
Oct 8, 2026
- Alliance-Break Timing: When 30 Seconds Is Worth the Trade
Decide whether to break a live alliance now, wait for it to expire, or renew it, using the 30-second traitor window, the 0.5 defense and 0.8 speed debuffs, and the -100/-40 relation drops in OpenFront v0.34.
Sep 30, 2026