Trusted Accounts: What the Locked Ranked Button Means and How to Unlock It

Direct answer. A trusted account is a normal account the game has judged not disposable: since v0.35, every ranked queue (1v1, 2v2, FFA, and Clan Wars) requires trust, and the level Plutonium reward track is held until you have it. Earn trust by playing more public games — no public number — or instantly on the website build by making any purchase. The lock icon is neither a ban nor a bug.

The ranked ladder changed shape in v0.35, and with the new queues came a new gate most players hit within their first week: the Ranked button shows a small lock, and the matchmaking modal tells you that ranked play is limited to trusted accounts. If you have ever seen that line, this guide is the primary answer. It covers what “trusted” actually means, exactly what the gate blocks (and what it does not), the two ways to earn trust and why the game never publishes a number for the first one, how to read every line the modal can show you so you fix the right problem, how the lock is enforced under the hood, two concrete scenarios with a decision framework, the failure modes that waste real time and the counterplay for each, and how to adapt the plan to your platform, your mode, and your map. Every rule and number here is anchored to the stable v0.35.2 release and its tag source; if a value in your client differs, the newer official release is the thing to re-check. For the ladder rules the four ranked queues share — ELO, the daily free-match budget, rating protection — see Ranked Mode & Rating System.

What a trusted account is, and why v0.35 added the gate

A trusted account is not a premium tier, not a rank, and not a badge you display. It is a server-side judgement about your account: the game’s backend has decided that this account is a persistent human presence rather than a disposable one, and it records that judgement in a field the client can read. Everything visible to you follows from that single internal flag. Before v0.35 you could jump straight into ranked 1v1 and 2v2 the moment the queues existed; v0.35 changed the contract. The v0.35.0 release states it plainly — “Ranked now needs a trusted account” — and the same release adds the lock icons to the Ranked button and the matchmaking modal so that the restriction is visible before you queue, not only after you are refused. The v0.35 line is also the line that introduced the two newest ranked queues, ranked FFA and Ranked Clan Wars, so the trust requirement now fronts the entire ranked surface: 1v1, 2v2, FFA, and Clan Wars, without exception.

Why does the gate exist at all? Ranked ladders are the part of a game where disposable accounts hurt other players most. A ranked queue is a promise that the person across the map is a persistent player with a reputation and a ladder position; an unlimited supply of throwaway accounts would let people queue with no skin in the game, dodge consequences, and skew the ELO pool. A trust flag is the cheapest honest filter available: instead of judging every single match, the game asks for evidence of persistence first — a history of public games, or the simple fact that the account spent real money. That is the whole design intent behind the line you see in the modal. It is an anti-abuse gate, applied at the door of competitive play, not a quality judgement on your skill. A brand-new account and a five-year account look identical until one of them has public-game history or a purchase; the gate does not care about your rank, your win rate, or your map knowledge. It cares about persistence. The practical consequence of that framing is that the lock is not something you argue with or appeal on skill grounds; it is a condition that resolves by accumulating the evidence the game asks for, which is exactly what the next sections turn into a plan. The lock is temporary by design, and the two ways to clear it are both fully within your control.

What the gate blocks, and what it leaves open

The trust gate blocks one thing and one thing only at the door: entering a ranked queue. All four ranked queues sit behind it — ranked 1v1, ranked 2v2, ranked FFA, and Ranked Clan Wars — because the requirement is written against “ranked” as a whole, not against the two new queues. On the v0.35.2 client the Ranked button and the matchmaking modal carry the lock icons, and the modal’s headline line reads “Ranked is limited to trusted accounts.” Every queue, from the single 1v1 duel to a twenty-player Clan Wars match between four clans, checks the same flag. If the flag is not set, no queue you choose will accept you, and choosing a different queue is not a workaround — switching from FFA to 2v2 does not relax the check, because it is the same check.

The gate also touches one reward path. The v0.35.0 release notes that level Plutonium is held until your account is trusted, and the rewards list says so in the client. Level Plutonium is the reward track that pays Plutonium every 25 levels as you climb the progression levels; on an untrusted account those rewards accrue but stay held rather than being claimable. That is a holding, not a forfeiture: the release describes it as held until trust, so the design intent is that the rewards are yours to collect once the flag flips. You should still watch for it — a new account that levels quickly through public games will carry held Plutonium that looks like a missing payout until the account is trusted.

