Please create an account or Login! Have fun!

User:DeltaCore/Button: Difference between revisions

Jump to navigation Jump to search
No edit summary
m (DeltaCore moved page User:Cowman/Button to User:DeltaCore/Button without leaving a redirect)
 
(17 intermediate revisions by the same user not shown)
Line 1: Line 1:
A '''button''' is a utility tile connected to one or more other tiles, such as walls, monsters, traps, wiring, clone machines and more. The color of a button determines its specific function, however all buttons share the following characteristics:
{{#get_web_data:url=https://beta.bitbusters.club/wiki/level_listing.php?pack=cc1&level=33|format=json|data=NAME=name,DESIGNER=designers,MS_BOLD=MS_bold,LYNX_BOLD=LYNX_bold,STEAM_BOLD=STEAM_TIME_bold,MS_LUCK=MS_luck_diff,MS_EXEC=MS_exec_diff,MS_ROUTE=MS_routing_diff,MS_CASUAL=MS_casual_diff,LYNX_LUCK=LYNX_luck_diff,LYNX_EXEC=LYNX_exec_diff,LYNX_ROUTE=LYNX_routing_diff,LYNX_CASUAL=LYNX_casual_diff}}


* Buttons are pressed when [[Chip]], [[Melinda]], a [[Block|block]] or any monster enters the same tile as a button.
* Buttons can be held down as long as the player, a block or any monster remains on the same tile. Holding down a button may have no effect depending on the color button and to what the button is connected.
* There is no guarantee a button is connected to something nearby. Many levels use buttons as an element of the puzzle where the player must determine its effect through trial and error.
__NOTOC__ <!-- This removes the table of contents -->
== Black Button==


{{Infobox Cowmantest
So this is the damn level 33 of set 0!
|name = Black Button
|image = [[Image:BlackButton.png]]
|cc1 =
|cc2 = Yes
|cc1index  =
|multidirectional = No
|moves = No
}}


The '''black button''' is a button introduced in Chip's Challenge 2. It has the opposite behavior of a [[pink button]]: it will activate any [[wire]] it is connected to ''except'' when stepped on by [[Chip]], [[Melinda]], [[block]]s, and [[monster]]s.
* Title: {{#external_value:NAME}}
 
* Designers: {{#external_value:DESIGNER}}
{{clear}}
* MS Bold: {{#external_value:MS_BOLD}}
 
* Lynx Bold: {{#external_value:LYNX_BOLD}}
== Blue Button ==
* Steam Bold: {{#external_value:STEAM_BOLD}}
 
* MS Luck: {{#external_value:MS_LUCK}}
{{Infobox Cowmantest
* MS Exec: {{#external_value:MS_EXEC}}
|name = Blue Button
* MS Routing: {{#external_value:MS_ROUTE}}
|image = [[Image:Blue Button.png]] [[Image:BlueButtonCC2.png]]
* MS Casual: {{#external_value:MS_CASUAL}}
|cc1 = Yes
* Lynx Luck: {{#external_value:LYNX_LUCK}}
|cc2 = Yes
* Lynx Exec: {{#external_value:LYNX_EXEC}}
|cc1index  = 40
* Lynx Routing: {{#external_value:LYNX_ROUTE}}
|multidirectional = No
* Lynx Casual: {{#external_value:LYNX_CASUAL}}
|moves = No
}}
 
The '''blue button''', sometimes called a '''tank button''', reverses the direction of all moving [[tank|tanks]], with some exceptions, in the current level when stepped on. If there are no moving tanks remaining in the level, with one of the same exceptions, the blue button has no effect.
 
Tanks will not be reversed if they are standing on [[ice]] or [[force floor|force floors]], unless Chip touched the blue button on his initial move, or landed on it after sliding over one ice, force floor, or [[teleport]]. Tanks standing on [[clone machine|clone machines]] will only switch in the MS version or the most recent [[Tile World]] emulation, and only under specialized circumstances. When this happens, the [[Frankenstein Glitch]] has occurred. This glitch is seen in [[David Stolp]]'s ''table of contents'' and ''ode to a cloned tank, pointed the wrong way''.
 
=== See also ===
* [[Tank]]
 
{{clear}}
 
== Brown Button ==
 
{{Infobox Cowmantest
|name = Brown Button
|image = [[Image:Brown Button.png]] [[Image:BrownButtonCC2.png]]
|cc1 = Yes
|cc2 = Yes
|cc1index  = 39
|multidirectional = No
|moves = No
}}
 
The '''brown button''' or '''trap button''' is a tile that releases the [[trap]] to which it is connected, if any, when moved to the lower layer by any [[object]] (it is unconditional [[acting floor]]) or if it already starts on the lower layer. If the brown button does not have a connected trap, it has no effect when stepped on. More than one brown button can release the same trap, but more than one trap cannot be released by the same button.
 
Under the [[ruleset|pedantic Lynx ruleset]] and in [[Chip's Challenge 2]], brown buttons are automatically connected to the next clone machine in reading order. In Chip's Challenge 2, brown buttons cannot be wired to clone machines, but [[Pink button|pink buttons]] can.
 
The brown button is the only button not affected by the [[Button Smash Glitch]] in a specific case. Only currently trapped items will fail to be released when the button is "smashed".
 
=== See also ===
* [[Trap]]
* [[Button Smash Glitch]]
* [[Sokoban level]]
 
{{clear}}
 
== Green Button ==
 
{{Infobox Cowmantest
|name = Green Button
|image = [[Image:Green Button.png]] [[Image:GreenButtonCC2.png]]
|cc1 = Yes
|cc2 = Yes
|cc1index  = 35
|multidirectional = No
|moves = No
}}
 
[[Image:Green Button.png|left]]
 
The '''green button''', informally known as a '''toggle button''', is a [[tile]] in [[Chip's Challenge]] that causes all [[toggle wall]]s contained in a level to switch state. If a green button is touched by any moving object, the walls switch, but two separate presses of different buttons on the same turn will cancel each other out. Therefore, if an odd number of presses occur on the same turn, the wall will switch; if it is an even number, nothing at all happens (the latter case is one of the only two possible ways to solve [[Perfect Match]] in CC1, the other being the [[Concussion Rule]]).
<!--"cancel out" is actually not true ^, block off the bees and the fireballs only in Monster Lab and watch what happens-->
 
In [[Chip's Challenge 2]], green buttons cause [[green chip]]s and [[green bomb]]s to switch state in addition to toggle walls.
 
Green buttons do ''not'' switch toggle walls on [[clone machine]]s or toggle walls that ''began'' the level on the lower layer under anything other than a [[monster]], although they will switch toggle walls that become displaced to the lower layer.
 
Toggle walls are not fatal to [[Chip]] or [[monster]]s if they turn closed when Chip or monster is on them, but they will protect Chip from [[monster]] impacts and sliding [[block]]s, and the [[wall]] rather than the monster will take effect if Chip tries to step onto the closed toggle/monster tile.
 
=== Trivia ===
 
* In the MS ruleset, the green button is the only one of the four buttons which does not make a "popping" noise when it is touched; it is instead silent. In Lynx, it makes the same sound as the other buttons.
 
=== See also ===
* [[Toggle wall]]
* [[Button Smash Glitch]]
 
{{clear}}
 
== Grey Button ==
 
{{Infobox Cowmantest
|name = Grey Button
|image = [[Image:GreyButton.png]]
|cc1 =
|cc2 = Yes
|cc1index  =
|multidirectional = No
|moves = No
}}
 
The '''grey button''' is a [[button]] introduced in [[Chip's Challenge 2]]. It changes the state of objects in a 5 by 5 square centered at the button, even if the tiles are already [[wire]]d. Tiles that can be changed include [[toggle wall]]s, [[flame jet]]s, [[force floor]]s, [[swivel door]]s, [[train track]]s. [[Trap]]s, [[green chip]]s, and [[green bomb]]s are not affected by grey buttons.
 
{{clear}}
 
== Orange Button ==
 
{{Infobox Cowmantest
|name = Orange Button
|image = [[Image:OrangeButton.png]]
|cc1 =
|cc2 = Yes
|cc1index  =
|multidirectional = No
|moves = No
}}
 
The '''orange button''' is a [[button]] introduced in [[Chip's Challenge 2]]. When held down, they invert the state of a corresponding [[flame jet]] from its start state. An orange button connects to a flame jet in a diamond grow pattern, prioritizing the rightmost flame jet and then travelling in a counterclockwise fashion.
 
{{clear}}
 
== Pink Button ==
 
{{Infobox Cowmantest
|name = Pink Button
|image = [[Image:PinkButton.png]]
|cc1 =
|cc2 = Yes
|cc1index  =
|multidirectional = No
|moves = No
}}
 
The '''pink button''' is a button introduced in Chip's Challenge 2. When stepped on by [[Chip]], [[Melinda]], [[block]]s, and [[monster]]s, it will activate any [[wire]] it is connected to.
 
{{clear}}
 
== Red Button ==
 
{{Infobox Cowmantest
|name = Red Button
|image = [[Image:Red Button.png]] [[Image:RedButtonCC2.png]]
|cc1 = Yes
|cc2 = Yes
|cc1index  = 36
|multidirectional = No
|moves = No
}}
 
The '''red button''', sometimes called a '''clone button''', is a [[tile]] in [[Chip's Challenge]] that activates a corresponding [[clone machine]] specified by the designer. While more than one red button may activate the same clone machine, a single red button cannot activate more than one clone machine. If the designer connects it to more than one clone machine, only the first connection is valid. To change the connection to a different clone machine in a [[level editor]], either erase the clone machine and red button and reconnect them (in [[ChipEdit]]), or go to the "Clone Connections" menu and disconnect the tiles (in [[CCEdit]] or [[CCLD]]). In addition, ChipEdit will automatically connect a clone button to a clone machine if one is created ''directly'' after the other.
 
Under the [[Ruleset|pedantic Lynx ruleset]] and in [[Chip's Challenge 2]], red buttons are automatically connected to the next clone machine in [[reading order]]. In Chip's Challenge 2, red buttons cannot be wired to clone machines, but [[pink button]]s can.
 
Various things happen when a red button is connected to a tile that is not on top of a clone machine. To clone, the tile must be a [[monster]] or [[clone block]], and the direction it is cloning has to be clear, or the clone will have no effect and the button must be pressed again.
 
If the red button is connected to a monster that is not in the monster list, the red button will add that monster to the [[monster list]] and also cause it to start moving in the specified direction, assuming that move is legal. If the move is illegal, or if the monster is already in the monster list, the red button will have no effect.
 
If it is connected to a clone block without a clone machine under it, it will clone only one copy of the block before the original clone block disappears and reveals anything that may be underneath the clone block, assuming once again that the direction of the clone block is legal. If it is illegal, nothing happens.
 
=== See also ===
* [[Clone machine]]
* [[Controller and Boss Glitch]]
 
{{clear}}
 
== Yellow Button ==
 
{{Infobox Cowmantest
|name = Yellow Button
|image = [[Image:YellowButton.png]]
|cc1 =
|cc2 = Yes
|cc1index  =
|multidirectional = No
|moves = No
}}
 
The '''yellow button''' is a [[button]] introduced in [[Chip's Challenge 2]]. When pressed, every [[yellow tank]] in the level will attempt to move in the same direction as the object that pressed it.

Latest revision as of 05:06, 15 August 2022

Error while fetching data from URL https://beta.bitbusters.club/wiki/level_listing.php?pack=cc1&level=33: $2.
Error fetching URL: SSL: no alternative certificate subject name matches target host name 'beta.bitbusters.club'
There was a problem during the HTTP request: 0 Error
Could not get URL https://beta.bitbusters.club/wiki/level_listing.php?pack=cc1&level=33 after 3 tries.


So this is the damn level 33 of set 0!

  • Title: Error: no local variable "NAME" has been set.
  • Designers: Error: no local variable "DESIGNER" has been set.
  • MS Bold: Error: no local variable "MS_BOLD" has been set.
  • Lynx Bold: Error: no local variable "LYNX_BOLD" has been set.
  • Steam Bold: Error: no local variable "STEAM_BOLD" has been set.
  • MS Luck: Error: no local variable "MS_LUCK" has been set.
  • MS Exec: Error: no local variable "MS_EXEC" has been set.
  • MS Routing: Error: no local variable "MS_ROUTE" has been set.
  • MS Casual: Error: no local variable "MS_CASUAL" has been set.
  • Lynx Luck: Error: no local variable "LYNX_LUCK" has been set.
  • Lynx Exec: Error: no local variable "LYNX_EXEC" has been set.
  • Lynx Routing: Error: no local variable "LYNX_ROUTE" has been set.
  • Lynx Casual: Error: no local variable "LYNX_CASUAL" has been set.
Retrieved from "https://wiki.bitbusters.club/index.php?title=User:DeltaCore/Button&oldid=34193"