Skip to main content

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

I wrote this as I played through, the so the notes will be in order of my experience, with some minor editing after I finished. Overall, you have a decent start here. I have a number of suggestions here based on what I think would be good, but this is your game, so do what works for you.

As a general rule, it is good to have some margins around text, between it and screen edges or borders. Your buttons with text, such as the Start button, could use with a bit of margin on the sides.

Clicking on "Touch Grass" gets an error of "Uncaught TypeError: Cannot read properties of null (reading 'currentTime') at SampleNode._pause".

Challenge Modes does not seem to do anything. It would be nice if the button was disabled, or displayed a message, if it is not yet ready.

I like that you have the option for disabling the fancy font for those who would prefer a simpler one. Similarly, having the Disable Clankers option for Robophobes is a nice accessibility feature.

While Escape is a common button for pausing, on web it can also be used to exit full screen. While this game does not currently offer fullscreen, I would recommend adding support for pressing "P" to pause as well as Escape. It would also be nice to offer fullscreen for those who prefer it.

I regularly saw errors about Tweens being started without Tweeners.

While I was testing how the rope worked and trying to attache them to the broken bridge I ended up on the edge, but not over it. I seemed to be stuck at the edge. I could not jump or move away. I clicked to restart the level, but it just reloaded and moved me back to where I had been and the ropes still placed. I then chose to return to the menu and restarted from there, and it restarted me on the rope level. It gave me the message about getting the rope again, even though I had the rope when I started. After that message the screen stayed a bit darker than it had been.

With the game controls primarily using the keyboard, it would be nice if the pause menu grabbed focus, instead of needing to use the mouse. I'd also recommend changing the "Exit" button to say "Resume", as I would think of Exit as exiting the game.

I think the falling rocks on the second level progresses the difficulty a bit too fast. Maybe the rope can help with it, but I wasn't really understanding how to use the rope, and was still figuring out the best way to move around. Every time I was starting to do well a rock would hit me and I was not able to recover. I think this level increases the difficulty enough without the falling rocks.

I did finally mange to cross the first gap. The sign on the other side had the end of the message covered over by part of the UI.

It felt like sometimes the hands would start moving in towards the body on their own. It also seemed like sometimes they did not reach as far. I think it may be tied to how things were moving, but did not fully understand the mechanics.

I stopped to write the above, and when I went back to the game and closed the message, I was unable to move the hands. I got hit by a rock and after that I could move them again.

I had enough trouble with the basic controls, and this new technique of one handed pulling, using these small grips, was where I stopped. I really think you need to add in a more gradual difficulty progression and more time to practice and build up skills for the player. A bit more explanation, and possibly showing how things work, would be good. I still don't understand how the rope is supposed to be used. Pressing R with the rope did not seem to do anything.

The game concept is interesting. Controlling each hand individually is challenging, but a good mechanic. The basic level design is a good start, but needs to be refined to introduce new players to the game at a better pace. You've probably played a lot and so are good at it, and it may seem easy, but you need to step back and design for someone new who is learning. You have a good start here.

(1 edit) (+1)

I vastly appreciate this in-depth review and I have actually been working with a lot of these issues you have mentioned. Out of all the problems you've listed, I feel as though the most urgent is the lack of proper onboarding and I have been revamping the first two levels to give more practice time for later levels. The rope is by-far the most complex and basically useless feature in the game, so i really need to set up a dedicated tutorial for it. I think I may change some of the rope's functionality to make it less confusing/janky in the future.  Thank you for playing my game!:) Edit: I forgot to mention that the touch grass button and tweener errors are mostly due to the game not originally being built for browsers; the existence of the web version is so that more people will play it in this early access state, as people generally are more willing to play browser games on here. The touch grass button closes the game in the non-web version.

Web versions are definitely important for taking part in jams. Many people won't play download only. We tend not to do them either, but will for our jam. Still, we run them through anti-virus scanners and will play in a VM or sandbox. We are also on Linux, so any Windows only games go through Wine or a VM.

For the web export it is nice to add a closing screen, since the game stays up in the browser showing the last screen. We just added a basic "Thank you for playing" scene, and load that above anything else just before exiting. That gives clear feedback to the player that the game reacted and has ended.