About: Security Breach   Sponge Permalink

An Entity of Type : dbkwik:resource/U3deC9qR3btFCKjN3a2lUg==, within Data Space : dbkwik.org associated with source dataset(s)

Security Breach is the 53rd level in Chip's Challenge Level Pack 2. I was created by John Matthews. While Chip can simply take the level's two chips, this causes the pink ball controlling the brown button to trap or release the one controlling the blue button too soon, and therefore cause the tank to open a column of toggle walls. This sets off the "security system" by releasing more pink balls into the exit corridor, who cannot physically be passed when released. To avoid this, Chip must keep the rhythm going in some way.

AttributesValues
rdf:type
rdfs:label
  • Security Breach
rdfs:comment
  • Security Breach is the 53rd level in Chip's Challenge Level Pack 2. I was created by John Matthews. While Chip can simply take the level's two chips, this causes the pink ball controlling the brown button to trap or release the one controlling the blue button too soon, and therefore cause the tank to open a column of toggle walls. This sets off the "security system" by releasing more pink balls into the exit corridor, who cannot physically be passed when released. To avoid this, Chip must keep the rhythm going in some way.
Level
  • 53(xsd:integer)
dcterms:subject
chips available
  • 2(xsd:integer)
difficulty lynx
  • 2(xsd:integer)
bold lynx
  • 57(xsd:integer)
Password
  • XYZK
levelset
bold difficulty ms
  • 1(xsd:integer)
bold ms
  • 58(xsd:integer)
bold complexity ms
  • 1(xsd:integer)
difficulty ms
  • 2(xsd:integer)
bold difficulty lynx
  • 1(xsd:integer)
bold complexity lynx
  • 1(xsd:integer)
Hint
  • Now that you're in, collect the security cards and go on the next room. Don't set of the security system.
chips required
  • 2(xsd:integer)
Name
  • Security Breach
dbkwik:chipschalle...iPageUsesTemplate
Time
  • 75(xsd:integer)
abstract
  • Security Breach is the 53rd level in Chip's Challenge Level Pack 2. I was created by John Matthews. While Chip can simply take the level's two chips, this causes the pink ball controlling the brown button to trap or release the one controlling the blue button too soon, and therefore cause the tank to open a column of toggle walls. This sets off the "security system" by releasing more pink balls into the exit corridor, who cannot physically be passed when released. To avoid this, Chip must keep the rhythm going in some way. This monster rhythm is based on the fact that the pink ball in the northwest is ahead of the tank in the monster order, and will turn the tank around before it touches the green button. Because the monster order works differently in Lynx, the tank hits the green button before he can be switched, which makes Security Breach unsolvable. The solution is easy; cover the brown button with block 2, from the far right side, which maintains equilibrium and allowing Chip to collect the two chips and exit with no danger. This route is trickier to find than to perform, in John Matthews' emerging style, which raises the rating.
Alternative Linked Data Views: ODE     Raw Data in: CXML | CSV | RDF ( N-Triples N3/Turtle JSON XML ) | OData ( Atom JSON ) | Microdata ( JSON HTML) | JSON-LD    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software