Everything else stays open. Public lobbies, unlisted private lobbies, custom games, and the non-ranked modes you already play are not behind the trust gate; the restriction is scoped to the ranked matchmaking surface and to the one Plutonium reward track noted above. Two clarifications prevent the most common misreads. First, the trust gate is not the daily free-match budget: a trusted account can still see “You’re out of free ranked matches” when it has used up the day’s free ranked allocation, and that line has a completely different fix (wait for the daily refill, or subscribe for unlimited ranked play). Second, Ranked Clan Wars has a second, independent gate on top of trust: you must also be in a clan, with a valid clan whose membership verifies. Trust gets you past the first door; clan membership gets you through the second. If you are locked out of Clan Wars specifically, the two conditions need to be checked separately, because a trusted account with no clan is just as locked out as an untrusted account with one.

How to earn trust: the two paths and the unpublished number

The modal gives you the entire rule in one sentence: “Your account becomes trusted after you play more public games, or right away with any purchase.” Read carefully, that sentence contains two complete paths with very different time profiles, and there is nothing else. There is no application, no verification email, no support ticket, no in-game test you must pass, and no reputation score you can watch tick up. The flag is assigned by the server on its own schedule, and the client only shows the consequence: the lock while it is unset, the open ladder once it is.

Path one: play public games. This is the default path and the one the game describes first. You queue casual or public matches, play them, and the server’s judgement matures over time. The uncomfortable part — and the part that generates most of the community confusion — is that the game does not publish the number. There is no “play 10 public games” line anywhere in the release notes, the client copy, or the rewards list. The copy deliberately says “more public games” without a count, which is a design choice: a published threshold would invite exactly the farm behaviour the gate is trying to stop, so the threshold stays on the server and stays unannounced. What you can rely on is the shape: it is a persistence signal, so steady play in normal public lobbies is what feeds it, and players who have hit the lock report it clearing after a stretch of casual play over a few days. Treat that community shape as a rough expectation, not a deadline, because the number is not public and can change with the next release. Do not read it as “exactly N games”; read it as “the account needs to stop looking disposable, and normal play does that on a human timescale.” If you are playing ranked-adjacent content daily anyway — public lobbies, custom matches with friends, tournament prep — you are already on this path without extra cost.

Path two: any purchase, instantly. The second clause — “or right away with any purchase” — is the fast lane, and it is worth reading literally. It says any purchase, which means a single one-time purchase is enough; you do not need a subscription, and you do not need to spend a specific amount. If you were going to buy a pattern or a cosmetic anyway, buying it now does double duty: the purchase lands, the trust flag sets, and the lock disappears “right away” in the client’s own wording. One important platform boundary applies here: this fast lane is on the website build. The CrazyGames build of the game ships a different modal line — “Your account becomes trusted after you play more public games” — with the purchase clause removed entirely, because that build has no purchase flow to reference. On CrazyGames there is exactly one path, and it is public games.

A decision rule that covers both paths: if you need ranked access today and are on the website build, the purchase path is the only one that can deliver it today; if you have no purchase planned, the public-game path is free, needs no spending decision, and clears on a timescale of days rather than a fixed number. Either way the outcome is identical: the same flag, the same unlocked queues, the same released Plutonium rewards.

Reading the modal: every line and the fix it points to

The matchmaking modal is the diagnostic panel for this whole system, and it can show several lines that players routinely conflate. The table below lists the lines as they ship in the v0.35.2 client, what each one means, and the correct next action. The single most important skill this guide teaches is the first column: read the exact line before you decide anything, because two visually similar popups have completely different fixes.

