All posts
RLCS Season 22 Introduces Visible MMR, Flip Reset Indicator, and Bracket Rivalry Feature And rank.rocketleague Doesn't Exist Yet

RLCS Season 22 Introduces Visible MMR, Flip Reset Indicator, and Bracket Rivalry Feature
And rank.rocketleague Doesn't Exist Yet

Rocket League just made its skill rating system publicly visible to players in real time, and it still lives entirely inside a proprietary client with no external attestation.

The Season That Opened the Black Box

Rocket League Season 22 began on March 11, 2026, described as full of quality-of-life upgrades that enhance the core game without altering the vehicular arcade-style soccer experience. The headline feature for competitive players is not cosmetic. In Rocket League, a number called MMR — short for matchmaking rating — determines your rank. The goal is to win matches, raise your MMR, and reach higher ranks, though if you lose matches, your MMR score can go down. Since its inception, MMR has been an invisible numerical score. Now, with Rocket League Season 22, players can opt to see it.

Before Season 22, the client only showed MMR directly at Grand Champion and Supersonic Legend levels, and most players used external tools or sites to track it. That dependency on third-party scrapers is now partly obsolete. The Season 22 visible MMR feature changes this by letting every player opt in to see their MMR number in ranked playlists. With the new setting enabled, MMR appears on each Competitive Playlist tile in the Play menu and on the scoreboard after ranked matches. The number is only visible to you and does not appear to teammates or opponents, and it does not change how matchmaking works in Casual playlists. Alongside the MMR reveal, flip reset indicators are visual and audio cues under the vehicle that show when a player’s flip has been reset after touching the ball with at least three wheels in the air. Only the player can see and hear them. Both features are optional. Both are private. Both live entirely inside the Epic Games client.

The competitive scaffolding extends beyond individual mechanics. Season 22 tournaments opened with a new weekly Cash Cup format that lets players earn both cash and Tournament Credits by playing ranked matches after linking an account at rpt.gg. On the esports side, Bracket Rivalry returns in Season 22, featuring eight content creator duos competing from March 20 to 26. Players claim their favorite team’s Player Title for free in the Item Shop from March 20 to March 26, and every goal scored while wearing that Title helps them move forward. The final two teams go head-to-head at the Paris Major on May 24. Recent coverage also points to Jordan Brand-themed items as part of the Season 22 content push, which fits the “rivalries ignite” marketing angle in the official trailer rollout. The patch is designated v2.66 and is live across Epic Games Store, Steam, PlayStation, Xbox, and Nintendo platforms.


The TLD That Isn’t There

No registered onchain TLD exists under .rocketleague at the time of writing. No record of Epic Games, Psyonix, or any affiliated party registering .rocketleague on Freename, Unstoppable Domains, or any other onchain naming registry appears in public data. Blockchain domain extensions are Top-Level Domains that exist on blockchain networks rather than within the traditional DNS system managed by ICANN. They are minted as NFTs or smart contract records, giving owners verifiable and transferable ownership. None of that has been applied to the Rocket League brand onchain.

The Web2 paradigm places authority in centralized organizations that choose which names are available, determine renewal costs, and have the authority to cancel domains under specific circumstances. Blockchain technology in Web3 ensures that once you own your own TLD, it stays on the decentralized ledger and is not subject to censorship or unilateral seizure. Epic’s current infrastructure choice runs in exactly the opposite direction. Every piece of player identity data — rank tier, MMR value, competitive history — is held inside a proprietary platform. In-game MMR display is confirmed as one of the new features coming in Season 22. This allows all players, including console users, to see their exact Matchmaking Rating without third-party tools. Seeing it is not the same as owning it. The number lives on Epic’s servers. It is readable through Epic’s UI. It is queryable through Epic’s API — on Epic’s terms, at Epic’s pace, with Epic’s permission.

That matters more now than it did before Season 22 made MMR public. Visibility without portability is a half-measure. The data exists. It just cannot travel. Nothing in the current Rocket League infrastructure allows a tournament operator, a sponsor, or an automated seeding system to pull a verified, tamper-evident snapshot of a player’s current rank without going through Epic’s private API stack. That dependency is structural. It will not be resolved by another UI toggle.


What rank.rocketleague Would Actually Do

The speculative case begins here, clearly marked as such. The infrastructure need it addresses is real.

Since launch, Rocket League matchmaking has used a hidden Matchmaking Rating to decide opponents and to back each visible competitive rank. Each playlist has its own MMR value that moves up when you win and down when you lose, with the size of the change depending on the relative ratings of both teams. There are multiple playlists — 1v1, 2v2, 3v3, Heatseeker, Dropshot, Snowday — each with an independent MMR. A player building a competitive profile carries multiple distinct skill values simultaneously. Right now, that profile cannot be exported, signed, or attested to anyone outside the Epic ecosystem without that party calling Epic’s API directly and trusting the response.

