Flick: Difference between revisions

Flick (edit)

Revision as of 18:03, 19 May 2024

1,031 bytes added , 19 May

rearrange to be less ms-focused, mention flicking off revealing walls, add a bit more explanation

Eevee

trusted-editors

67

edits

@@ Line 1: / Line 1: @@
 {{otheruses4|the action of moving a [[block]] off an [[acting wall]]|the action of flicking a block using the mouse|Mouse Panel Glitch}}
-A '''flick''' is a specialized technique in the [[MS ruleset]] of [[Chip's Challenge]], which allows [[Chip]] to push a [[block]] off an [[acting wall]] that he would otherwise be unable to enter. Prominent levels which require flicking to solve include [[Checkerboard II]] with closed [[toggle wall]]s, and [[Debug File]] and [[Captured]] with thin walls. Other tiles that blocks can be flicked off of include [[wall]]s, [[socket]]s, real [[blue wall]]s, and [[lock]]s when Chip does not hold its [[key]]. If a block is on a [[clone machine]], pushing the block will clone a new block in the direction of the push rather than moving the block off of the clone machine.
-== Conditions ==
+To '''flick''' a [[block]] is to push it off of a tile that [[Chip]] (or [[Melinda]]) cannot enter, i.e. an [[acting wall]].  Normally, blocks are pushed by being displaced: the player enters the block's cell and moves the block out of the way.  However, under some circumstances, a block can be pushed out of a cell that the player couldn't have entered in the first place.
-For a flick to work, the block must be directly next to Chip and on top of any acting wall. The block itself must be able to make the intended move legally; otherwise, nothing will happen. Some tiles, such as an [[ice]] corner or a [[thin wall]], will only block specific directions. For example, a block on a southeast thin wall can be flicked north when Chip is south of the block or flicked west when Chip is east of the block, but cannot be flicked south or east.
+Flicking is arguably a [[glitch|bug]] for this reason, but its utility in level design has made it a common feature in official [[level set]]s.
-== Demonstration ==
+A flick is only possible when the push ''would'' be legal, if the acting wall weren't present.
+== [[File:Chip S (Lynx).png]] Lynx ==
+In the [[Lynx ruleset]], flicking is only possible for blocks on real [[blue wall]]s and [[hidden wall]]s.  This setup is common in community pack levels after [[CCLP2]], which require that all levels be playable under Lynx rules.  An example is [[Bisection]] from [[CCLP4]].
+== [[File:Chip S.png]] MS ==
+In the [[MS ruleset]], a block may be flicked off of ''any'' acting wall, including normal [[wall]]s, [[socket]]s, real [[blue wall]]s, and [[lock]]s when Chip does not have a matching [[key]].  If a block is on a tile with solid edges, such as an [[ice]] corner or a [[thin wall]], Chip may flick against the walls from the outside to push the block, but the block cannot move ''through'' the walls.  For example, a block on a southeast thin wall can be flicked north when Chip is south of the block or flicked west when Chip is east of the block, but cannot be flicked south or east.
+If a real block is on a [[clone machine]], pushing the block will clone it in the direction of the push, rather than moving the block off of the clone machine.  (What actually happens here is that the block is flicked normally, but the clone machine duplicates anything that moves off of it.)  This isn't possible with the clone machines in the original [[Chip's Challenge]], as they all contain [[clone block]]s, which can't be pushed at all.
+Prominent levels which require flicking to solve include [[Checkerboard II]] (with closed [[toggle wall]]s) and [[Debug File]] and [[Captured]] (with thin walls).
+=== Demonstration ===
 [[File:Flick.png]]
-In this small level, to reach the [[exit]], Chip must move the block to pass the [[water]]. When he tries to move [[Directional notation|-L]], the block is pushed L off the east [[thin wall]], such that this happens:
+In this small level, to reach the [[exit]], Chip must move the block to pass the [[water]].  When he tries to move [[Directional notation|-L]], the block is pushed L off the east [[thin wall]], such that this happens:
 [[File:Flick part 2.png]]
-and the block continues to slide across the [[ice]] until Chip can use it. Note that if the thin wall was facing west, the flick would not work from this direction.
+and the block continues to slide across the [[ice]] until Chip can use it.  Note that if the thin wall was facing west, the flick would not work from this direction, as the block would simply stop against the wall.
-== In Lynx ==
-Flicking is not possible in the [[Lynx ruleset]] with an exception for blocks on real blue walls. This is commonly seen in community pack levels after CCLP2 which required that all levels be compatible with the Lynx ruleset. An example is [[Bisection]] from [[CCLP4]].
-== In Chip's Challenge 2==
+== Chip's Challenge 2 ==
-Flicking appears in a more minor form in CC2, where entities can push blocks off of [[recessed wall]]s, [[railroad]]s with appropriate junctions, [[turtle]]s, and [[swivel door]]s but do not move onto the tile the block was previously occupying afterward.
+Flicking appears in a more minor and deliberate form in CC2, where a block's movement out of a cell can ''cause'' the cell to become an acting wall and prevent its pusher from following it.  This happens with [[recessed wall]]s, [[railroad]]s with appropriate junctions, [[swivel door]]s, and [[turtle]]s (because the resulting splash blocks players).
 == See also ==
 * [[Ram]]
-* [[Block slapping]], for a [[Lynx ruleset|Lynx]]-exclusive relative
+* [[Block slapping]], a [[Lynx ruleset|Lynx]]-exclusive move that also allows pushing a block without entering its cell
+* [[Spring mining]], a CC2 bug with the opposite effect, where pushing a block causes the player to move onto wall
 [[Category:Terminology]]
 [[Category:Mechanics]]