On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags
(+1)

Made it to wave 21! Had to play the tutorial twice before I "got it" but after that I felt like I understood how to play.

I think with a bit better UI design this could be really fun! As it stands it takes 2 clicks to fire/heal/defend/etc and that typically involves moving the mouse all the way down to the bottom of the screen to all the way to the top (or close to it). That's a lot of precise movement that I'm being asked to do while also trying to rotate the ring to track my shots.

I also found that if I clicked on the Fire button while it was on cooldown, it de-selected my current die which meant I had to go back down and select the proper die, wasting valuable time.

Not to mention having to scroll! I barely used the "defend" command because it was so out of the way to reach it. I never used "Stun" for the same reason.

A possible remedy (I think) is to have the 4/6/8/10/12/20 buttons be built into the fire/heal/defend buttons and there should be a separate indicator for how much of that resource you have. That means firing is just one button.

Another remedy would be to bind hotkeys to all of the commands (both selecting dies and fire/heal/etc). That would make it much easier to engage strategically rather than keeping plates spinning.

Really cool idea, would love to see a post-jam build!

Thanks for the feedback! The UI was actually my biggest worry with this game, as I teaching myself how to use Godot's control and vScroll nodes while working on it. I was actually planning on doing what you said about the hotkeys for each dice, but I couldn't get that to work in the time I had. Still, I'm glad to see that you enjoyed it!


Also, fun fact: when you click the fire button while it's on cooldown, it doesn't actually deselect the current die due to a bug lol
The dice icon changes from the selected color to the normal color whenever you click any other button, even if the button is disabled. However, actually deselecting the die only happens when the button's function goes off, so not when a disabled button is pressed. I just find it really funny how I overlooked that.