Chiidoku’s current major public change is the expansion of Campaign to level 400 with new puzzle-board themes. The creator’s event ran from August 28 to September 4, 2026 and explicitly described the additional levels and fresh board looks. Roblox game metadata also showed a September 1 update timestamp when checked on September 2.
Use this page for dated, developer-controlled changes. A timestamp proves that the experience changed; it does not reveal undocumented balance adjustments, theme names, reward tables, or patch notes.
Latest verified status
The current English description also continues to advertise win streaks, random Endless puzzles with no level limit, daily-refresh missions, rewards, coins, and character unlocks. Their detailed mechanics are not explained by the event.
Update timeline
2026-09-01 — Universe metadata updated
Type: Live metadata
Roblox’s Games API showed the Chiidoku Universe updated at 2026-09-01T04:11:40Z. The current description at the September 2 check included the 400-level Campaign and no-adjacency wording.
- Treat the timestamp as a freshness signal, not a complete patch note.
- Recheck rules, mode labels, store entries, and live screens after joining.
- Do not invent hidden balance changes from the time alone.
Source: Roblox Games API
2026-08-28 — Campaign expanded to 400 levels
Type: New content
The official public event says Campaign expanded to level 400, added brand-new puzzles, and introduced updated puzzle-board themes. This replaces older pages that still describe a 300-level campaign.
- Current Campaign endpoint: level 400.
- New puzzle-board themes exist.
- Theme names, count, unlock method, and stage mapping were not included.
- Exact level answers, difficulty bands, and completion rewards were not included.
Source: Official Roblox virtual event
What changed for players
Players following Campaign can continue beyond the older level-300 endpoint to level 400. Use 400 Levels for a progress plan that follows current rules and avoids unsupported answer grids. If a guide tells you that 300 is the final stage, check its date and replace that assumption.
The event also confirms new puzzle-board themes. Depending on the live interface, a theme may be automatic, selectable, or tied to progress, but no public first-party text establishes which. Prioritize a readable board and record exact names or unlock steps only after the current game displays them.
The English description says Chiikawas cannot be placed next to each other, while some older pages say adjacency is allowed. Follow the current description and use Adjacency Rule for the unresolved edge-versus-diagonal scope.
What did not receive public patch details
No public update entry explains the exact adjacency directions, Campaign reward schedule, Endless entry or failure rules, streak reset behavior, daily mission pool, reset timezone, coin rates, full character roster, character prices, or gamepass effect coverage. Those are not safe additions to patch notes.
The official pass catalog still listed Heart + 1 at 149 Robux and 2x Rewards Pass at 249 Robux when checked. Both public descriptions were blank. Their creation date was August 12, but the current 400-level event does not say their behavior changed.
No developer-published working code appeared in the checked description, event, or empty group shout. That supports the dated Codes status, not a permanent “no codes” promise.
How to verify a future update
Start with the official experience and confirm Place 139705352041000, Universe 10628006421, and creator group 미지 스튜디오. Read the current description and Events panel. Then check the creator group for a dated shout.
For each claim, record the announcement date, exact wording, affected system, and current game result. Separate official statements from in-game verified behavior. A community report can identify a question, but it should not become a confirmed patch item until it agrees with a developer source or reproducible live observation.
Avoid using visit count, favorite count, active-player count, or a general update timestamp as proof of a mechanic. Those values can change without describing the puzzle rules.
Update-sensitive page checklist
Rules
Check row, column, color-area, and adjacency wording. Re-test direction scope if the tutorial changes.
Open RulesModes
Check Campaign total, Endless wording, and streak labels. Keep exact rewards and resets tied to live evidence.
Open ModesEconomy
Check current daily objectives, coins, character roster, prices, and visible reward behavior.
Open EconomyPurchases and codes
Check pass catalog ownership and creator, plus any original code announcement. Do not merge earned and Robux systems.
Open GamepassesReport a possible change responsibly
Capture the live menu, result, or rule text with the game update date and mode. Include the actions that led to it, while removing account identifiers and payment data. If another player cannot reproduce the result, compare device, server age, mode, pass ownership, event status, and whether a cached interface was involved.
Do not call a visual theme a new mechanic, a local display bug a global update, or a changed number a deliberate balance patch without context. A concise reproducible observation is more useful than a dramatic unsupported explanation.
Frequently asked questions
What is the latest Chiidoku update?
The current official event expands Campaign to level 400 and adds new puzzle-board themes. Game metadata showed an update on September 1, 2026.
Did Chiidoku increase from 300 to 400 levels?
Yes. The official event explicitly says Campaign expanded to level 400.
What are the new themes?
The public event confirms new themes but does not list their names, count, unlock route, or stage assignments. Check the live game.
Did the puzzle rules change?
The current English description includes a no-adjacency rule. Older adjacency-allowed text conflicts and should not be treated as current. Exact directions still need live testing.
Are there detailed patch notes for every September 1 change?
No. The timestamp alone does not explain every modification. This page records only supported public changes.