Recent reviews by Rimdes

Casual coop puzzle game.

• Dynamic action-based puzzles.
  
• Checkpoints are frequent, so if you fail you don't lose that much time. The game allows for a fast iteration and improvement.
  
• The game allows the struggling player to complete their own part of the puzzle even if the faster player is ahead. Unlike some other games where the struggling player is just teleported forward.

• In a combined camera mode it's hard to keep track of your own character, especially when the camera distance is high.
  
• Can't turn off forced split screen. This is relevant when you have the 2nd player right next to you, playing on another monitor.

• Both players can hold Q (B on gamepad) to skip cutscenes.
  
• Use mouse for gun fights even if you are using gamepad for the rest. Adjust mouse sensitivity in input settings.

Not so idle, but very addictive.

First I first multiple monsters, acquire a magical parkour ability with super speed. Almost defeat a dragon.

Then I am captured by a few guards with pointy sticks. Run away? Fight back? Nah, back to the courthouse.

The best thing is the moment of capture was just a black screen. Even the developer didn't figure out how to make sense out of it.

People complain this is Mary Sue, no, Mary Sue would be fine. This is Mary Stupid.

Want to go on a 4 year NERV-wracking adventure to Duna? This game is for you!

Parachute still breaks :'(

The combat is surprisingly satisfying.

As a person who doesn't play turn-based games, I love it. The controls are a bit unintuitive however, so be ready to spend some 10 minutes remapping everything :)

The game crashes every hour or so. It's not bad, but I can't recommend something where you lose progress that often.

Relaxing, fun, replayable. Enjoy!

I love this so much. You are given a programming language which is basically an automaton programming.
You are given an input string and you define a list of instructions.
The input string is basically the state.
Each instruction is tried in order, once matching instruction found, restart the execution while keeping the state string.

The program finishes when no instructions can be executed.
It's brilliant in its simplicity.

There are optional challenges, you have to write a solution using at most given number of instructions.
I am not the biggest fan of that, but I do see it can be enjoyable for some people to optimize their solutions this way.
I am more used to execution time limits, not source code size limits.