Modal line (v0.35.2 client)	What it means	Correct next action
”Ranked is limited to trusted accounts.” + “Your account becomes trusted after you play more public games, or right away with any purchase.”	Your account does not have the trust flag.	Play public games until the flag sets, or make any purchase on the website build. No support contact needed.
”Your account becomes trusted after you play more public games.” (no purchase clause)	Same trust lock, CrazyGames build, where there is no purchase fast lane.	Play public games; there is no purchase shortcut on this build.
”You’re out of free ranked matches.” + “Free matches refill daily. Subscribe for unlimited ranked play.”	You are trusted, but the day’s free ranked budget is spent.	Wait for the daily refill, or subscribe. Do not confuse this with the trust lock.
”You must be logged in to play ranked matchmaking.”	You are not signed in, so the client cannot even check your trust state.	Log in; the trust question only becomes answerable once you are authenticated.
”Clan Wars is played for a clan. Select the tag of a clan you’re a member of next to your username, then queue again.”	You are trusted, but you have not selected a clan tag for the Clan Wars queue.	Pick your clan’s tag next to your username and queue again.
”Your selected clan is no longer valid. Please select a current clan and queue again.” / “Clan membership could not be verified. Please try matchmaking again.”	The clan you selected failed verification (left, disbanded, or the membership check failed).	Re-join or re-select a valid clan; retry matchmaking after the membership state is clean.
”Your ELO: {elo}” / “No ELO yet”	Normal queue state; you are trusted and matched into a queue with rating data attached.	Nothing — this is the success state, not a lock.

Two reading rules make the table pay off. First, the trust lock and the free-match limit never appear as the same line: the trust lock is a statement about your account (“limited to trusted accounts”), while the budget limit is a statement about today’s quota (“out of free ranked matches”). If you have ever queued, been refused, and then assumed you needed to “wait it out” like a ban cooldown, check which of those two lines you actually saw — the wait-for-daily-refill answer is only correct for the second one. Second, the Clan Wars lines tell you that you already passed the trust gate; when a Clan Wars modal asks for a clan tag or reports a verification failure, your account is trusted and the remaining problem is clan-side. That ordering is worth internalizing because it inverts the usual instinct: in Clan Wars, the trust question is the first door and the clan question is the second, and the modal text tells you exactly which door you are standing in front of.

What happens under the hood when you queue untrusted

Knowing the enforcement path removes the last bit of mystery about the lock, and it matters because it tells you why certain things the client does (or refuses to do) are correct behaviour rather than bugs. The design of the trust gate splits work between the client and the server in a deliberate way. The client is told to always queue. Its unit tests make the contract explicit: an account whose trust tier reads untrusted, trusted, or not set at all is still sent into the queue — the client does not pre-filter you out based on what it can see, because the trust decision belongs to the server, not to the client. The client’s job is only to present the lock icon as a pre-queue signal and to be ready to handle the refusal if it comes.

The server is the one that refuses. When an untrusted account’s queue attempt reaches the server’s trust check, the server closes the connection with a dedicated close code: 4103, named NotTrusted in the shared close-code table. That close code is the server’s entire answer — it is not a generic error, not a network drop, and not a timeout. The client’s handling of that specific close is also deliberate. On receiving NotTrusted, the matchmaking modal switches to the not-trusted view (the “Ranked is limited to trusted accounts” line plus the path-specific info text, with the CrazyGames variant on that build) and stops without reconnecting. This is a designed behaviour with its own test coverage: the client does not loop the queue attempt, hammering a refusal that cannot change mid-queue. Re-queueing after hours of public play — when the server’s judgement can actually have matured — is the intended retry, not an immediate re-queue.

Three practical consequences follow. One: if you see the not-trusted modal, the queue attempt already completed the full round trip, so the lock you see is the server’s current decision, not a stale client-side state — restarting the client or clearing cache will not flip it. Two: the lock icon on the Ranked button is the predictive signal (the client showing what it expects based on its view of your account), while the modal is the authoritative signal (the server having actually checked); when the two disagree, the modal has just won, because it carries the server’s answer. Three: because the refusal is a specific close code rather than a crash, the “Matchmaking is unavailable right now. Please try again later” line is a different failure — a service-side unavailability — and its fix (retry later) is unrelated to trust. If your client is refusing ranked with the service-unavailable line, that is infrastructure, not an account state, and playing public games will not change it. The trust system, the service availability system, and the daily budget system are three separate subsystems that happen to live in the same modal, and the modal text is the only thing that tells you which one you are talking to.

Scenario: new website account that wants ranked this week

Put the pieces together in a concrete situation. You just created an account on the OpenFront website, you have played a handful of public lobbies, and the Ranked button carries the lock. You want ranked play this week, and you are weighing the purchase path against the public-game path. Here is the decision framework with the numbers you actually have.

