Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
A jam submission

dreamseamView game page

Fly the seams. Stay close to Ito. Don’t wake up.
Submitted by daguaroadtrip — 9 hours, 24 minutes before the deadline
Add to collection

Play game

dreamseam's itch.io page

Results

CriteriaRankScore*Raw Score
Overall Enjoyment#13.9003.900
AI Direction & Adaptability#33.9003.900
Theme Fidelity & Creativity#53.9003.900
Production Velocity#83.4003.400

Ranked from 10 ratings. Score is adjusted from raw score by the median number of ratings per game in the jam.

The Biggest Challenge
Finding the core loop, and then calibrating it. The AI could produce plausible systems far faster than we could tell which one was the game, so the loop was found by cutting rather than by adding, and every number in it was set by a playtest rather than by a guess. The loop that survived: flying close to the shapes pays, and flying wing to wing with Ito charges a bond that fuses the two of you into one being — the only thing that fits through the Climb. The decision that made it a game was coupling those two: flying together in safe open sky charges nothing at all. Before that, the Buddy was a shelter you could hide next to; after it, togetherness is something you can only earn where it is dangerous. That single rule is now an assertion in the test suite, because it is the one thing the whole design rests on. Then the calibration, and almost all of it came from watching people play. A first-time player could not get past layer 1 at all until the director sat beside her and explained each mechanic — that verdict produced the guided first dream and a one-per-session mercy on the opening layer. A flown probe showed that nobody, human or synthetic, was passing the Climb: auto-UNISON was spending the merge 300 m before the one wall it was the key to, so the bond is now held and spent at 150 m. The scoring pocket went to 9 m with hysteresis at 13 and one number per pass, because a stream of small numbers reads as noise and one number reads as a reward. Six layers were measured across two seeds and two pilot skill levels to check the curve actually rises. The hardest part was not building any of it — it was accepting how much had to be thrown away between the version that sounded good and the version that played.

AI Tools Used
Claude (Anthropic), used through Claude Code, as the pair programmer for all of the code. Image generation for the crystalline logo and the cover art. The six per-layer music tracks were AI-generated (album "Dusk Drift", Treblo) and then processed by hand — low-passed at 3 kHz, normalised to -20 LUFS, faded — to the director's brief of "no highs, always fades, never loud". Every sound effect is synthesised in code; there are no audio asset files.

Areas Where AI Was Used
Code: all of it — flight, procedural world generation from a seed, the sky, the HUD, the 3D bedroom that opens the game, and the automated test suite. Music: generated, then processed by hand. Sound effects: synthesised in code. Images: the logo and the cover art. Not AI: every design decision, playtest verdict, difficulty call and art-direction call was the human director's. Several AI proposals were rejected outright — a throw/launch mechanic for the Buddy (twice), an angel-winged version of the fused form, and, in this last session, making the recording pilot invulnerable so the trailer clips would stop ending in crashes. That last one was cut with "it's no use making it survive the crash, it has to be a well-flown scene."

Leave a comment

Log in with itch.io to leave a comment.

Comments

Host

No matter how many times I try, I always get stuck just past the entrance to the building and end up crashing. I still don't understand what exactly I did wrong.

The 3D graphics are stunning, and the sensation of floating is delightful. I really wanted to see a little more of the game, but I gave up.

Still, I think this game has genuine appeal. 🙂

Developer(+1)
Thank you for giving it several tries, and I'm sorry the game didn't make the failure legible. If a player reaches the same point repeatedly and still can't tell what went wrong, that's a communication problem in the game, not a lack of effort. From your description, I suspect this was the first Gatehouse/Climb section: the intended read is to stay close to Ito and the nearby geometry until BOND fills, then use UNISON (F, or Auto-UNISON) for the narrow route — but the game clearly isn't teaching that well enough in motion. I'm treating onboarding and failure feedback as the highest-priority post-jam issue. I'm glad the flight and world still showed their appeal, and I really appreciate you describing exactly where the game lost you.
Host

