The source
matters.

A small site with a clear job

Kabuki Codes is built for the moment between playing and getting back to playing. You have heard there might be a new reward, opened a browser, and want an answer you can use. The code board puts the text, reported reward, and evidence note together so you do not have to work through a long introduction before finding the list. The guide sits underneath for the occasions when you need a little more help.

The resource covers one Roblox experience rather than collecting unrelated games in a giant directory. That narrow focus keeps the navigation simple: the code page and this About page. We do not run the game, distribute rewards, or change what a developer's code gives you. Our role is to organize public information and make its limitations visible. A useful resource should help you make a decision without making promises it cannot keep.

Independent of the game and its developer

This website is not affiliated with, endorsed by, or operated by Roblox Corporation or Oicho Kabu. Kabuki and Roblox names identify the game and platform discussed here. Any rights in their names, branding, and game content remain with their respective owners. Our visual design is original and does not use official game artwork as though it belongs to this site.

The official experience page is linked so you can check the game's identity and open it yourself. Community links are supporting references, not an invitation to share account information with this website. We do not offer customer support for Roblox purchases, moderation decisions, lost accounts, or game progress. For those matters, use the relevant platform or developer support channels. This site cannot reverse a redemption or recover an item from your account.

What a status label is allowed to mean

Reported, verified, and expired describe evidence, not the appearance of a badge. A reported code has a traceable publication behind it. A verified code needs a documented successful redemption test. An expired label records evidence that the code is no longer available. If reputable sources disagree, the disagreement belongs in the note rather than being hidden to make the list look more certain.

The initial collection is based on published reporting and has not been tested in game by this site. That is why the initial entries carry Reported labels in the status column. We do not treat a copied article, a recent timestamp, or an enthusiastic comment as a successful test. Rewards are described as reported until the evidence supports a stronger claim. The game's own response is the final authority when you try a code, even if a website says something different.

Publication dates and review dates do different jobs

The release-month filter helps you explore when entries first appeared in the reporting we reviewed. It does not reconstruct every historical version of the game's reward system. A code from an older month can have a current expired status. A code from the newest month can still be unverified. Separating these dimensions lets you browse the archive without confusing age with availability.

A source review date records when the published information was checked for this collection. An in-game verification date, when present, records a successful test. We keep those dates separate and do not update them simply because a visitor refreshes the page. Where an exact release day is unknown, we say so. The month archive grows only when there are real entries to add; empty months are not populated with made-up codes or copied lists.

How sources are used

Official game information is the starting point for identifying Kabuki and its developer. Third-party gaming publications help locate reported codes and describe the redemption interface. The reference desk below links only to the official game and its Roblox community. Reporting sources are retained as maintenance records rather than visitor-facing links. Different publications may update at different times, and their lists can disagree.

We avoid turning the number of repeated reports into a confidence score. Several articles can share the same original source, and a newer page can repeat information that has already changed. Useful review asks what was reported, when it was reported, and whether the evidence actually supports the status. For community announcements and social channels, start with the official experience page. Follow the developer's current links when looking for a server, since a copied invite may be outdated or point somewhere different.

Corrections should make the next visit clearer

If a code fails, keep the exact message the game shows and compare it with the entry's note. A failure can mean the code expired, was already used, or was entered incorrectly. Those possibilities need different explanations. A helpful correction identifies the code, the approximate time, the relevant game update, and the result without including private account details. Screenshots should hide names or other personal information that is not needed.

There is no public comment form or direct support inbox on this version of the site. For now, check the developer's announcements when an entry seems outdated. The maintainer can update the underlying collection and publish a corrected version. This is a maintained reference, not a live connection to the game's reward system. We do not claim round-the-clock testing, automatic code discovery, or a guaranteed update frequency.

Useful on a phone, usable with a keyboard

Players often switch between a small browser window and Roblox, so the board is designed for touch screens as well as desktops. Filters have visible or accessible labels, copy buttons identify their code, and status is described with words as well as color. Keyboard users can move through the controls, browse code statuses, and read the guide questions. The reading sections use a comfortable line length rather than stretching across the entire screen.

If the browser blocks clipboard access, a copy button reveals a text field you can select manually. The initial code list and guide are rendered with the page, so they remain readable if JavaScript does not run. Search, filtering, and the copy interaction require JavaScript. Motion is decorative, and the design respects reduced-motion preferences. These choices help the resource stay useful across different devices, input methods, and browser settings.

Privacy and analytics

You can read and use this site without creating an account. It does not ask for your Roblox password, payment information, email address, or character details. Search text is used to filter the collection in your browser and is not sent as a custom analytics event. Copying a code does not tell us whether you redeemed it, and this website cannot inspect your Roblox session or inventory.

Google Analytics measures page visits, and Microsoft Clarity helps us understand how visitors interact with the layout through usage analysis and session recording. Both services load automatically when you visit this site. There is no analytics consent prompt or settings panel. These services may process device, browser, page, and interaction information, and may use cookies or similar browser storage according to their own practices.

You can manage cookies and site permissions through your browser. Browser restrictions, tracking protection, or extensions may limit the information these services receive. Clearing local storage does not erase information a provider previously received. Hosting providers may also process ordinary request data to deliver the site and protect their infrastructure. The code list remains readable if an analytics service is blocked or unavailable, and rewards are always claimed inside Roblox.

What happens when you leave this site

Opening the official Roblox experience or community takes you to a separate service with its own account requirements and privacy practices. The monitoring described here covers this website; separate services have their own data practices. Read the destination's rules and privacy information if you need to know how it handles data. A community invite may stop working or point to a changed server, so use the current game page to confirm where the developer wants players to go.

Google Search Console and Bing Webmaster Tools are used for website ownership verification and search performance reporting. Their verification tags do not require you to sign in here, and they are separate from visitor analytics. Nothing on this site generates new developer codes. If someone offers guaranteed rare rewards in exchange for a password, a download, or payment, that offer is outside the purpose of this resource.