Hacking NDS - Revision history

Demonic722: /* Code Types */

2014-08-03T20:59:42Z

Code Types

MathUser at 16:42, 4 December 2008

2008-12-04T16:42:20Z

← Older revision		Revision as of 16:42, 4 December 2008
Line 1,373:		Line 1,373:

	It should be easy to convert most codes if proper documentation is kept handy. Code porting is a skill to be learned, and should not be treated as a set of steps to mechanically go through.		It should be easy to convert most codes if proper documentation is kept handy. Code porting is a skill to be learned, and should not be treated as a set of steps to mechanically go through.


			{{EnHacklopedia}}

	{{Template: EnHacklopedia_Legal}}		{{Template: EnHacklopedia_Legal}}
	[[Category: EnHacklopedia]]		[[Category: EnHacklopedia]]

Ace: /* Hacking */

2008-12-04T15:55:03Z

Hacking

← Older revision		Revision as of 15:55, 4 December 2008
Line 463:		Line 463:
	====Hacking====		====Hacking====

	Click "New Search". Then choose the data type. By default, the <~~abbr~~ title="Trainer Toolkit">TT</~~abbr~~> will list 2 items under "Memory Ranges". The one called "Working RAM" may be removed. As the manual for the toolkit states, nothing of interest has ever been found here. If the hacker knows of a specific memory range they want to search in, then he may also remove the Main RAM, then click on "Add". The hacker will need to supply the range a name, a starting address, and an ending address. Remember to prefix with a "0x0". The ability to save and load ranges is included. Narrowing the range is useful, sometimes necessary, if the hacker needs to perform searches while connected to the Nintendo WiFi Connection as the time it takes to complete a full search of the Main RAM will take too long and the hacker will ping out.		Click "New Search". Then choose the data type. By default, the <acronym title="Trainer Toolkit">TT</acronym> will list 2 items under "Memory Ranges". The one called "Working RAM" may be removed. As the manual for the toolkit states, nothing of interest has ever been found here. If the hacker knows of a specific memory range they want to search in, then he may also remove the Main RAM, then click on "Add". The hacker will need to supply the range a name, a starting address, and an ending address. Remember to prefix with a "0x0". The ability to save and load ranges is included. Narrowing the range is useful, sometimes necessary, if the hacker needs to perform searches while connected to the Nintendo WiFi Connection as the time it takes to complete a full search of the Main RAM will take too long and the hacker will ping out.

	To perform another search, choose the appropriate condition and click "Search Again". To search for a specific value in the RAM, select "Equal to" and uncheck "Previous Value". The value box will now be typed in. clicking the triangle next to the text box will allow the hacker to see previous values that have been entered. Remember to prefix the value with a 0x.		To perform another search, choose the appropriate condition and click "Search Again". To search for a specific value in the RAM, select "Equal to" and uncheck "Previous Value". The value box will now be typed in. clicking the triangle next to the text box will allow the hacker to see previous values that have been entered. Remember to prefix the value with a 0x.

Ace: /* Hacking */

2008-12-04T08:50:50Z

Hacking

← Older revision		Revision as of 08:50, 4 December 2008
Line 463:		Line 463:
	====Hacking====		====Hacking====

	Click "New Search". Then choose the data type. By default, the <~~acronym~~ title="Trainer Toolkit">TT</~~acronym~~> will list 2 items under "Memory Ranges". The one called "Working RAM" may be removed. As the manual for the toolkit states, nothing of interest has ever been found here. If the hacker knows of a specific memory range they want to search in, then he may also remove the Main RAM, then click on "Add". The hacker will need to supply the range a name, a starting address, and an ending address. Remember to prefix with a "0x0". The ability to save and load ranges is included. Narrowing the range is useful, sometimes necessary, if the hacker needs to perform searches while connected to the Nintendo WiFi Connection as the time it takes to complete a full search of the Main RAM will take too long and the hacker will ping out.		Click "New Search". Then choose the data type. By default, the <abbr title="Trainer Toolkit">TT</abbr> will list 2 items under "Memory Ranges". The one called "Working RAM" may be removed. As the manual for the toolkit states, nothing of interest has ever been found here. If the hacker knows of a specific memory range they want to search in, then he may also remove the Main RAM, then click on "Add". The hacker will need to supply the range a name, a starting address, and an ending address. Remember to prefix with a "0x0". The ability to save and load ranges is included. Narrowing the range is useful, sometimes necessary, if the hacker needs to perform searches while connected to the Nintendo WiFi Connection as the time it takes to complete a full search of the Main RAM will take too long and the hacker will ping out.

	To perform another search, choose the appropriate condition and click "Search Again". To search for a specific value in the RAM, select "Equal to" and uncheck "Previous Value". The value box will now be typed in. clicking the triangle next to the text box will allow the hacker to see previous values that have been entered. Remember to prefix the value with a 0x.		To perform another search, choose the appropriate condition and click "Search Again". To search for a specific value in the RAM, select "Equal to" and uncheck "Previous Value". The value box will now be typed in. clicking the triangle next to the text box will allow the hacker to see previous values that have been entered. Remember to prefix the value with a 0x.