An onchain namespace like rank.rocketleague would reframe the problem. Under such a system, a second-level domain — say, nrg_jstn.rocketleague or team_g2.rocketleague — could carry a cryptographically signed attestation of the holder’s current MMR tier, updated at intervals by an authorized oracle or by the player themselves with verification anchored to their Epic account. In Freename’s Web3 model, TLD extensions are minted as tokens on the blockchain. When a user purchases and registers a TLD, that record is written permanently on-chain, confirming the owner as the legitimate holder of the extension. Once the TLD is active, anyone who registers a second-level domain beneath it generates a royalty for the TLD owner. The infrastructure is already in place for exactly this kind of layered identity namespace. What is missing is the decision to connect it to competitive game data.

The practical downstream uses are not exotic. They are operational today in adjacent contexts. A tournament organizer seeding a bracket without access to Epic’s private API could query rank.rocketleague SLD records instead — pulling a signed attestation of a player’s Champ II 3v3 MMR that was last updated within a defined time window. A sponsor evaluating a player for a content deal could run the same query programmatically. This is where the x402 and ERC-8004 layers become relevant. ERC-8004 answers “who you are” and “how trustworthy you are” through on-chain identity and reputation, while x402 handles “how agents pay each other” via HTTP-native micropayments. An agentic bracket-seeding tool operating under that architecture would identify a player, verify their attested MMR record from the rank.rocketleague namespace, and settle the query in a single automated cycle — the entire process autonomous, with no human intervention required.

The x402 protocol is an open payment standard that uses the HTTP 402 status code to enable AI agents and software to make instant stablecoin payments onchain. Developed by Coinbase and backed by the x402 Foundation, it turns any API endpoint into a paywall that machines can navigate without human intervention, credit cards, or subscription accounts. A rank.rocketleague attestation endpoint, gated behind x402, would allow any external agent system to query it per-request — paying fractions of a cent per lookup, receiving a signed response, and proceeding to the next step of bracket construction or player verification without ever touching a proprietary API or waiting for a human approval chain. Agentic commerce is economic activity initiated and executed by autonomous AI agents with minimal human oversight. In a traditional setup, an AI might find you a flight, but you must manually enter your credit card details to finalize it. In agentic commerce, you give your agent a budget and a goal, and the agent executes the entire transaction on its own. Bracket seeding is a simpler task than booking a flight. The infrastructure gap closing it requires is narrower than it appears.

Today, fan loyalty cannot be readily displayed and understood outside of specific platforms. For example, the League of Legends subreddit enables users to post “flairs” for specific teams as a way to showcase their fandom. But if a user migrates to another platform, the same option doesn’t exist. Additionally, these loyalty signals are not directly issued by the esports team themselves, but are rather features of external platforms. The same structural problem applies to competitive identity. A Rocket League player’s rank exists on Epic’s servers, not on the player. It cannot be presented to a third party without trusting Epic to answer the query honestly, quickly, and without an API key expiration getting in the way. An attestation recorded in an onchain SLD map under .rocketleague would invert that dependency. The player would carry their credential. The verifier would query the chain. Epic would not need to be in the loop at all.

The timing of Season 22’s changes is not coincidental. Psyonix appears to be implementing native versions of popular Bakkesmod features before removing mod support. Bakkesmod offers far more than just flip reset indicators and MMR display. The closure of Bakkesmod via Easy Anti-Cheat removes a generation of third-party tools that players used precisely to surface and transport data the client kept locked away. The native MMR display replaces one Bakkesmod feature. It replaces none of the portability that the mod ecosystem provided. That portability gap widens with every season that passes without a structured onchain layer.


The Score Is Visible. The Credential Is Not.

Season 22 is a well-executed product update. The MMR visibility change is overdue. The Bracket Rivalry mechanic is a smart way to thread the community into the RLCS competitive calendar. The weekly Cash Cups give ranked play a consistent monetary floor. Psyonix executed cleanly on a list of long-requested features.

None of that changes the structural picture. The headline for competitive players isn’t the new cars, but the data. This update integrates visible MMR directly into the UI, alongside new indicators for boost recharge progress and flip reset status. But data visible in a client is not data that belongs to the player. The MMR number exists. It is now shown. It is still locked. There is no rank.rocketleague namespace. There is no signed attestation a player can carry to a third-party tournament organizer, an agent system, or a sponsor without going back to the source. The infrastructure that would make that possible does not exist onchain yet. Durable identity systems require coordination, interoperability, and careful stewardship of shared infrastructure. Showing a number in a UI is not the same as building a credential. One closes an information gap. The other closes a trust gap. Only one of those has happened.


The author holds onchain positions related to this topic. This post reflects independent editorial judgment.

The author holds onchain positions related to this topic. This post reflects independent editorial judgment.
Kooky Writing at the intersection of trademarks, onchain identity, and brand intelligence.
About Kooky →