Ikari Warriors/Game Mechanics - Revision history

Ktwo: /* Glitches */

2025-03-09T09:42:26Z

Glitches

← Older revision		Revision as of 09:42, 9 March 2025
Line 63:		Line 63:
	- The first is to fly to the end of an area and exit. You will then start the next area in the normal state. Since areas 3 and 4 have bosses at the end, this method only works in area 1 (no helicopter in area 2).<br />		- The first is to fly to the end of an area and exit. You will then start the next area in the normal state. Since areas 3 and 4 have bosses at the end, this method only works in area 1 (no helicopter in area 2).<br />
	- The other method is to buffer a death when initiating the flying state. Upon breaking the flying state, the player dies and then restarts in the normal state as after a normal death. To buffer a death, the helicopter needs to be destroyed before it's scrolled off-screen. This can either be done by firing a missile just before entering the flying state (so press A slightly before pressing B) or have an enemy destroy the helicopter. The latter can e.g. be done by triggering a kamikaze soldier to explode near the helicopter. This method allows the flying glitch to be used in areas 3 and 4, since the bosses at the end of these areas require you to be in the normal state to defeat them.<br /><br />		- The other method is to buffer a death when initiating the flying state. Upon breaking the flying state, the player dies and then restarts in the normal state as after a normal death. To buffer a death, the helicopter needs to be destroyed before it's scrolled off-screen. This can either be done by firing a missile just before entering the flying state (so press A slightly before pressing B) or have an enemy destroy the helicopter. The latter can e.g. be done by triggering a kamikaze soldier to explode near the helicopter. This method allows the flying glitch to be used in areas 3 and 4, since the bosses at the end of these areas require you to be in the normal state to defeat them.<br /><br />

			===Transform a tank into a helicopter (requires 2p)===
			If continuously exiting and re-entering a tank as p2 (does not seem to work for p1?), it's possible to transform the tank into a helicopter. The details behind this glitch are not well known at the time of writing.

			The first known mention of this glitch appears to be on https://davidwonn.kontek.net/nes.html#I and an accompanying demonstration by the same person, https://www.youtube.com/watch?v=UahtkOcf-co. Following the discovery of this resource, some TAS discussion followed, https://tasvideos.org/Forum/Posts/534676.<br /><br />

	===Visual glitches===		===Visual glitches===

Ktwo: /* Continue code */

2024-06-02T07:46:32Z

Continue code

← Older revision		Revision as of 07:46, 2 June 2024
Line 75:		Line 75:

	===Continue code===		===Continue code===
	One of the most well known continue codes throughout the NES library, A B B A. Just press the button combination after having lost the last life and before the game over screen. In a casual playthrough, it can be expected to input this code 100+ times. In that context, it can be worth highlighting that the game only polls player inputs at the same framerate as the game, i.e. 15fps. When inputting the code that many times in a playthrough, it's not too unlikely that one manages by accident to tap one of inputs on three frames the game does not poll player inputs, leading to the code not working. Another risk is that two buttons are pressed in too rapid succession. There needs to be an empty input polled by the game between each button press. As long as the game over screen hasn't appeared, one can however attempt again to input the code. To prevent the code from not working, avoid tapping too fast and try instead to hold down each button (but not overlap any button presses).<br /><br />		One of the most well known continue codes throughout the NES library, A B B A. Just press the button combination after having lost the last life and before the game over screen. In a casual playthrough, it can be expected to input this code 100+ times. In that context, it can be worth highlighting that the game only polls player inputs at the same framerate as the game, i.e. 15fps. When inputting the code that many times in a playthrough, it's not too unlikely that one manages by accident to tap one of the inputs on three frames the game does not poll player inputs, leading to the code not working. Another risk is that two buttons are pressed in too rapid succession. There needs to be an empty input polled by the game between each button press. As long as the game over screen hasn't appeared, one can however attempt again to input the code. To prevent the code from not working, avoid tapping too fast and try instead to hold down each button (but not overlap any button presses).<br /><br />

	The game checks for player inputs from instruction $FF89 and onward. Each correct button press increases the counter in $58. When it equals 4, the code branches to starting a continue (3 lives back etc).~~<br />~~<br />		The game checks for player inputs from instruction $FF89 and onward. Each correct button press increases the counter in $58. When it equals 4, the code branches to starting a continue (3 lives back etc).<br />

	When reaching the end of a level (check of $73 at instruction $D1F0) or killing the boss in level 3 or 4, $FB is set to a non-zero value. This skips the ABBA-checking section in the code and continues are no longer possible until starting the next level. There are reports of the ABBA code stopped working in the middle of a level. From the code sections referenced above, it's not clear how that could happen. It's possible that $FB could be written to from other sub-routines, but it's also possible that these reports are from incorrectly inputting the code. If someone manages to record an emulator movie of when the ABBA-code stops working mid-level, please post about it in the forum.<br />		''Note: Pressing 'B' at the wrong time will reset $58 to 0, while pressing 'A' at the wrong time will reset $58 to 1.''<br /><br />

			When reaching the end of a level (check of $73 at instruction $D1F0) or killing the boss in level 3 or 4, $FB is set to a non-zero value. This skips the ABBA-checking section in the code and continues are no longer possible until starting the next level.<br /><br />

			There are reports of the ABBA code stopped working in the middle of a level. From the code sections referenced above, it's not clear how that could happen. It's possible that $FB could be written to from other sub-routines, but it's also possible (more likely?) that these reports are from incorrectly inputting the code. If someone manages to record an emulator movie of when the ABBA-code stops working mid-level, please post about it in the forum.<br />
	(Credits to 'Fo__' for contributions to the code analysis of this section)<br /><br />		(Credits to 'Fo__' for contributions to the code analysis of this section)<br /><br />