Ace: /* Metroid Prime Hunters Auto Kill */

2008-12-03T23:48:28Z

Metroid Prime Hunters Auto Kill

← Older revision		Revision as of 23:48, 3 December 2008
Line 935:		Line 935:
	\|-		\|-
	\| class="EnHack-opcode" \| loop:		\| class="EnHack-opcode" \| loop:
			\| class="EnHack-arguments" \|
	\| class="EnHack-comments" \| <nowiki>;loop will check all players buttons</nowiki>		\| class="EnHack-comments" \| <nowiki>;loop will check all players buttons</nowiki>
	\|-		\|-
Line 1,031:		Line 1,032:
	\|-		\|-
	\| class="EnHack-opcode" \| loop:		\| class="EnHack-opcode" \| loop:
			\| class="EnHack-arguments" \|
	\| class="EnHack-comments" \| <nowiki>;loop will check all players buttons</nowiki>		\| class="EnHack-comments" \| <nowiki>;loop will check all players buttons</nowiki>
	\|-		\|-

Ace at 14:04, 3 December 2008

2008-12-03T14:04:05Z

Ace at 13:59, 3 December 2008

2008-12-03T13:59:54Z

Ace: /* Code Types */

2008-12-03T13:57:58Z

Code Types

← Older revision		Revision as of 13:57, 3 December 2008
Line 372:		Line 372:
	\|-		\|-
	\| class="EnHack-type" \| Type 0x0C<br /> C0000000 YYYYYYYY		\| class="EnHack-type" \| Type 0x0C<br /> C0000000 YYYYYYYY
	\| class="EnHack-desc" \| This sets the 'Dx repeat value' to YYYYYYYY and saves the 'Dx ~~nextcode~~ to be executed' and the 'Dx execution status'. Repeat will be executed when a D1/D2 code is encountered.<br /> When repeat is executed, the AR reloads the 'next code to be executed' and the 'execution status' from the Dx registers.		\| class="EnHack-desc" \| This sets the 'Dx repeat value' to YYYYYYYY and saves the 'Dx next code to be executed' and the 'Dx execution status'. Repeat will be executed when a D1/D2 code is encountered.<br /> When repeat is executed, the AR reloads the 'next code to be executed' and the 'execution status' from the Dx registers.
	\|-		\|-
	! class="EnHack-desc" colspan="2" \| Special Codes		! class="EnHack-desc" colspan="2" \| Special Codes
Line 419:		Line 419:
	\| class="EnHack-desc" \| Use the code type D3, DC or B before to set the offset. D2 should be needed to clear the offset after the code.<br /> D3000000 XXXXXXXX<br /> FYYYYYYY ZZZZZZZZ<br /> This should copy ZZZZZZZZ bytes from offset (=XXXXXXXX in this case) to YYYYYYYY. (YYYYYYYY if fixed, no offsets are added to it).		\| class="EnHack-desc" \| Use the code type D3, DC or B before to set the offset. D2 should be needed to clear the offset after the code.<br /> D3000000 XXXXXXXX<br /> FYYYYYYY ZZZZZZZZ<br /> This should copy ZZZZZZZZ bytes from offset (=XXXXXXXX in this case) to YYYYYYYY. (YYYYYYYY if fixed, no offsets are added to it).
	\|}		\|}



	==Dipstar==		==Dipstar==

Ace: /* Converting Codes */

2008-12-03T13:54:12Z

Converting Codes

