Chop Chop Inc. updates

The 2026-04-10 pre-release announcement records the team preparing its first playable demo. The 2026-05-21 demo state belongs to Steam App ID 4707740 and marks the public demo release. The full game followed on 2026-08-07 under App ID 4369130. That separation is important: the demo is historical context, while the current achievement and gameplay records belong to the full App ID.

Three named hotfixes share the launch date. Hotfix #1 added a GPU Occlusion Culling toggle and fixed the main-menu Load button. Hotfix #2 added a frame limiter, removed the firewood minigame, and fixed a tutorial-message/save edge case. Hotfix #3 fixed a possible softlock after building the cannon foundation and is the current captured anchor. Reading these as six states keeps the demo App ID, full App ID, and same-day hotfix labels from collapsing into one misleading version number. It also makes the predecessor chain explicit: each record has a date and role, while the latest hotfix remains the current reference for the rest of the wiki.

A vertical field chronology keeps the date rail and the predecessor relationship visible at the same time. The launch and three hotfix entries can share 2026-08-07 without being collapsed into a single launch note. Their change counts make the difference legible: two changes in Hotfix #1, three in Hotfix #2, and one in Hotfix #3. The selected dot and spotlight update together when a player moves through the list.

The controls intentionally use the public titles rather than invented semantic numbers. Steam did not publish a build number for Hotfix #3, so the page says Hotfix #3. This preserves the language used by the official announcements and prevents a false “1.0.3” from becoming a search or gameplay fact. The selected spotlight is a reading aid over the same six records, not a second data source that can silently diverge from the timeline cards. Selecting a tile changes the emphasis only; it does not fabricate a patch label, merge dates, or replace the public change list.

Research found a much larger demo catalogue, but that does not create a current item or recipe database. The update route uses the demo only for its dated release state and its separate App ID. It does not copy demo records into current navigation, and it does not infer that a screenshot or announcement proves a current quantity, machine list, price, or recipe graph.

That boundary makes the timeline more useful for a player returning after launch. Choose the demo to see what was public on 2026-05-21, choose full release to see the launch transition, or choose one of the three hotfixes to isolate the documented change. Each record links to its official Steam announcement for the complete source context. Historical context stays useful precisely because it is not promoted into a current inventory or guide claim. The page can therefore explain what changed without implying that every demo-era record still describes the released Windows build.

A future first-party update can be added as another named state after Hotfix #3 without rewriting the earlier chain. Its exact public date, title, changes, predecessor, and source link would become one new record. The interface already keeps the selected version separate from the full chronology, so a longer history can remain legible on mobile by stacking the tiles and preserving the left rule.

For this capture, the visible UTC observation boundary is 2026-08-08T21:04:53.364Z. The six release records are version facts, while achievement percentages are separate observations. Keeping those time types distinct prevents a launch note from looking like a current rate measurement and makes the page easier to update when Steam publishes new material. A later release can therefore extend the chronology without rewriting the facts already tied to their original date and source. Dates describe when a state was published or observed; they are not interchangeable labels for a build number or an unlock percentage.