Ktwo: /* Continue code */

2023-06-25T07:45:47Z

Continue code

← Older revision		Revision as of 07:45, 25 June 2023
Line 75:		Line 75:

	===Continue code===		===Continue code===
	One of the most well known continue codes throughout the NES library, A B B A. Just press the button combination after having lost the last life and before the game over screen. In a casual playthrough, it can be expected to input this code 100+ times. In that context, it can be worth highlighting that the game only polls player inputs at the same framerate as the game, i.e. 15fps. When inputting the code that many times in a playthrough, it's not too unlikely that one manages by accident to tap one of inputs on three frames the game does not poll player inputs, leading to the code not working. As long as the game over screen hasn't appeared, one can however attempt again to input the code.<br /><br />		One of the most well known continue codes throughout the NES library, A B B A. Just press the button combination after having lost the last life and before the game over screen. In a casual playthrough, it can be expected to input this code 100+ times. In that context, it can be worth highlighting that the game only polls player inputs at the same framerate as the game, i.e. 15fps. When inputting the code that many times in a playthrough, it's not too unlikely that one manages by accident to tap one of inputs on three frames the game does not poll player inputs, leading to the code not working. Another risk is that two buttons are pressed in too rapid succession. There needs to be an empty input polled by the game between each button press. As long as the game over screen hasn't appeared, one can however attempt again to input the code. To prevent the code from not working, avoid tapping too fast and try instead to hold down each button (but not overlap any button presses).<br /><br />

	The game checks for player inputs from instruction $FF89 and onward. Each correct button press increases the counter in $58. When it equals 4, the code branches to starting a continue (3 lives back etc).<br /><br />		The game checks for player inputs from instruction $FF89 and onward. Each correct button press increases the counter in $58. When it equals 4, the code branches to starting a continue (3 lives back etc).<br /><br />

Ktwo: /* Continue code */

2023-06-25T07:40:01Z

Continue code

