FANDOM


A bug, often known as a bee and called an ant in Chip's Challenge 2, is a monster in Chip's Challenge. It always stays to the left when it moves, so if there is no wall to the left of it, it will turn left. If there is no wall within its vicinity, it will resort to continually turning clockwise in a 2-by-2 square until a wall appears to the left of it. It will die in water, but treats fire as a wall.

The following diagram illustrates these properties:

Bug demo

Because this is the bug's first move, it will not be affected by the force floor, and will step U onto the ice space. Meanwhile, if Chip steps on the dirt, the flippers will keep him from being killed. If Chip waits to collect the flippers, the bug will circle across the northwest and then continue circling around this thin wall if the flippers are then removed. Should they still remain untouched, the bug will circle around the southwest. If the bug were left to go back to the force floor before Chip removed the flippers, the level would become unsolvable as Chip could not collect the flippers safely. In Lynx, this level is both unsolvable and unplayable because the bug would already be stuck on its first turn and the flippers are under the dirt.

The quickest route through the level is 2R DR, and using boosting techniques, 2R just ahead of the bug into the exit. The bug, in this situation, would continue to move DR, be slid back to [1, 1], and then move DR and slide back without cessation.

One further important gameplay situation which pertains to the bug is the Controller and Boss Glitch.

Trivia

  • According to Melinda, the Chip's Challenge bug originates from Africa, and her collection accidentally got loose into the clubhouse.
  • The bug is the first monster seen in the game, originally found in Lesson 2.

See also

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.