The honest number inventory first. What is published: the gate exists, it covers all four ranked queues, it also holds the level Plutonium rewards, the purchase path works “right away” on the website build, and the free-match budget refills daily. What is not published: the public-game count for the trust flag. Anyone quoting an exact number is guessing, and a plan built on a guessed deadline will break the day the server’s actual threshold disagrees. So the framework is about the two things you control — time and money — not about a number you cannot see.

If you need ranked now and money is not an obstacle: the purchase path is the only route with a same-day guarantee, because its promise in the client’s own words is “right away.” Buy anything — a single one-time pattern purchase suffices, no subscription required — and the lock clears immediately. The cost is whatever you chose to buy; the benefit is that the trust question is settled in minutes instead of days, and any level Plutonium you were carrying releases at the same moment. If you were planning to buy cosmetics this week regardless, the marginal cost of the fast lane is zero.

If you would rather not spend: the public-game path is the plan, and its numbers are the ones you can control. Play steady public lobbies on your normal schedule; the community experience around the v0.35 launch is that the lock clears over a stretch of days of casual play, so expect a few days, not hours, and not a fixed count. Do not try to optimise the path with edge behaviour — the flag is a persistence signal, so the plan that matches its design is simply being a persistent, normal player. While you wait, the held level Plutonium is accruing for the future, so nothing about your progression is at risk during the waiting window. A third, hybrid option exists for the common case: use public-game play as the default, keep the purchase path in your back pocket for the day you actually need ranked access on a hard deadline (a tournament, a clan’s Clan Wars slot), and spend nothing unless the deadline forces it. The framework’s core is that the two paths end at the identical state; the only real choice is when, and what it costs you to get there sooner.

Scenario: the CrazyGames build, where the fast lane does not exist

The second scenario is the same question on a different platform. You play OpenFront through the CrazyGames portal, you hit the locked Ranked button, and you are reading the modal to figure out your options. The first thing to notice is that your modal text is different from the website build’s. Where the website build says “Your account becomes trusted after you play more public games, or right away with any purchase,” the CrazyGames build says only “Your account becomes trusted after you play more public games.” The purchase clause is absent, and that absence is load-bearing: it is not a typo or a translation gap, it is the build telling you that its fast lane does not exist. CrazyGames hosts the game without a purchase flow of its own, so there is no purchase event the server can use to set the flag, and the client’s copy reflects exactly that.

What this means for the plan. On the CrazyGames build there is exactly one path to trust, and it is the public-game path: play public games until the server’s flag matures. The shape of the expectation is the same as everywhere else — days of steady casual play rather than a fixed count, with the community-reported clearance happening over a short stretch of days — but the floor is higher in a specific sense: there is no “I need it today” option at all, and no spending decision that can shorten the wait. If your constraint is a hard deadline (you want to enter a ranked queue before a specific day, or you want the Clan Wars queue open for your clan’s first slot), the CrazyGames build forces one of three answers: accept the wait, move to the website build where the purchase fast lane exists (the trust flag and the account are the same account, so progress in public games carries across), or play the deadline content in public or custom lobbies where no gate applies at all.

Two mistakes to avoid on this build. First, do not assume the website build’s “any purchase” promise applies to you by virtue of buying something elsewhere — the copy the CrazyGames build ships is the copy that governs what that build can observe, and it names one mechanism only. Second, do not read the missing purchase clause as the build devaluing your account or restricting your future: the end state is identical, every queue opens, and the held level Plutonium releases the moment the flag sets. The only permanent difference between the two scenarios in this guide is the timing of clearance on a no-spending budget; everything the flag unlocks afterwards is the same on every platform.

Failure modes, and the counterplay for each

The trust gate is simple, which means the failures around it are mostly misdiagnosis rather than broken mechanics. The five below are the ones that actually cost players time after v0.35, each with the check that ends the confusion.

Mistake one: treating the lock as a ban. The most common misread, because a locked button looks like a punishment. It is not. A ban or a penalty would not come with the line “becomes trusted after you play more public games” — that is a condition, stated in present tense, with a stated way out. Counterplay: read the modal line. If it is the trust line, you are in the normal onboarding state for a new account; if you genuinely suspect a penalty (you see different wording, you lost access to things you had, you got a notice), then — and only then — is a support contact the right move.