← Older revision		Revision as of 07:40, 25 June 2023
Line 75:		Line 75:

	===Continue code===		===Continue code===
	One of the most well known continue codes throughout the NES library, A B B A. Just press the button combination after having lost the last life and before the game over screen.<br /><br />		One of the most well known continue codes throughout the NES library, A B B A. Just press the button combination after having lost the last life and before the game over screen. In a casual playthrough, it can be expected to input this code 100+ times. In that context, it can be worth highlighting that the game only polls player inputs at the same framerate as the game, i.e. 15fps. When inputting the code that many times in a playthrough, it's not too unlikely that one manages by accident to tap one of inputs on three frames the game does not poll player inputs, leading to the code not working. As long as the game over screen hasn't appeared, one can however attempt again to input the code.<br /><br />

	The game checks for player inputs from instruction $FF89 and onward. Each correct button press increases the counter in $58. When it ~~reaches~~ 4, the code branches to starting a continue (3 lives back etc).<br /><br />		The game checks for player inputs from instruction $FF89 and onward. Each correct button press increases the counter in $58. When it equals 4, the code branches to starting a continue (3 lives back etc).<br /><br />

	When reaching the end of a level (check of $73 at instruction $D1F0) or killing the boss in level 3 or 4, $FB is set to a non-zero value. This skips the ABBA-checking section in the code and continues are no longer possible until starting the next level. There are reports of the ABBA code stopped working in the middle of a level. From the code sections referenced above, it's not clear how that could happen. It's possible that $FB could be written to from other sub-routines, but it's also possible that these reports are from incorrectly inputting the code. If someone manages to record an emulator ~~video~~ of when the ABBA-code stops working mid-level, please post about it in the forum.<br />		When reaching the end of a level (check of $73 at instruction $D1F0) or killing the boss in level 3 or 4, $FB is set to a non-zero value. This skips the ABBA-checking section in the code and continues are no longer possible until starting the next level. There are reports of the ABBA code stopped working in the middle of a level. From the code sections referenced above, it's not clear how that could happen. It's possible that $FB could be written to from other sub-routines, but it's also possible that these reports are from incorrectly inputting the code. If someone manages to record an emulator movie of when the ABBA-code stops working mid-level, please post about it in the forum.<br />
	(Credits to 'Fo__' for contributions to the code analysis of this section)<br /><br />		(Credits to 'Fo__' for contributions to the code analysis of this section)<br /><br />

Ktwo: /* Continue code */

2023-06-21T18:37:42Z

Continue code

← Older revision		Revision as of 18:37, 21 June 2023
Line 79:		Line 79:
	The game checks for player inputs from instruction $FF89 and onward. Each correct button press increases the counter in $58. When it reaches 4, the code branches to starting a continue (3 lives back etc).<br /><br />		The game checks for player inputs from instruction $FF89 and onward. Each correct button press increases the counter in $58. When it reaches 4, the code branches to starting a continue (3 lives back etc).<br /><br />

	When reaching the end of a level (check of $73 at instruction $D1F0) or killing the boss in level 3 or 4, $FB is set to a non-zero value. This skips the ABBA-checking section in the code and continues are no longer possible until starting the next level. There are reports of the ABBA code ~~stops~~ working in the middle of a level. From the code sections referenced above, it's not clear how that could happen. It's possible that $FB could be written to from other sub-routines, but it's also possible that these reports are from incorrectly inputting the code. If someone manages to record an emulator video of when the ABBA-code stops working mid-level, please post about it in the forum.<br /><br />		When reaching the end of a level (check of $73 at instruction $D1F0) or killing the boss in level 3 or 4, $FB is set to a non-zero value. This skips the ABBA-checking section in the code and continues are no longer possible until starting the next level. There are reports of the ABBA code stopped working in the middle of a level. From the code sections referenced above, it's not clear how that could happen. It's possible that $FB could be written to from other sub-routines, but it's also possible that these reports are from incorrectly inputting the code. If someone manages to record an emulator video of when the ABBA-code stops working mid-level, please post about it in the forum.<br />
			(Credits to 'Fo__' for contributions to the code analysis of this section)<br /><br />

	==Some comments about various aspects of the game mechanics==		==Some comments about various aspects of the game mechanics==

Ktwo: /* Memory addresses */

2023-06-19T16:17:35Z

Memory addresses

