Escape the Room 2

Player Rating3.34/8

"#709 overall, #25 for 2005"
based on 213 ratings since 08/20/2005
played 2,417 times (finished 296)

Story Difficulty3/8

"trek through the forest"

Play Length1/8

"Make sure not to blink"

Maturity Level4/8

"need to be accompanied by an adult"
Contains content that may not be suitable for persons under age 13. If this were a movie, it would probably be PG.
You thought you have gotten out but that was only the beginning. Now you are in a differant room, and you still have to get out. Find new clues to get out of this place.

Player Comments

Slightly better than the first, but not by much.

Again, I really dislike the lack of a plot but that could be overlooked if this had interesting gameplay, but it didn't have that either.

At least this time you might have needed to think a bit to see how to solve the puzzles.
However, the dead end door was an annoying problem, and so was the fact that you had to guess the code.
Putting little clues everywhere so the player had to figure out the order of the code would have been nice, but there was none of that.

And can I just reiterate that the plot was nonexistent?
You're in some room with some stuff and the door is also locked here and you need a key to unlock the door.
Okay. But why are you stuck in this place, and why did whoever that left you here leave you things to get out?

I do agree that I like the pictures, however. Kept it from being too bland like the last one.

2/8. Again, slightly better but it needed a lot of work.
-- Seto on 11/24/2017 4:52:26 PM with a score of 0
I enjoyed this as there was actually some improvement from the first, because while this is still a bit easy to beat, it wasn't as basic as the previous one that I've played. I also felt that the use of pictures helped add a bit more to this story, keeping things from becoming too dull as I was trying to escape.

Also, another thing that I found to be improved on is the length. While not being a long game, it wasn't as short as the first and the solutions while still easy to solve, weren't too overly obvious. However, sometimes I couldn't help but feel that descriptions for things and items were a bit too basic at times, but that's only really a minor issue in terms of the overall presentation.

There was something that I found to be a bit odd. Was there really any use for the money? Because I found myself completing this storygame without the use of that item, and it seemed like everything else at least had some purpose in escaping.

Regardless of that, I felt that this was a welcome improvement from the first game in this series. So nice work in creating a fun storygame, one that's rather simple, but not without it's share of fun.
-- TharaApples on 2/28/2017 2:59:48 PM with a score of 0
eh, very easy
-- GbyteM3 on 10/29/2019 4:06:17 AM with a score of 0
I was hoping for this to be better than the last one. This is literal garbage and I can't wait to end this game
-- Anonymous on 7/8/2019 3:06:27 PM with a score of 0
how in gods name did you manage to make the same game but with an extra second of playtime
-- slenderman on 7/6/2019 11:38:28 AM with a score of 0
I love it :)
-- IvyGreen on 3/23/2019 9:14:30 AM with a score of 0
Looking forward to the 3rd part!
-- stealth5106 on 2/11/2019 12:15:12 PM with a score of 0
Um... This game was poorly executed, and also seemed as if there was no storyline. Please spend more time on your storygames.
-- hbroc3 on 5/29/2018 7:36:33 PM with a score of 0
ahhhhhh it was not good make it better and i did not like ur confidence with it beacause it sucks and you know it and you are conceited whatever that means
-- i am bored on 3/16/2018 10:44:38 AM with a score of 0
Just a few gameplay problems I experienced:
1. If you go to the Door without the gold key you’re stuck without an option to exit to the Red Kitchen.
2. I believe I checked all my options and I don’t see where there was a hint at the safe code. I used trial and error to get it, but did I miss something?

FYI - I was playing this in Chrome on an iPad (not sure if it’s just my browser that caused issues).
-- Nate on 3/3/2018 8:24:42 PM with a score of 0
Show All Comments