✨ HEYO!! It’s Rainbow back again with another chaotic masterpiece!!! ✨ And this time... it’s a project that’s 98% effort, 2% donut, and 1000% BUGS. Welcome to: "GET THAT DONUT!" (long description ahead, read the whole) aka: The project that slowly destroyed my sanity but also gave me life? Let me explain. I made this game for the Scratch Week Studio – Mini Game Madness and let me just say... it lives up to the name. Because it was MADNESS. I spent like one to two whole weeks on this thing — mostly because I had to stop every few seconds and pretend to study (school really said “no fun allowed” this year). This is officially the longest I've worked on a project on this account (on this account... let's not talk about the secret old one where I coded through the apocalypse ). So, what’s the game about? You chase a donut. That’s it. Kidding! Kind of. ✨ When you click the green flag, you’ll see a shiny instructions button (oOoOoh fancy right?). Click that, read how to play, and then begin your glorious quest to GET. THAT. DONUT. ?⚔️ !BUT WAIT. THERE’S A BUG. ! Yeah… the game just randomly stops after a while .Not like, "oh no you lost" kind of stop. More like: everything freezes, the game over screen disappears, buttons ghost you, and life as we know it ends. I’ve tried everything to fix it. I’ve cried. I’ve yelled at my code. I’ve stared at the screen dramatically. Nothing works. So, I did what any desperate Scratcher would do: ✨ I added cloud data ✨ That way, even if the game rage-quits life, you can still check your score and pretend everything’s fine =) If you somehow manage to find the cause of this evil bug, I will literally explode from happiness.!!! =D Feel free to remix it and help me out, or just send me your wisdom. Coding angels, I am begging !! HAPPY SCRATCH WEEK!! ✨ I hope you enjoy this ridiculous game as much as I enjoyed (and suffered) making it. Bug or not, donut or bust — this one’s for you ❤️ — ✨Rainbow ✨ update:13/5/25 OH NO. IT’S ME AGAIN. RAINBOW. BACK FROM THE DEBUGGING UNDERWORLD. And guess what? I fixed That cheeky bug! But at what cost? The game doesn’t freeze anymore. Amazing. Glorious. I danced. I celebrated. And then the timer disappeared. Welcome to: GET THAT DONUT: THE REPLAY CURSE EDITION Also known as: “Rainbow slowly unraveling while staring into the void of broken scripts.” Let me paint the scene. You defeat the first round. You emerge victorious, score blazing, confidence soaring. You hit replay, ready to dominate again. And then—nothing. No countdown. No dramatic pressure. No “oh no I’m running out of time” adrenaline. Just… silence. The donut’s still there. Your determination is still there. But the timer? Vanished. Yeeted out of existence. Probably on vacation. It’s gone. I went back into the code. I checked every script. I rewired it. I whispered to it. I made offerings of digital cookies. Nothing worked. The replay button now summons a game with no clock. Just eternal donut chasing. A limbo of breakfast-based ambition. So yeah. I won the battle, but I might be losing the war. The freeze is gone. But now the tension, the urgency, the sweet ticking chaos of time... has left the building. If anyone knows how to resurrect a timer from the dead, I am open to sorcery, science, or interpretive dance. Help a struggling coder out. Until then— The game is playable. The donut is gettable. But the timer? It’s a myth. A legend. A casualty in the Great Bug War of Rainbow’s Scratch Account. In Summary: Timer gone? Probably hiding or never restarted. Cloud data gone? yes because no one viewed my project!! Game’s still playable? YES. Donut’s still chaseable? ABSOLUTELY. Is Rainbow okay? Spiritually debatable. But clearly unstoppable. — Rainbow (Coding through the chaos. Fighting ghosts in the machine. Probably still not doing homework.) (comment: the cursed donut) Ya still here???? Happy Scratch week!!!!! Yum Yum Yum donut!!! hewo!! (psst... try clicking the space button. trust me, it will help you a lot) bye =D -Rainbow