← Older revision		Revision as of 16:17, 19 June 2023
Line 113:		Line 113:

	==Memory addresses==		==Memory addresses==
	~~$55 Global counter that determines several random events/paramters~~ in the ~~game~~. ~~The counter starts from 0 at the start screen (when you~~ have ~~the choice between 1 and 2 players). It then runs continuously, except for fixed breaks when the screen turns black (when the game starts and~~ during the transition between areas). The value can at any given time, t1, be calculated with the following formula: [$55]=(t1-t0-55-142-x*840)/4, where t0 is 4 frames before $55 changed to 1 on the start screen and x is the number of area transitions.~~<br /><br />~~		Some addresses are mentioned in the respective relevant sections on this page. Below is a selection of addresses that have been identified during code analysis.

	$51C ~~object~~ screen position y (mid)~~<br />~~<br />		* $55 - Global counter that determines several random events/parameters in the game. The counter starts from 0 at the start screen (when you have the choice between 1 and 2 players). It then runs continuously, except for fixed breaks when the screen turns black (when the game starts and during the transition between areas). The value can at any given time, t1, be calculated with the following formula: [$55]=(t1-t0-55-142-x*840)/4, where t0 is 4 frames before $55 changed to 1 on the start screen and x is the number of area transitions.
			* $65 - Flag for two players
			* $73/$72 - Big/Small level progress
			* $74 - Relative position compared to the center of the screen (y-direction) (probably telling the game if the screen should be scrolled and/or if the level progress should increase)
			* $51C - Object screen position y (mid)
			* $6FC - Level flag (0 - level 1; 1 -level 2 etc)
			<br />

	The below analysis of the memory addresses was made by TaoTao in http://tasvideos.org/forum/posting.php?mode=quote&p=450038.<br />		The below analysis of the memory addresses was made by TaoTao in http://tasvideos.org/forum/posting.php?mode=quote&p=450038.<br />
	<u>RAM</u><br />		<u>RAM</u><br />
	$3D U8 $2000 mirror~~<br />~~		* $3D U8 $2000 mirror
	$3E U8 $2001 mirror~~<br />~~		* $3E U8 $2001 mirror
	$3F U8 $2005 x mirror~~<br />~~		* $3F U8 $2005 x mirror
	$40 U8 $2005 y mirror~~<br />~~		* $40 U8 $2005 y mirror
	$41 U8 tmp variable for input reading~~<br />~~		* $41 U8 tmp variable for input reading
	$42 U8 tmp variable for input reading~~<br />~~		* $42 U8 tmp variable for input reading
	$43 U8 P1 input # ABSTUDLR~~<br />~~		* $43/$45 U8 P1/P2 input, ABSTUDLR
	$44 U8 P1 input modified # suppress continuous A~~<br />~~		* $44/$46 U8 P1/P2 input modified, suppress continuous A
	~~$45 U8 P2 input<br />~~		* $6A U8 current sprite buffer page, 2..3
	~~$46 U8 P2 input modified<br />~~		* $E4/$E5 U8 P1/P2 life
	$6A U8 current sprite buffer page # 2..3~~<br />~~
	$E4 ~~U8 P1 life<br~~ />
	$E5 U8 P2 life~~<br /><br />~~

	$0200-$02FF Sprite[64] sprite buffer 1<br />		$0200-$02FF Sprite[64] sprite buffer 1<br />
Line 149:		Line 152:
	$063C- U8[] object direction # 0..15<br />		$063C- U8[] object direction # 0..15<br />
	$0674- U8[] object drop-related value<br />		$0674- U8[] object drop-related value<br />
	$067F ~~U8 P1 ammo of gun<br~~ />		$067F/$0680 U8 P1/P2 ammo of gun<br />
	$0680 U8 P2 ammo of gun<br />		$0681/$0682 U8 P1/P2 ammo of grenade<br />
	$0681 ~~U8 P1 ammo of grenade<br~~ />
	$0682 U8 P2 ammo of grenade~~<br />~~<br />

	<u>ROM</u><br />		<u>ROM</u><br />

Ktwo: /* Continue code */

2023-06-19T16:01:49Z

Continue code

← Older revision		Revision as of 16:01, 19 June 2023
Line 75:		Line 75:

	===Continue code===		===Continue code===
	One of the most well known continue codes throughout the NES library, A B B A. Just press the button combination after having lost the last life and before the game ~~reverts back to the title~~ screen.<br />		One of the most well known continue codes throughout the NES library, A B B A. Just press the button combination after having lost the last life and before the game over screen.<br /><br />
	~~For unknown reasons~~, the code ~~doesn't work when you've scrolled until the very end of~~ a ~~level~~.<br />
	~~Sometimes~~, the ~~game~~ continues ~~to scroll~~ the ~~screen after~~ a ~~game over (unknown reasons)~~, ~~which~~ also ~~prevents you~~ from ~~continuing~~. ~~This is quite uncommon though~~.<br /><br />		The game checks for player inputs from instruction $FF89 and onward. Each correct button press increases the counter in $58. When it reaches 4, the code branches to starting a continue (3 lives back etc).<br /><br />

			When reaching the end of a level (check of $73 at instruction $D1F0) or killing the boss in level 3 or 4, $FB is set to a non-zero value. This skips the ABBA-checking section in the code and continues are no longer possible until starting the next level. There are reports of the ABBA code stops working in the middle of a level. From the code sections referenced above, it's not clear how that could happen. It's possible that $FB could be written to from other sub-routines, but it's also possible that these reports are from incorrectly inputting the code. If someone manages to record an emulator video of when the ABBA-code stops working mid-level, please post about it in the forum.<br /><br />

	==Some comments about various aspects of the game mechanics==		==Some comments about various aspects of the game mechanics==

