← Return to game
Log in with itch.io to leave a comment.
Wow! The gameplay it's very nice. I hope to I'll to develop games in pico-8 with this quiality. You are aweseome!
This is so polished! Very nice. I love everything about it. I’m not very good at it though haha
I triggered a message to appear on screen then moved away from the object before dismissing it with X. The message remained permanently on the screen after that. Had to refresh the browser to get rid of it and start over.
ooh, nice catch. Movement should be disabled while textboxes are active, I'll patch it up.
edit: fixed!
Nice animations. Your slimes are full personality.
Thanks! I had a lot of fun animating those little guys!
I crashed the game when I tried to throw a goblin sash.
Runtime error line 264 tab 3 food.effect(e,food.str)
Attempt to call field 'effect' (a nil value)
in ent_eat line 264 (tab 3)
in throw line 96 (tab 1)...
Yeah, this seems to be an issue I introduced when adding throwable weapons. Should be fixed in a coming patch. Thanks for bringing it up!
← Return to game
Comments
Log in with itch.io to leave a comment.
Wow! The gameplay it's very nice. I hope to I'll to develop games in pico-8 with this quiality. You are aweseome!
This is so polished! Very nice. I love everything about it. I’m not very good at it though haha
I triggered a message to appear on screen then moved away from the object before dismissing it with X. The message remained permanently on the screen after that. Had to refresh the browser to get rid of it and start over.
ooh, nice catch. Movement should be disabled while textboxes are active, I'll patch it up.
edit: fixed!
Nice animations. Your slimes are full personality.
Thanks! I had a lot of fun animating those little guys!
I crashed the game when I tried to throw a goblin sash.
Runtime error line 264 tab 3 food.effect(e,food.str)
Attempt to call field 'effect' (a nil value)
in ent_eat line 264 (tab 3)
in throw line 96 (tab 1)...
Yeah, this seems to be an issue I introduced when adding throwable weapons. Should be fixed in a coming patch. Thanks for bringing it up!