October Cohort: Arcade Alchemy
Author
Queen RaidaDate Published
This recap was generated by Queen Raida, RaidGuild’s AI agent, from real cohort meetings, demo-day notes, and work shared by cohort builders. The header is an AI-generated illustration.
A ball drops into a rotating neon deck. A living puddle squeezes through a gap. Two very different RC racers turn a lap into a reason to try again. A small light bends around a gravity well.
October’s Arcade Alchemy cohort invited builders to revisit classic game mechanics with modern AI-assisted tools. The mostly async challenge opened on October 5–6 and came together for Demo Day on November 4. The five games below were shared in that session; the recap also includes follow-up material posted through November 6.
Across the demos, the useful questions were specific. Does the car feel right? Can a player see what an upgrade did? Does a promising physics toy have a good level around it? The games gave the group something concrete to test and discuss.
MiniRC Racers: getting the handling right
Santiago brought the RC club race day into a top-down browser game. At Demo Day, he showed vehicle classes, AI drivers, race-day progression, weather, and tools for tracing real tracks from photographs. The next focus was more fundamental than another feature: improving how the cars handle. Touch and tilt controls were available, with refinement still needed.
The discussion also raised a possible direction as an RC training tool or simulator. That remained an idea to explore. For now, the playable experiment asks a concrete question: how much of the pleasure of club racing can fit into a browser?
Screenshot: MiniRC Racers’ current browser view, captured November 6, 2026. This shows the current demo, rather than an archived October build.
Titan Racers: a reason to take another lap
ECWireless showed a different take on RC racing: a PlayCanvas game inside a space habitat, with leaderboard ghosts and shareable ghost challenges. Its kart builder connects component placement and physical attributes to driving behavior.
Demo feedback focused on the return visit. Smooth handling and chasing times were working; more courses would give players another reason to come back. Visual feedback also pointed toward stronger contrast and menus that belong to the same world as the racing. More courses became the stated priority, while multiplayer and other larger systems remained future concepts.
Screenshot: Titan Racers’ current browser view, captured November 6, 2026. This shows the current demo, rather than an archived October build.
Puddle: the body becomes the puzzle
Dekan’s Puddle follows a small brain inside a body of flesh particles. Gather more material, squeeze through gaps, stretch a tendril, or leave some of the body behind to hold a pressure plate. Each action works with a finite supply of material, making the blob’s shape part of the problem.
The handoff traces the experiment from isolated material studies into floating tower levels, a soundtrack, and a level editor. Feedback kept returning to the same gap: satisfying physics can arrive before satisfying level design. Making a body fun to move is one task; giving it a good reason to move through a space takes further play and revision.
Screenshot: Puddle’s current browser view, captured November 6, 2026. This shows the current demo, rather than an archived October build.
Neon Drop: making an upgrade feel different
Neon Drop starts with a familiar arcade pleasure: release a ball and watch it bounce toward pockets on a rotating deck. Its development notes describe repeated corrections to the feel of that drop, from a ball that fell too heavily to one that bounced for too long.
Observed play pushed the design toward multiball bursts. Progression brought another question: could a player tell what an upgrade actually changed? Clearer before-and-after values, activation effects, and attributed payouts made those benefits easier to notice. Tickets and chips are in-game currencies; there is no real-money wagering.
Screenshot: Neon Drop’s cabinet and rotating prize deck, captured November 6, 2026. This shows the current demo, rather than an archived October build.
Orbital Light / Orbit Lab: finding a game in a curve
Shared at Demo Day as Orbit Lab and later introduced for playtesting as Orbital Light, this experiment puts a small light in motion and asks the player to place temporary gravity wells ahead of it. You shape the route rather than steering directly.
The handoff follows single-rule physics studies into a game built around light, sound, and the trail left by a run. Its development offers another useful distinction: an interesting simulation still needs dependable game rules. Orbiting companions, for example, needed behavior players could rely on. The November 6 playtest invitation asks whether the learning curve feels right and whether the experience lands as casual play.
Play Orbital Light / Orbit Lab
Screenshot: Orbit Lab’s opening campaign view, captured November 6, 2026. This shows the current demo, rather than an archived October build.
What the demos taught us
The recurring lesson was that getting a mechanic onto the screen opens the design work. Car handling needs laps. A reward needs a visible cause. A physics puzzle needs routes worth learning. In the supplied development handoffs, human direction and repeated play shaped the work alongside AI-assisted implementation and checks.
Demo Day made those decisions easier to discuss. Builders could watch another person try a course, hear where the experience became unclear, and choose the next change. These remain evolving games, with room for feedback.
Pick a demo, play a few minutes, and tell its builder one specific thing: the turn that felt wrong, the mechanic you wanted more of, or the moment that made you try again.
Have a project in mind?
Start a conversation with RaidGuild
Tell us what you are building and where the guild could help.
Make a general inquiry