Small bug story from this week.

A player told me the game "froze". Attack did nothing, no damage, nothing. Turned out it wasn't frozen at all.

Opening Settings, the Bank or the Store pauses the fight. That part was on purpose. But if you then hid the menu or went fullscreen, the panel vanished and the pause flag stayed on. So the fight just sat there waiting forever.

The fix was boring. Closing a panel any way at all now clears the pause, and hitting Attack un-pauses too, just in case.

The part I liked more: I wrote a little random-click tester that mashes buttons, opens panels, toggles fullscreen and checks the fight still moves. It found no more stuck states after the fix. I also added a quiet error report so if it ever happens to someone again, I can see what they clicked last.

It's plain JS, no engine. The game is SnowRSPS Mini if you want to try to break it: https://snowrsps.com/io

How do you all handle pause state? One flag, or a stack of reasons?

I rebuilt my little browser clicker into a wave roguelike. You fight waves, a boss shows up every 5, and each level you pick 1 of 3 blessings. Some are cursed, big power with a real downside.

There are 6 zones, 63 items, a collection log, boss pets and prestige. Talents and the log stay when you die. Leaderboards are checked on the server. Plain JS, no engine.

Free, no account, works on phones. It's a mini version of a bigger game I run, but it plays fine on its own.

New this week: a 250-level Snow Pass, checkpoints, hold-to-attack, a shop and a live feed of other players' big drops.

Feedback I'd love: where did you get stuck, and did the first boss feel fair?