Skip to main content

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

Thank you so much for playing it live and for writing all of this down — this is the most

detailed feedback I've ever had on anything I've made. And yes please, I'd love the VOD link

when it's up!

Also, my views jumped to 52 on September 2nd, which is by far the most this game has ever had

in a single day. Was that the day you played it?

Your notes were specific enough that I could go find the causes in the code, so I fixed all

five and just uploaded the new build.

1. The pause after the bite — you were exactly right, and it was literally a "+ 500" sitting

in the code. Half a second between "Bite!" and the ring appearing. The ring now starts the

moment the bite appears. The ring's own timing is unchanged, so the difficulty is the same.

2. The background freezing — I'd frozen it on purpose, because redrawing it costs 18ms and a

frame is only 16.7ms, so it stuttered every 0.7 seconds. But looking again, when the three

background frames are pre-baked, swapping them costs 0ms. So the background keeps living now,

and a critter already walking past finishes its walk.

3. The extra click after reeling in too early — I found why. When you're late, the game ends

the round by itself. When you're early, your click is what ends it, so it cost one more press.

Same mistake, more work. They're the same now.

4. "First page" — a plain mistake, and only in the English text. Korean, Japanese and Chinese

all said "Previous page" already. Fixed.

5. The lag on Slippery — this one turned out to be the most interesting, because it wasn't lag.

Slippery is a fish trait where the shrinking ring drops to 30% speed partway through. And you

weren't the first person to call it lag: someone else said the exact same thing a while back.

When two people who've never met read it the same way, the effect isn't communicating. The

problem was never the speed — it was that nothing said it was on purpose, because a frame drop

and a deliberate slowdown look identical on screen. So now the crayon line shivers while the

ring is crawling. Lag freezes; a shivering line doesn't.

I wrote a devlog about all five if you're curious.

About the AI question — that's a fair thing to ask. The design, the fish, the rhythms and every

decision are mine; the code was written with AI. I'm still learning to program, and I've bounced

off it before, so hearing "you could make this yourself" from someone who actually played it

means a lot. It's something I want to work toward.

Thank you again — genuinely. Number 5 especially, I only found because you narrowed it down to

"only with the Slippery ring."