Hello, GBAtemp.
Some weeks ago I created a fork of the original NTR debugger made by cell9 from the following github page: https://github.com/44670/NTRClient . My intention was to create some easier cheating methods for the 3ds then having to write a NTR plugin yourself or buying gateway. I also wanted to make it easier for people to start working with the NTR debugger, therefor I added some buttons to make life easier. Since some of you have already seen this debugger on reddit I finally decieded to make a post here. Also because people wanted to use gateshark codes with NTR.
This does only work with kernel access. You need a sysNAND version of 9.2 or below. I'd recommend using NTR on emuNAND. All versions are supported.
I'm no longer working on this project. If somebody wants to for the project, go to the github page and do so. Hope somebody does so.
Basic tab
As you can see in the first tab I created separate buttons to 'connect', 'disconnect', 'list all processes', 'see the memlayout', 'dump a file of a specified memregion', 'See an address' and 'write to an address'.
When starting your 3ds you have to start NTR first with any method you like. I prefer the BootNTR cia for version NTR 3.3. When you started NTR press X+Y and start the debugger. When that's finished just connect the debugger on your pc by entering the Nintendo 3ds IP address in the corresponding textfield. Press 'Connect'. This might take some tries, NTR is pretty buggy when connecting. Often the connection will just 'Timeout' after maybe 30 seconds. If that happens you have to try again. This is a problem with NTR itself. Once you connected start a game and press the 'List processes' button. You should see a list of all currently running processes on your 3ds. One of them should stand out. Game Process names often start capitalized or are in full caps. The process name is not the same as the game name. 'Monster Hunter 4 Ultimate' for example has the process name 'REDGIANT'. Next to the process list you should see the PID of that process. Enter the PID, which looks something like: 29, 2A, 3A, 3F, 34.. etc , into the 'Process PID' textbox - You mustn't write the 0x in front of the PID.
Once you finished setting up everything you can finally start using cheats. I prepared some sample cheatcodes in the corresponding tabs ( EUR, USA, JPN ), but there aren't very many. You might also notice the Gateshark tab. For some gateshark instructions please open the following SPOILER
Here are some screenshots of the modified NTR debugger.
As of version 1.4 I started making some small previews of upcoming features. If you want to view them just open the following spoiler
Download link: https://github.com/imthe666st/NTRClient/releases
Having an issue or an idea for an enhancement? : https://github.com/imthe666st/NTRClient/issues ( or just post it in the comments right here)
Having issues with booting NTR? Take a look http://gbatemp.net/threads/release-ntr-cfw-3-2-with-experimental-real-time-save-feature.385142/
DISCLAIMER
I am in no way responsive or to blame if you get caught cheating online and get banned. This is primarily for singleplayer use only! If you got banned it's your own fault!
Some weeks ago I created a fork of the original NTR debugger made by cell9 from the following github page: https://github.com/44670/NTRClient . My intention was to create some easier cheating methods for the 3ds then having to write a NTR plugin yourself or buying gateway. I also wanted to make it easier for people to start working with the NTR debugger, therefor I added some buttons to make life easier. Since some of you have already seen this debugger on reddit I finally decieded to make a post here. Also because people wanted to use gateshark codes with NTR.
This does only work with kernel access. You need a sysNAND version of 9.2 or below. I'd recommend using NTR on emuNAND. All versions are supported.
I'm no longer working on this project. If somebody wants to for the project, go to the github page and do so. Hope somebody does so.
Basic tab
This is the "BASIC" tab as of Version 1.2-2
As you can see in the first tab I created separate buttons to 'connect', 'disconnect', 'list all processes', 'see the memlayout', 'dump a file of a specified memregion', 'See an address' and 'write to an address'.
When starting your 3ds you have to start NTR first with any method you like. I prefer the BootNTR cia for version NTR 3.3. When you started NTR press X+Y and start the debugger. When that's finished just connect the debugger on your pc by entering the Nintendo 3ds IP address in the corresponding textfield. Press 'Connect'. This might take some tries, NTR is pretty buggy when connecting. Often the connection will just 'Timeout' after maybe 30 seconds. If that happens you have to try again. This is a problem with NTR itself. Once you connected start a game and press the 'List processes' button. You should see a list of all currently running processes on your 3ds. One of them should stand out. Game Process names often start capitalized or are in full caps. The process name is not the same as the game name. 'Monster Hunter 4 Ultimate' for example has the process name 'REDGIANT'. Next to the process list you should see the PID of that process. Enter the PID, which looks something like: 29, 2A, 3A, 3F, 34.. etc , into the 'Process PID' textbox - You mustn't write the 0x in front of the PID.
Once you finished setting up everything you can finally start using cheats. I prepared some sample cheatcodes in the corresponding tabs ( EUR, USA, JPN ), but there aren't very many. You might also notice the Gateshark tab. For some gateshark instructions please open the following SPOILER
The gateshark tab as of version 1.2-2
This is the gateshark tab. You can use most gateshark codes using this. Codes that require button presses will ignore the button presses, since you can't emulate this. There are also a few not yet supported gateshark codes, mostly the conditional codes. If your code doesn't work, please report it in the comments.
To find gateshark codes go to http://www.fort42.com/gateshark/
Using the gateshark codes with the modified NTR debugger:
Once you grabbed a gateshark code from fort42 simply insert it into the textbox with the default code
and override it. Press 'Try Gateshark' first to see this code can be compiled. This doesn't automatically mean the code will work! If some numbers and letters appeared in the right textbox hit 'Execute Gateshark'. This will execute it.
For gateshark codes that have multiple different effect depending on the button presses, please split them using the following:
This is the gateshark tab. You can use most gateshark codes using this. Codes that require button presses will ignore the button presses, since you can't emulate this. There are also a few not yet supported gateshark codes, mostly the conditional codes. If your code doesn't work, please report it in the comments.
To find gateshark codes go to http://www.fort42.com/gateshark/
Using the gateshark codes with the modified NTR debugger:
Once you grabbed a gateshark code from fort42 simply insert it into the textbox with the default code
Code:
00000000 00000000For gateshark codes that have multiple different effect depending on the button presses, please split them using the following:
To split a gateshark code into multiple different codes we will use the following example ( because I'm bad at explaining )
We can split this code into 3 different parts. The following spoiler shows the same code again, with the parts infront of the lines:
As you can see part 2 and 3 are the individual codes with the button presses in front of them. Part 1 is needed for both part 2 and part 3, since it's written without any button combo needed. That way we can split this into 2 different codes. It will look the following:
Don't worry about the unneccessary Button combos, the debugger will simply ignore them.
Well done, you just split your code into 2. You can also ask me if you need help. That's no problem
Code:
B8100000 00000000 ; READ OFFSET FROM 8100000
DD000000 00000001 ; BUTTON COMBO INDEX 1
00100000 12345678 ; WRITE 12345678 TO 100000
D0000000 00000000 ; END BUTTON COMBO
DD000000 00000002 ; BUTTOM COMBO INDEX 2
00200000 90ABCDEF ; WRITE 90ABCDEF TO 200000
D0000000 00000000 ; END BUTTON COMBOWe can split this code into 3 different parts. The following spoiler shows the same code again, with the parts infront of the lines:
Code:
1 : B8100000 00000000 ; READ OFFSET FROM 8100000
2 : DD000000 00000001 ; BUTTON COMBO INDEX 1
2 : 00100000 12345678 ; WRITE 12345678 TO 100000
2 : D0000000 00000000 ; END BUTTON COMBO
3 : DD000000 00000002 ; BUTTOM COMBO INDEX 2
3 : 00200000 90ABCDEF ; WRITE 90ABCDEF TO 200000
3 : D0000000 00000000 ; END BUTTON COMBO
Code:
[OUR CODE 1]
B8100000 00000000 ; READ OFFSET FROM 8100000
DD000000 00000001 ; BUTTON COMBO INDEX 1
00100000 12345678 ; WRITE 12345678 TO 100000
D0000000 00000000 ; END BUTTON COMBO
[OUR CODE 2]
B8100000 00000000 ; READ OFFSET FROM 8100000
DD000000 00000002 ; BUTTOM COMBO INDEX 2
00200000 90ABCDEF ; WRITE 90ABCDEF TO 200000
D0000000 00000000 ; END BUTTON COMBODon't worry about the unneccessary Button combos, the debugger will simply ignore them.
Well done, you just split your code into 2. You can also ask me if you need help. That's no problem
Here are some screenshots of the modified NTR debugger.
When starting the debugger
NTR debugger in use:
NTR debugger in use:
As of version 1.4 I started making some small previews of upcoming features. If you want to view them just open the following spoiler
Clearing the log
Heartbeat codes - Gateshark codes automatically executed all 4 seconds.
Update checker
Selecting a process:
Heartbeat codes - Gateshark codes automatically executed all 4 seconds.
Update checker
Selecting a process:
Download link: https://github.com/imthe666st/NTRClient/releases
Having an issue or an idea for an enhancement? : https://github.com/imthe666st/NTRClient/issues ( or just post it in the comments right here)
Having issues with booting NTR? Take a look http://gbatemp.net/threads/release-ntr-cfw-3-2-with-experimental-real-time-save-feature.385142/
DISCLAIMER
I am in no way responsive or to blame if you get caught cheating online and get banned. This is primarily for singleplayer use only! If you got banned it's your own fault!
Last edited by Deleted member 369977,
