Peeking and Poking

[optimism247]

I'm not sure if I would call this an issue, but I'm not exactly sure who to reach out to in means of this matter.

When attempting to peek a code, it seems like the script isn't going anywhere. Nor does it do anything in the poking process either.

I'm using sendCommand (s, "peek 0xcode") and following up with sendCommand (s, "poke 0xcode")

But it's just not writing the code.

Any advice?

[wwwwwwzx]

You may use socket.recv() to get the response of "peek" from console. My example: https://github.com/wwwwwwzx/PyNXBot/blob/master/nxbot/PyNXBot.py#L30-L33

[olliz0r]

One thing to note is that when you are using any form of cheats (EdiZon or AMS Cheats for example) the current cheat implementations will block sys-botbase from reading/writing to memory. I know of a case where someone had a cheatfile for pokemon on his sd in a specific folder and AMS would attach dmntcht to the process upon launch, blocking sys-botbase from attaching itself to the process. Deleting the cheat file then fixed the issue.

If you are using the latest sys-botbase you can try sending the command "configure printDebugResultCodes 1", this will tell the sysmodule to print any failing result codes and we can use it to debug.

[Chaos192]

One thing to note is that when you are using any form of cheats (EdiZon or AMS Cheats for example) the current cheat implementations will block sys-botbase from reading/writing to memory. I know of a case where someone had a cheatfile for pokemon on his sd in a specific folder and AMS would attach dmntcht to the process upon launch, blocking sys-botbase from attaching itself to the process. Deleting the cheat file then fixed the issue.

If you are using the latest sys-botbase you can try sending the command "configure printDebugResultCodes 1", this will tell the sysmodule to print any failing result codes and we can use it to debug.

Is there a way to just poke the cheats using sysbot directly or no?