Mistake two: confusing the trust lock with the free-match limit. Both popups appear in ranked matchmaking, both can refuse you, and both are easy to blur. The trust lock says “limited to trusted accounts”; the budget limit says “out of free ranked matches.” They have different owners (your account’s persistence vs. today’s quota) and different fixes (public games or a purchase vs. daily refill or a subscription). Counterplay: the modal text is unambiguous if you read the first line — “free matches refill daily” is the tell for the budget, and it means you are already trusted. If you have been “waiting it out” for a budget limit as if it were a ban cooldown, you have been doing the right thing by accident, but know the distinction so you can stop guessing which system you are in.

Mistake three: expecting a Clan Wars queue with no clan (or a broken one). Trust is necessary but not sufficient for Ranked Clan Wars; the queue also verifies that you belong to a current, valid clan, and it asks you to select the clan’s tag next to your username before queuing. A trusted account with no clan is locked out of Clan Wars exactly like an untrusted one, and the modal will say which condition failed — “played for a clan… select the tag,” “no longer valid,” or “membership could not be verified.” Counterplay: if you are locked out of Clan Wars specifically, check the trust line first and the clan line second, in that order, and fix the clan-side problem (re-join, pick the right tag, wait for membership to re-verify) before assuming the gate is about you. The guide for the mode itself — Ranked Clan Wars — covers the queue’s full contract.

Mistake four: assuming the held Plutonium is lost. New accounts that level up before earning trust will see level Plutonium that has not landed in their balance. The release notes the hold explicitly and the rewards list says so in the client; the wording is “held until your account is trusted,” which is a postponement, not a deduction. Counterplay: do not file it as a missing payout while the trust flag is still unset; check your flag state first, and expect the held rewards to release when the flag flips.

Mistake five: retrying the queue in a loop expecting the flag to mature mid-queue. The client is deliberately built to stop on the NotTrusted close and not reconnect, because re-queueing seconds later asks the server the same question it just answered. Counterplay: the unit of retry is time plus public games, not a refresh button. Queue, get the refusal, play public games for the rest of the session, and try again tomorrow — that loop, not a hammering of the queue button, is the path the system is designed around.

How to check your state, adapt by mode and map, and what to re-verify

The system gives you three state indicators, and together they answer “where am I?” without any guessing. First, the lock icon on the Ranked button: present means the client expects your account untrusted; absent means it expects you clear. Second, the modal line after a queue attempt: the authoritative server answer, and the one to read first in any dispute. Third, the held vs. released Plutonium on your progression reward track: a concrete, money-shaped signal of whether the flag has flipped — if rewards that should have paid out are sitting held, the flag is still unset; once it sets, they release. Check in that order whenever something looks wrong: icon, modal, rewards.

Adapt the plan to the mode you actually want. For ranked 1v1 and 2v2, trust is the only gate: once the flag is set, you queue with the same contract as every other account, and the shared ladder rules in Ranked Mode & Rating System — ELO, the daily free-match budget, rating protection — take over as your operating environment. For ranked FFA, same story: trust first, then the four-to-ten-player ladder contract described in Ranked FFA. For Ranked Clan Wars, trust is the first door and clan membership the second; a clan planning its first Clan Wars match should make every roster player trust-clear before the first slot, because one untrusted member with a seat that must be filled turns the trust wait from a background task into a match-day blocker. That last point is the mode-specific adjustment that changes real behaviour: trust clearance is a per-player prerequisite, so it belongs on the clan’s pre-match checklist, not on the individual’s someday list.

Map choice is the one place the trust system does not intervene — the gate is upstream of queue entry, so it does not interact with map pools, timers, or win conditions in any ranked mode; once you are trusted, the mode-specific guides are your complete operating manual and this guide’s job is done for that match. What remains is the version boundary. Every fact here is anchored to the stable v0.35.2 release (tag commit 08b63c054897c030e6516e0731ab7cc62b2998b7, published 2026-10-17): the gate’s existence and scope from the v0.35.0 release, the exact modal copy and the 4103 close-code enforcement from the v0.35.2 tag source. The trust threshold itself remains unpublished by design, so the one thing to re-verify with each future official release is the modal copy and the close-code table — if a newer release changes the wording of the not-trusted lines or the purchase fast lane, this guide’s “what to read” table is the section to refresh, and the official release body is the authority to check against.