← Older revision		Revision as of 13:54, 3 December 2008
Line 1,272:		Line 1,272:
	* Convert by hand.		* Convert by hand.

	Before attempting this one should read up on [[#Code Types\|Action Replay]] and [[#Code Types_2\|Codebreaker]] ~~codetypes~~. For example, ''Special Stage Ring Modifier'' hacked by DSman for Sonic Rush:		Before attempting this one should read up on [[#Code Types\|Action Replay]] and [[#Code Types_2\|Codebreaker]] code types. For example, ''Special Stage Ring Modifier'' hacked by DSman for Sonic Rush:

	{\| class="EnHack-code"		{\| class="EnHack-code"
Line 1,288:		Line 1,288:
	\|}		\|}

	Most codes can be ported this way. More complicated codes can be converted, but the hacker really needs to get familiar with the codes and ~~codetypes~~ of both systems to do this.		Most codes can be ported this way. More complicated codes can be converted, but the hacker really needs to get familiar with the codes and code types of both systems to do this.

	Here's a more complicated code: ''Moon Jump'' hacked by DSman for Yoshi's Island DS:		Here's a more complicated code: ''Moon Jump'' hacked by DSman for Yoshi's Island DS:
Line 1,326:		Line 1,326:
	\|}		\|}

	Action Replay DS pointers are ~~layed~~ out so that the pointer address is temporarily loaded into the data register, and then a code is written using this offset as a baseline. The Codebreaker actually has a nice pointer codetype, on the other hand.		Action Replay DS pointers are laid out so that the pointer address is temporarily loaded into the data register, and then a code is written using this offset as a baseline. The Codebreaker actually has a nice pointer codetype, on the other hand.

	{\| class="EnHack-code"		{\| class="EnHack-code"
Line 1,350:		Line 1,350:
	\|-		\|-
	\| class="EnHack-addy" \| C		\| class="EnHack-addy" \| C
	\| class="EnHack-comments" \| The ~~condtional~~ used to replace the second line of the AR code. It should be equal to 1. (enabled)		\| class="EnHack-comments" \| The Conditional used to replace the second line of the AR code. It should be equal to 1. (enabled)
	\|-		\|-
	\| class="EnHack-addy" \| T		\| class="EnHack-addy" \| T
	\| class="EnHack-comments" \| ~~Condtional~~ Type. Since line 2 of the AR is != to a 32-bit value of 0, T should equal 1 in this case.		\| class="EnHack-comments" \| Conditional Type. Since line 2 of the AR is != to a 32-bit value of 0, T should equal 1 in this case.
	\|-		\|-
	\| class="EnHack-addy" \| U		\| class="EnHack-addy" \| U

Ace: /* Metroid Prime Hunters Auto Kill */

2008-12-03T13:48:44Z

Metroid Prime Hunters Auto Kill

← Older revision		Revision as of 13:48, 3 December 2008
Line 1,263:		Line 1,263:


	After checking the switch, if to does not equal '0' the entire section of code performing the auto kill should be skipped completely, so it branches to the label quit. After this first important check, the code then loads all of the necessary varaibles into the registers to begin looping through each player. In the loop, it uses r6 as a timer and r8 as the player number. By executing a mov r8,r6,lsr #0x6 the code does a logical right shift on r6 by 0x6 and stores it in r8. The ~~higer~~ the number used in the lsr, the faster r8 will change. In this case 0x6 was a good enough value to allow enough time when warping between players to kill them.		After checking the switch, if to does not equal '0' the entire section of code performing the auto kill should be skipped completely, so it branches to the label quit. After this first important check, the code then loads all of the necessary varaibles into the registers to begin looping through each player. In the loop, it uses r6 as a timer and r8 as the player number. By executing a mov r8,r6,lsr #0x6 the code does a logical right shift on r6 by 0x6 and stores it in r8. The higher the number used in the lsr, the faster r8 will change. In this case 0x6 was a good enough value to allow enough time when warping between players to kill them.

	==Converting Codes==		==Converting Codes==

← Older revision		Revision as of 20:59, 3 August 2014
Line 28:		Line 28:
	! class="EnHack-desc" colspan="2" \| Conditional 32-Bit Code Types		! class="EnHack-desc" colspan="2" \| Conditional 32-Bit Code Types
	\|-		\|-
	\| class="EnHack-type" \| Type 0x03<br /> ~~Greater~~ Than<br /> 3XXXXXXX YYYYYYYY		\| class="EnHack-type" \| Type 0x03<br /> Less Than<br /> 3XXXXXXX YYYYYYYY
	\| class="EnHack-desc" \| Checks if YYYYYYYY> (word at [XXXXXXX])<br /> If not, the code(s) following this one are not executed (ie. execution status is set to false) until a code type D0 or D2 is encountered, or until the end of the code list is reached.		\| class="EnHack-desc" \| Checks if YYYYYYYY < (word at [XXXXXXX])<br /> If not, the code(s) following this one are not executed (ie. execution status is set to false) until a code type D0 or D2 is encountered, or until the end of the code list is reached.
	\|-		\|-
	\| class="EnHack-type" \| Type 0x04<br /> ~~Less~~ Than<br /> 4XXXXXXX YYYYYYYY		\| class="EnHack-type" \| Type 0x04<br /> Greater Than<br /> 4XXXXXXX YYYYYYYY
	\| class="EnHack-desc" \| Checks if YYYYYYYY < (word at [XXXXXXX]).<br /> If not, the code(s) following this one are not executed (ie. execution status is set to false) until a code type D0 or D2 is encountered, or until the end of the code list is reached.		\| class="EnHack-desc" \| Checks if YYYYYYYY > (word at [XXXXXXX]).<br /> If not, the code(s) following this one are not executed (ie. execution status is set to false) until a code type D0 or D2 is encountered, or until the end of the code list is reached.
	\|-		\|-
	\| class="EnHack-type" \| Type 0x05<br /> Equal To<br /> 5XXXXXXX YYYYYYYY		\| class="EnHack-type" \| Type 0x05<br /> Equal To<br /> 5XXXXXXX YYYYYYYY
Line 42:		Line 42:
	! class="EnHack-desc" colspan="2" \| Conditional 16-Bit + Masking RAM Writes		! class="EnHack-desc" colspan="2" \| Conditional 16-Bit + Masking RAM Writes
	\|-		\|-
	\| class="EnHack-type" \| Type 0x07<br /> ~~Greater~~ Than<br /> 7XXXXXXX ZZZZYYYY		\| class="EnHack-type" \| Type 0x07<br /> Less Than<br /> 7XXXXXXX ZZZZYYYY
	\| class="EnHack-desc" \| Checks if (YYYY)> (not (ZZZZ) < halfword at [XXXX]).<br /> If not, the code(s) following this one are not executed (ie. execution status is set to false) until a code type D0 or D2 is encountered, or until the end of the code list is reached.		\| class="EnHack-desc" \| Checks if (YYYY) < (not (ZZZZ) < halfword at [XXXX]).<br /> If not, the code(s) following this one are not executed (ie. execution status is set to false) until a code type D0 or D2 is encountered, or until the end of the code list is reached.
	\|-		\|-
	\| class="EnHack-type" \| Type 0x08<br /> ~~Less~~ Than<br /> 8XXXXXXX ZZZZYYYY		\| class="EnHack-type" \| Type 0x08<br /> Greater Than<br /> 8XXXXXXX ZZZZYYYY
	\| class="EnHack-desc" \| Checks if (YYYY) < (not (ZZZZ) & halfword at [XXXXXXX]).<br /> If not, the code(s) following this one are not executed (ie. execution status is set to false) until a code type D0 or D2 is encountered, or until the end of the code list is reached.		\| class="EnHack-desc" \| Checks if (YYYY) > (not (ZZZZ) & halfword at [XXXXXXX]).<br /> If not, the code(s) following this one are not executed (ie. execution status is set to false) until a code type D0 or D2 is encountered, or until the end of the code list is reached.
	\|-		\|-
	\| class="EnHack-type" \| Type 0x09<br /> Equal To<br /> 9XXXXXXX ZZZZYYYY		\| class="EnHack-type" \| Type 0x09<br /> Equal To<br /> 9XXXXXXX ZZZZYYYY

← Older revision		Revision as of 14:04, 3 December 2008
Line 29:		Line 29:
	\|-		\|-
	\| class="EnHack-type" \| Type 0x03<br /> Greater Than<br /> 3XXXXXXX YYYYYYYY		\| class="EnHack-type" \| Type 0x03<br /> Greater Than<br /> 3XXXXXXX YYYYYYYY
	\| class="EnHack-desc" \| Checks if YYYYYYYY> (word at [XXXXXXX])<br /> If not, the code(s) following this one are not executed (ie. execution status is set to false) until a code type D0 or D2 is encountered, or until the end of ~~thecode~~ list is reached.		\| class="EnHack-desc" \| Checks if YYYYYYYY> (word at [XXXXXXX])<br /> If not, the code(s) following this one are not executed (ie. execution status is set to false) until a code type D0 or D2 is encountered, or until the end of the code list is reached.
	\|-		\|-
	\| class="EnHack-type" \| Type 0x04<br /> Less Than<br /> 4XXXXXXX YYYYYYYY		\| class="EnHack-type" \| Type 0x04<br /> Less Than<br /> 4XXXXXXX YYYYYYYY
Line 217:		Line 217:
	\|-		\|-
	\| class="EnHack-type" \| Type 0x00<br /> 8-Bit<br /> 0XXXXXXX 000000YY		\| class="EnHack-type" \| Type 0x00<br /> 8-Bit<br /> 0XXXXXXX 000000YY
	\| class="EnHack-desc" \| XXXXXXX = Address to be ~~writen~~ to<br /> YY = Byte to be written		\| class="EnHack-desc" \| XXXXXXX = Address to be written to<br /> YY = Byte to be written
	\|-		\|-
	\| class="EnHack-type" \| Type 0x10<br /> 16-Bit<br /> 1XXXXXXX 0000YYYY		\| class="EnHack-type" \| Type 0x10<br /> 16-Bit<br /> 1XXXXXXX 0000YYYY
	\| class="EnHack-desc" \| XXXXXXX = Address to be ~~writen~~ to<br /> YYYY = Halfword to be written		\| class="EnHack-desc" \| XXXXXXX = Address to be written to<br /> YYYY = Halfword to be written
	\|-		\|-
	\| class="EnHack-type" \| Type 0x20<br /> 32-Bit<br /> 2XXXXXXX YYYYYYYY		\| class="EnHack-type" \| Type 0x20<br /> 32-Bit<br /> 2XXXXXXX YYYYYYYY
	\| class="EnHack-desc" \| XXXXXXX = Address to be ~~writen~~ to<br /> YYYYYYYY = Word to be written		\| class="EnHack-desc" \| XXXXXXX = Address to be written to<br /> YYYYYYYY = Word to be written
	\|-		\|-
	! class="EnHack-desc" colspan="2" \| Increment/Decrement Codes		! class="EnHack-desc" colspan="2" \| Increment/Decrement Codes
	\|-		\|-
	\| class="EnHack-type" \| Type 0x30<br /> 8/16-Bit<br /> 3XXXXXXX 000UYYYY		\| class="EnHack-type" \| Type 0x30<br /> 8/16-Bit<br /> 3XXXXXXX 000UYYYY
	\| class="EnHack-desc" \| XXXXXXX = Address to be ~~writen~~ to<br /> U = Bit-type Write, 0 for 8-Bit and 1 for 16-Bit<br /> YYYY = Halfword/Byte to be written		\| class="EnHack-desc" \| XXXXXXX = Address to be written to<br /> U = Bit-type Write, 0 for 8-Bit and 1 for 16-Bit<br /> YYYY = Halfword/Byte to be written
	\|-		\|-
	\| class="EnHack-type" \| Type 0x38<br /> 32-Bit<br /> 3XXXXXXX YYYYYYYY		\| class="EnHack-type" \| Type 0x38<br /> 32-Bit<br /> 3XXXXXXX YYYYYYYY
	\| class="EnHack-desc" \| XXXXXXX = Address to be ~~writen~~ to<br /> YYYY = Word to be written		\| class="EnHack-desc" \| XXXXXXX = Address to be written to<br /> YYYY = Word to be written
	\|-		\|-
	! class="EnHack-desc" colspan="2" \| Serial Repeat Constant Write (Slider) Code		! class="EnHack-desc" colspan="2" \| Serial Repeat Constant Write (Slider) Code
	\|-		\|-
	\| class="EnHack-type" \| Type 0x40<br /> Slider<br /> 4XXXXXXX TWWWZZZZ<br /> YYYYYYYY VVVVVVVV		\| class="EnHack-type" \| Type 0x40<br /> Slider<br /> 4XXXXXXX TWWWZZZZ<br /> YYYYYYYY VVVVVVVV
	\| class="EnHack-desc" \| XXXXXXX = Address to be ~~writen~~ to<br /> T = Bit-type Write, 0 for 32-Bit, 1 for 16-Bit and 2 for 8-Bit<br /> WWW = Number of times to repeat<br /> ZZZZ = Increase Address by (Multiply by data size (1 << (2 - T)))<br /> YYYY = Word to be written<br /> VVVVVVVV = Increase Value by		\| class="EnHack-desc" \| XXXXXXX = Address to be written to<br /> T = Bit-type Write, 0 for 32-Bit, 1 for 16-Bit and 2 for 8-Bit<br /> WWW = Number of times to repeat<br /> ZZZZ = Increase Address by (Multiply by data size (1 << (2 - T)))<br /> YYYY = Word to be written<br /> VVVVVVVV = Increase Value by
	\|-		\|-
	! class="EnHack-desc" colspan="2" \| Memory Copy Code		! class="EnHack-desc" colspan="2" \| Memory Copy Code

← Older revision		Revision as of 13:59, 3 December 2008
Line 68:		Line 68:
	\|-		\|-
	\| class="EnHack-type" \| Type 0x0C<br /> C0000000 YYYYYYYY		\| class="EnHack-type" \| Type 0x0C<br /> C0000000 YYYYYYYY
	\| class="EnHack-desc" \| This sets the 'Dx repeat value' to YYYYYYYY and saves the 'Dx ~~nextcode~~ to be executed' and the 'Dx execution status'. Repeat will be executed when a D1/D2 code is encountered.<br /> When repeat is executed, the AR reloads the 'next code to be executed' and the 'execution status' from the Dx registers.		\| class="EnHack-desc" \| This sets the 'Dx repeat value' to YYYYYYYY and saves the 'Dx next code to be executed' and the 'Dx execution status'. Repeat will be executed when a D1/D2 code is encountered.<br /> When repeat is executed, the AR reloads the 'next code to be executed' and the 'execution status' from the Dx registers.
	\|-		\|-
	! class="EnHack-desc" colspan="2" \| Special Codes		! class="EnHack-desc" colspan="2" \| Special Codes
Line 76:		Line 76:
	\|-		\|-
	\| class="EnHack-type" \| Type 0xD1<br /> Loop execute variant<br /> D1000000 00000000		\| class="EnHack-type" \| Type 0xD1<br /> Loop execute variant<br /> D1000000 00000000
	\| class="EnHack-desc" \| Executes the next block of codes 'n' times (specified by the 0x0C ~~codetype~~), but doesn't clear the Dx register upon completion.		\| class="EnHack-desc" \| Executes the next block of codes 'n' times (specified by the 0x0C code type), but doesn't clear the Dx register upon completion.
	\|-		\|-
	\| class="EnHack-type" \| Type 0xD2<br /> Loop Execute Variant/ Full Terminator<br /> D2000000 00000000		\| class="EnHack-type" \| Type 0xD2<br /> Loop Execute Variant/ Full Terminator<br /> D2000000 00000000
	\| class="EnHack-desc" \| Executes the next block of codes 'n' times (specified by the 0x0C ~~codetype~~), and clears all temporary data. (i.e. execution status, offsets, code C settings, etc.)<br /> This code can also be used as a full terminator, giving the same effects to any block of code.		\| class="EnHack-desc" \| Executes the next block of codes 'n' times (specified by the 0x0C code type), and clears all temporary data. (i.e. execution status, offsets, code C settings, etc.)<br /> This code can also be used as a full terminator, giving the same effects to any block of code.
	\|-		\|-
	! class="EnHack-desc" colspan="2" \| Data Register Codes		! class="EnHack-desc" colspan="2" \| Data Register Codes
	\|-		\|-
	\| class="EnHack-type" \| Type 0xD4<br /> Add Value<br /> D4000000 XXXXXXXX		\| class="EnHack-type" \| Type 0xD4<br /> Add Value<br /> D4000000 XXXXXXXX
	\| class="EnHack-desc" \| Adds 'XXXXXXXX' to the data register used by ~~codetypes~~ 0xD6 - 0xDB.<br /> More arithmetical/logical operations can be set using the 'NDS AR HACK #2'.		\| class="EnHack-desc" \| Adds 'XXXXXXXX' to the data register used by code types 0xD6 - 0xDB.<br /> More arithmetical/logical operations can be set using the 'NDS AR HACK #2'.
	\|-		\|-
	\| class="EnHack-type" \| Type 0xD5<br /> Set Value<br /> D5000000 XXXXXXXX		\| class="EnHack-type" \| Type 0xD5<br /> Set Value<br /> D5000000 XXXXXXXX
Line 380:		Line 380:
	\|-		\|-
	\| class="EnHack-type" \| Type 0xD1<br /> Loop execute variant<br /> D1000000 00000000		\| class="EnHack-type" \| Type 0xD1<br /> Loop execute variant<br /> D1000000 00000000
	\| class="EnHack-desc" \| Executes the next block of codes 'n' times (specified by the 0x0C ~~codetype~~), but doesn't clear the Dx register upon completion.		\| class="EnHack-desc" \| Executes the next block of codes 'n' times (specified by the 0x0C code type), but doesn't clear the Dx register upon completion.
	\|-		\|-
	\| class="EnHack-type" \| Type 0xD2<br /> Loop Execute Variant/ Full Terminator<br /> D2000000 00000000		\| class="EnHack-type" \| Type 0xD2<br /> Loop Execute Variant/ Full Terminator<br /> D2000000 00000000
	\| class="EnHack-desc" \| Executes the next block of codes 'n' times (specified by the 0x0C ~~codetype~~), and clears all temporary data. (i.e. execution status, offsets, code C settings, etc.)<br /> This code can also be used as a full terminator, giving the same effects to any block of code.		\| class="EnHack-desc" \| Executes the next block of codes 'n' times (specified by the 0x0C code type), and clears all temporary data. (i.e. execution status, offsets, code C settings, etc.)<br /> This code can also be used as a full terminator, giving the same effects to any block of code.
	\|-		\|-
	! class="EnHack-desc" colspan="2" \| Data Register Codes		! class="EnHack-desc" colspan="2" \| Data Register Codes
	\|-		\|-
	\| class="EnHack-type" \| Type 0xD4<br /> Add Value<br /> D4000000 XXXXXXXX		\| class="EnHack-type" \| Type 0xD4<br /> Add Value<br /> D4000000 XXXXXXXX
	\| class="EnHack-desc" \| Adds 'XXXXXXXX' to the data register used by ~~codetypes~~ 0xD6 - 0xDB.<br /> More arithmetical/logical operations can be set using the 'NDS AR HACK #2'.		\| class="EnHack-desc" \| Adds 'XXXXXXXX' to the data register used by code types 0xD6 - 0xDB.<br /> More arithmetical/logical operations can be set using the 'NDS AR HACK #2'.
	\|-		\|-
	\| class="EnHack-type" \| Type 0xD5<br /> Set Value<br /> D5000000 XXXXXXXX		\| class="EnHack-type" \| Type 0xD5<br /> Set Value<br /> D5000000 XXXXXXXX
Line 1,313:		Line 1,313:
	\|-		\|-
	\| class="EnHack-addy" \| 62105F88 00000000		\| class="EnHack-addy" \| 62105F88 00000000
	\| class="EnHack-comments" \| ~~Codetype~~ 6, or a 32-bit != code type, sort of part of the pointer. (Used for the conditional)		\| class="EnHack-comments" \| Code type 6, or a 32-bit != code type, sort of part of the pointer. (Used for the conditional)
	\|-		\|-
	\| class="EnHack-addy" \| B2105F88 00000000		\| class="EnHack-addy" \| B2105F88 00000000
Line 1,324:		Line 1,324:
	\|}		\|}

	Action Replay DS pointers are laid out so that the pointer address is temporarily loaded into the data register, and then a code is written using this offset as a baseline. The Codebreaker actually has a nice pointer ~~codetype~~, on the other hand.		Action Replay DS pointers are laid out so that the pointer address is temporarily loaded into the data register, and then a code is written using this offset as a baseline. The Codebreaker actually has a nice pointer code type, on the other hand.

	{\| class="EnHack-code"		{\| class="EnHack-code"