Knight Trap is a platform-strategy game released on April 4, 2011. The goal is to guide a certain number of knights past traps to the top of the level.
The game was first revealed in an image on the NES skin, which at the time was believed to be a completely separate NES game. Later, it received a sequel called Office Trap.
This section is incomplete. You can help by adding the missing info.
The game involves the player to traverse several platforms, sometimes setting off traps, in order to make it to the top of the castle. The number of knights to complete the level varies from level to level.
This section is incomplete. You can help by adding the missing info.
Need four knights at the top; seven lives. Each floor has a slime trap and crumbling platforms. To avoid the most traps, only step on the first floor's trap, regular jump, and continue double jumping onto crumbling platforms so as not to set off more traps.
This collapsible box contains a video walkthrough for this level in Knight Trap. If you would like to view it, click the[show]tag.
Knight Trap, the name previously unknown at the time, was previewed on March 18th 2011. Along with the post was an image of one of the levels.
On March 23rd, a video preview of the game was launched. The preview shows the titlescreen of Knight Trap, the intro, and some levels were shown in the video (below).
If the player leaves the titlescreen of Knight Trap untouched, the Knights will start to come in different numbers. Eventually, all the Knights will jump into the castle, then there will be for a few seconds no Knights on the screen.
The character, and traps from Knight Trap appeared in the Nitrome 2.0 skin in a building.
The title is almost certainly a reference to the 90's FMV game Night Trap.
There is a glitch where some platforms can be inaccessible and the Knight will continuously walk in the air until he reaches a platform. This will be fixed if you reset the level or die.
There is also a glitch where if the player reset the level the traps will remain where they were. After the player reset's a second time, it will be fixed.