Ktwo: /* Flying glitch */

2022-04-04T14:44:29Z

Flying glitch

← Older revision		Revision as of 14:44, 4 April 2022
Line 62:		Line 62:
	There are two ways to return to the normal state after activating the flying glitch.<br />		There are two ways to return to the normal state after activating the flying glitch.<br />
	- The first is to fly to the end of an area and exit. You will then start the next area in the normal state. Since areas 3 and 4 have bosses at the end, this method only works in area 1 (no helicopter in area 2).<br />		- The first is to fly to the end of an area and exit. You will then start the next area in the normal state. Since areas 3 and 4 have bosses at the end, this method only works in area 1 (no helicopter in area 2).<br />
	- The other method is to buffer a death when initiating the flying state. Upon breaking the flying state, the player dies and then restarts in the normal state as after a normal death. To buffer a death, the helicopter needs to be destroyed before it's scrolled off-screen. This can either be done by firing a missile just before entering the flying state (so press A slightly before pressing B) or have an enemy destroy the helicopter. The latter can e.g. be done by triggering a kamikaze soldier to explode near the helicopter~~. Note that you need to exit the helicopter and enter the flying state before it's destroyed (so e.g. a mine can't be used for this purpose)~~. This method allows the flying glitch to be used in areas 3 and 4, since the bosses at the end of these areas require you to be in the normal state to defeat them.<br /><br />		- The other method is to buffer a death when initiating the flying state. Upon breaking the flying state, the player dies and then restarts in the normal state as after a normal death. To buffer a death, the helicopter needs to be destroyed before it's scrolled off-screen. This can either be done by firing a missile just before entering the flying state (so press A slightly before pressing B) or have an enemy destroy the helicopter. The latter can e.g. be done by triggering a kamikaze soldier to explode near the helicopter. This method allows the flying glitch to be used in areas 3 and 4, since the bosses at the end of these areas require you to be in the normal state to defeat them.<br /><br />

	===Visual glitches===		===Visual glitches===

Ktwo: /* Flying glitch */

2022-02-10T10:21:37Z

Flying glitch

← Older revision		Revision as of 10:21, 10 February 2022
Line 58:		Line 58:
	https://www.youtube.com/watch?v=kQF-OpUh99o<br />		https://www.youtube.com/watch?v=kQF-OpUh99o<br />
	If you hold A, B and up at the same time while in the helicopter (they don't need to start to be pressed down simultaneously, you just need to hold them down at the same time), the character will exit the helicopter and continue traveling vertically at helicopter speed as long as A and/or B is kept held down (the glitch doesn't work with the tank). In this state, you're invincible and can't interact with items on the screen.<br />		If you hold A, B and up at the same time while in the helicopter (they don't need to start to be pressed down simultaneously, you just need to hold them down at the same time), the character will exit the helicopter and continue traveling vertically at helicopter speed as long as A and/or B is kept held down (the glitch doesn't work with the tank). In this state, you're invincible and can't interact with items on the screen.<br />
	If you let go of A and B, you will be teleported to the (small) y-position you left the helicopter on. Your ~~movement speed~~ will be ~~back~~ to ~~walking speed~~. ~~You~~'ll still be in the invincible state and ~~you're still~~ unable to interact with the environment.<br /><br />		If you let go of A and B, you will be teleported to the "small y"-position you left the helicopter on. Your hitbox will however still be linked to the helicopter position. If the helicopter is off-screen, this means you're still in the invincible state and unable to interact with the environment (including shots and grenades).<br /><br />

	There are two ways to ~~"break"~~ the ~~invincibility of~~ the flying ~~state~~.<br />		There are two ways to return to the normal state after activating the flying glitch.<br />
	- The first is to fly to the end of an area and exit it. You will then start the next area in the normal state. Since ~~there is no helicopter to be found in area 2 and~~ areas 3 and 4 have bosses at the end, this method only works in area 1.<br />		- The first is to fly to the end of an area and exit. You will then start the next area in the normal state. Since areas 3 and 4 have bosses at the end, this method only works in area 1 (no helicopter in area 2).<br />
	- The other method is to buffer a death when initiating the flying state. Upon breaking the flying state, the player dies and then restarts in the normal state as after a normal death. To buffer a death, the helicopter needs to be destroyed before it's scrolled off-screen. This can either be done by firing a missile just before entering the flying state (so press A slightly before pressing B) or have an enemy destroy the helicopter. The latter can ~~be done by~~ e.g. triggering a kamikaze soldier to explode near the helicopter ~~or let an enemy missile hit it~~. Note that you need to exit the helicopter and enter the flying state before it's destroyed (so e.g. mine can't be used for this purpose). This method allows the flying glitch to be used in areas 3 and 4, since the bosses at the end of these areas require you to be in the normal state to defeat them.<br /><br />		- The other method is to buffer a death when initiating the flying state. Upon breaking the flying state, the player dies and then restarts in the normal state as after a normal death. To buffer a death, the helicopter needs to be destroyed before it's scrolled off-screen. This can either be done by firing a missile just before entering the flying state (so press A slightly before pressing B) or have an enemy destroy the helicopter. The latter can e.g. be done by triggering a kamikaze soldier to explode near the helicopter. Note that you need to exit the helicopter and enter the flying state before it's destroyed (so e.g. a mine can't be used for this purpose). This method allows the flying glitch to be used in areas 3 and 4, since the bosses at the end of these areas require you to be in the normal state to defeat them.<br /><br />

	===Visual glitches===		===Visual glitches===

Ktwo: /* Flying glitch */

2022-02-08T09:01:37Z

Flying glitch

← Older revision		Revision as of 09:01, 8 February 2022
Line 58:		Line 58:
	https://www.youtube.com/watch?v=kQF-OpUh99o<br />		https://www.youtube.com/watch?v=kQF-OpUh99o<br />
	If you hold A, B and up at the same time while in the helicopter (they don't need to start to be pressed down simultaneously, you just need to hold them down at the same time), the character will exit the helicopter and continue traveling vertically at helicopter speed as long as A and/or B is kept held down (the glitch doesn't work with the tank). In this state, you're invincible and can't interact with items on the screen.<br />		If you hold A, B and up at the same time while in the helicopter (they don't need to start to be pressed down simultaneously, you just need to hold them down at the same time), the character will exit the helicopter and continue traveling vertically at helicopter speed as long as A and/or B is kept held down (the glitch doesn't work with the tank). In this state, you're invincible and can't interact with items on the screen.<br />
	If you let go of A and B, you will be teleported to the (small) y-position you left the helicopter on. Your movement speed will be back to walking speed. You'll still be in the invincible state and you're still unable to interact with the environment. The ~~only way~~ to ~~revert back~~ to normal is to ~~exit~~ the area ~~or if~~ the ~~helicopter was destroyed after~~ the flying state ~~was initiated~~, ~~but still on~~ screen (either by an enemy or ~~by self-destruction~~).<br /><br />		If you let go of A and B, you will be teleported to the (small) y-position you left the helicopter on. Your movement speed will be back to walking speed. You'll still be in the invincible state and you're still unable to interact with the environment.<br /><br />

			There are two ways to "break" the invincibility of the flying state.<br />
			- The first is to fly to the end of an area and exit it. You will then start the next area in the normal state. Since there is no helicopter to be found in area 2 and areas 3 and 4 have bosses at the end, this method only works in area 1.<br />
			- The other method is to buffer a death when initiating the flying state. Upon breaking the flying state, the player dies and then restarts in the normal state as after a normal death. To buffer a death, the helicopter needs to be destroyed before it's scrolled off-screen. This can either be done by firing a missile just before entering the flying state (so press A slightly before pressing B) or have an enemy destroy the helicopter. The latter can be done by e.g. triggering a kamikaze soldier to explode near the helicopter or let an enemy missile hit it. Note that you need to exit the helicopter and enter the flying state before it's destroyed (so e.g. mine can't be used for this purpose). This method allows the flying glitch to be used in areas 3 and 4, since the bosses at the end of these areas require you to be in the normal state to defeat them.<br /><br />

	===Visual glitches===		===Visual glitches===