Fandom

Chip's Challenge Wiki

Madness I

1,094pages on
this wiki
Add New Page
Talk0 Share


Madness I is the 28th level in Chip's Challenge Level Pack 2. It was designed by Dave Borgman, and was there named More Madness, as the order of Madness II and it was reversed in the set. Unlike that level, Madness I is not difficult at all, and the only significant puzzle is that of figuring out a partial post to reach the exit.

To complete it, take the chips across the top, then the chip from the paramecium area on the top, and go downwards to collect a second chip. Finish with the one to the right and the lowest chip, then play down to steal one chip from the bugs. Now, play to the southeast corner and collect the final two pairs of chips, arriving to the southwest. From here, sneak into the beehive and collect the final two chips, then move 3R U specifically to escape without having to wait.

In the four corners were four red buttons, which cloned blocks onto four brown buttons to allow these four blocks to escape the traps; move blocks 3 and 1 into the bombs, block 4 UR, and block 2 west into the teleport, which causes a partial post and allows Chip to exit.

Fix for Lynx

The eight chips by the ice have ice under them themselves, which makes Madness I unplayable in Lynx. To fix it, simply remove the ice, as their original intentions were to keep Chip from sliding across the level as a shortcut as he does when picking up the chips in this route. There is no further need for Chip to use the buttons anyway, and the additional use of the same shortcut would only take Chip back to an already complete area.

Walkthrough

CCLP2 level 28 solution - 266 seconds00:35

CCLP2 level 28 solution - 266 seconds

Previous LevelCurrent LevelNext Level
← Frozen Floors Madness I Fire and Water →

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.