The documented history of +1 Fruit Samurai: creation, the August new-map wave, the September 11 UPD1 update, and today's status — every row attributed to its source, checked 2026-10-03.
The live game is on UPD1, shipped September 11, 2026 (official updatedAt 2026-09-11T04:02:26Z) and announced the creator's own way — the page title carries the [UPD1] tag and the description reads “New Code: UPD1”. Nothing has shipped since: the API timestamp is unchanged at today's check, and both tracked codes (UPD1, FRUITSAMURAI) remain listed active by RobloxDen and ROGameCodes. The creator has published no patch notes for any update, so this timeline is built from the official page itself plus dated creator and tracker coverage.
Official rows cite the Roblox page or API; community rows name the tracker or creator and the date they published.
Source: Roblox games API (official); Top2hot Roblox (August 2026, creators)
Source: Creators: ScorpionXZ and Top2hot Roblox videos (titles and descriptions)
Source: Official Roblox page title and description; Roblox games API updatedAt
Source: Publisher sites: ROGameCodes, BloxCodes, RobloxDen (dated checks)
Source: Roblox games API + RobloxDen, checked 2026-10-03
What moves when the game moves — and which page carries the fresh answer.
The next update has shipped: recheck both codes for retirement, expect a new code in the description, and re-run the tier framework against any balance note.
Open the affected page →The description is the creator's announcement channel — a new code, a new system, or a new map usually appears there first, before any tracker updates.
Open the affected page →The technical confirmation that content changed. We re-pull visits/votes snapshot at the same time so the popularity table stays dated.
Open the affected page →It gets a claim row with its source and date — and the rumor stays out until a tracker or the description itself lists it. No string has been added on word of mouth alone.
Open the affected page →Through the Roblox page itself: a bracketed tag in the title ([UPD1]) and edited description text. That is the whole official channel — no Discord, no Trello, no patch notes existed as of October 3, 2026.
UPD1's documented content is its code. The creator names codes in the description, and trackers confirm rewards — which is why the codes page rechecks on every update trigger.
The new-map wave (three creator videos, August 17–19) shows how content lands here: creators cover it within days. A quiet YouTube space is itself evidence no update has shipped.
Three documented beats in three months is the whole record so far — read honestly, that shapes expectations.
July launch, an August map wave covered by three creators in three days, a September numbered update — then quiet into October. This is not a weekly-update game, so a quiet API timestamp is normal, not a missed patch.
The launch window produced FRUITSAMURAI; UPD1 produced UPD1. One code per documented beat is the observed pattern, and it is why the codes page leads with the update triggers rather than a rumor list.
Every August change was on YouTube within roughly three days. If a real update ships, expect creator coverage almost immediately — and expect this page to cite it the same week.
Each link is a page whose answers can move when the official record does.
