In 2019, a now-defunct indie studio called Salted Pixel was developing a chaotic physics brawler titled Produce Kombat. One unreleased build, labeled REWIND_v0333, featured a playable character: a cucumber that could enter a “sprint” state—moving three times faster than intended due to a physics engine bug.
Testers wrote in internal Slack: “Cucumber sprint breaks level geometry. Rewinding time (a core mechanic) creates clones. Do not ship.”
The term “rewind v0333 sprinting cucumber” was first spotted in a scraped JSON file from an unprotected S3 bucket in 2021. The internet did what it does best: turned a bug into a meme. rewind v0333 sprinting cucumber
Here lies the magic. A cucumber is passive, cool, water-rich, and famously non-locomotive. To pair it with “sprinting” creates a surreal cognitive dissonance.
In software testing, “cucumber” is well-known as a behavior-driven development (BDD) tool. Cucumber (the framework) runs .feature files written in Gherkin language—sentences like “Given a user logs in” or “When they click submit.” But “sprinting” is an agile methodology term (sprint planning, sprint review). In 2019, a now-defunct indie studio called Salted
So “sprinting cucumber” could be interpreted as:
It’s absurd, but memorable. The illustration of a cucumber with tiny running legs is social-media gold. Rewind leans into the weirdness — the box’s back has a fake botanical sketch: Cucumis sprinterus “v0333.” This self-awareness prevents cringe. It’s no more ridiculous than “Buckin’ Buffalo Berry” or “Razzle Dazzle” from other brands. It’s absurd, but memorable
This build retained the legacy parsing engine from v0329.