Yes, I think you're absolutely right about the location. Thank you. That made sense, so I tried it again. However, even though the gauge was at about 80% on a few of my attempts, pressing the F key didn't seem to have any effect, and in the end, the result didn't change. It seems that even understanding the theory can't make up for my lack of skill...

Developer(+1)
Please don't blame your skill here — your 80% example exposed a real feedback failure. The F press was being read, but UNISON requires 100% SYNC, and the jam build silently rejected the input before that point, which made a working key look broken. I have now pushed the post-jam update: pressing F early shows the current percentage and “UNISON NEEDS 100%,” Ito tells the player to stay at his wing, and the Climb has a clearer visual lock and warning. Thank you for trying again and reporting exactly what happened; that follow-up directly changed the game. If you ever feel like giving the update one more attempt, I’d love to know whether the refusal and the Climb are finally readable — but no pressure after all the attempts you already gave it.
Host

After playing about 10 more times, I finally made it to the next, darker stage🌟
I now understand what “UNISON” means, and I feel like I’ve gotten a sense of that pleasant feeling it brings.

Thank you so much for letting me have such a wonderful experience! 🙂

Submitted

Beautiful entry. The engineless glider — no throttle, no brake, just pitch and momentum — made "DIVE" a mechanic instead of a label, and following Ito's red thread with the SYNC/UNISON meter is one of the most genuinely load-bearing takes on BUDDY I've played; your buddy isn't a passive companion, it's the line you read to fly well. The dream-world art and the hand-processed, always-fading music sell the mood completely. Loved reading that you rejected the throw/launch-the-buddy idea twice — the restraint shows. Congrats on a standout; wishing you well in the ranking.

Developer
Thank you — this is such a thoughtful read of what I was trying to build. I'm especially glad DIVE came through in the glider physics and that Ito felt load-bearing rather than decorative. Rejecting the throw/launch version was the turning point, so hearing that the restraint shows means a lot. Thank you for playing closely and for taking the time to write this.
Submitted

I really enjoyed this game although I didn't like how it stopped in the tutorial. Instead, I wish it let me learn from my mistakes 

Developer
Thank you, and that's fair feedback. The pauses came from an early playtest where a new player could not clear the first layer without someone explaining the mechanics, but I agree that stopping the flight works against learning through movement and mistakes. I'm looking at a lighter, in-motion approach for the post-jam update. I'm glad you enjoyed the game despite the interruption, and this is exactly the kind of feedback I needed.
Submitted

Of course. I'm still new to game dev, so I'm glad I actually had some good feedback despite my lack of experience. I really did enjoy your interpretation of "dive"  its vary fun, and I can't wait to see what you do with it post-jam. 

Developer(+1)
Being new to game development doesn't make your feedback less valuable — the useful part is what you noticed, not how many years you've been doing this. You described the contradiction very clearly: a game about movement was stopping the player to teach movement. That observation is now reflected in the live post-jam update: only the first lesson pauses, the later lessons happen during flight, and Ito's dialogue moves out of the flight corridor at speed. Thank you for the encouragement and for helping push the game toward the learn-by-doing version you had in mind. If you revisit it, I'd be very curious whether it feels better now — and I hope your own game-dev journey keeps being fun.
Submitted

It’s fun—but pretty challenging!

The experience of flying alongside a partner is really entertaining.

I kept getting a "Game Over" because I wasn't skilled enough,

but it’s the kind of game that makes you want to keep trying so you can see what lies ahead.

It’s amazing to create a game of this quality in just three days!

Developer
Thank you! I'm really glad flying alongside Ito was entertaining and, even more importantly, that the challenge made you want to try again instead of stop. Difficulty and onboarding are the two areas I'm watching most closely after the jam, so your experience is very useful. I hope you get to see what waits deeper in the dream!
Submitted

It feels absolutely amazing to fly around this beautiful world. ✨

Developer
Thank you! Making the world feel beautiful simply to fly through was one of my biggest goals, so I'm really happy that feeling came through. ✨