also chain fishing should be done before egg bot get all the simple ones out of the way before doing the breeding one
- Status
eh if theres a problem with bugs in ntr thats a huge problem since ntrs not open source
Black screen? Or connection lost?
--------------------- MERGED ---------------------------
Got same error with the softresetting bot
i get black screen randomly on sr bot and the wonder trade bot gets stuck on pss screen some times itneeds fixing
Connection Lost. Constantly on 107 Sr´s
In Earlier Versions was this a Memory Write Protection Failure exactly on 107 Sr´s
"Basically, trying to fix the blackscreen issue I moved the reconnection with the game from the initial cut-scene to after the game is loaded, that also gives a little disadvantage, after the reset, A button presses are time-based until I send the reconnect command, so there's also a slight chance to lose commands, that's the only part of the bot which can't read the screen."
I dont understand what this on
I have the Same Error After 106/107 Sr's in all Versions!
I have the Same Error After 106/107 Sr's in all Versions!
of course, i turned on ntr cfw and i have the cheat plugin
also, i turned on the debugging :o
Sad to hear the blackscreen/connection lost issue is still present. However, I think I've found the cause and it's probably fixable.
Basically any process started by the 3DS is assigned a number, called PID (not related PID of the pokémon). It starts at at a number between 0x29 to 0x2F, and in every soft reset this is increased by 0x2, currently, the PID variable is a one byte variable, so when it gets to 0xFE or 0xFF, it overflows to 0x00 or 0x01, which are the pid's of other processes, meanwhile the pokémon game process is in 0x100 or 0x101.
This causes the reading error because the program tries to read a memory location which doesn't exist in the process 0x01 or 0x02, breaking the bot (memory write problem), and likely NTR (black screen). This also explains why the program fails at 106-107 soft resets. For example, if the bot started with a game PID of 0x2A, after 106 resets the PID becomes 0xFE, in the next reset it will become 0x100, but the program tries to read the 0x00 process.
Currently testing this theory (game process started at 0x2C, currently at 0x6D), if this theory is true, is fixable by making the PID a 8-byte variable.
Basically any process started by the 3DS is assigned a number, called PID (not related PID of the pokémon). It starts at at a number between 0x29 to 0x2F, and in every soft reset this is increased by 0x2, currently, the PID variable is a one byte variable, so when it gets to 0xFE or 0xFF, it overflows to 0x00 or 0x01, which are the pid's of other processes, meanwhile the pokémon game process is in 0x100 or 0x101.
This causes the reading error because the program tries to read a memory location which doesn't exist in the process 0x01 or 0x02, breaking the bot (memory write problem), and likely NTR (black screen). This also explains why the program fails at 106-107 soft resets. For example, if the bot started with a game PID of 0x2A, after 106 resets the PID becomes 0xFE, in the next reset it will become 0x100, but the program tries to read the 0x00 process.
Currently testing this theory (game process started at 0x2C, currently at 0x6D), if this theory is true, is fixable by making the PID a 8-byte variable.
Last edited by drgoku282,
New version is up, this should fix the Soft-reset bot, testing it right now.
Link: https://github.com/drgoku282/PKMN-NTR/releases/tag/1.18.4-beta3
Link: https://github.com/drgoku282/PKMN-NTR/releases/tag/1.18.4-beta3
- Status
Similar threads
- No one is chatting at the moment.
