Skip to content

RAM Editing & Item Injection

Kurt edited this page Sep 30, 2020 · 30 revisions

Summary

By using sys-botbase, we can remotely read and modify the game's RAM from our PC.

  • Using this functionality requires the sys-botbase sysmodule running on the console.
  • Your console must be on the same network as the PC running this program.

NHSE provides two methods for RAM Manipulation:

  • Arbitrary RAM read/write via the Main Editor's RAM Edit (CTRL-H).

    • Connect and request RAM at a specific offset & length.
    • Update when finished, or close the window to cancel.
  • Pocket Item Injection

    • In the Player Items window, click the Injector button and connect.
    • Check the checkboxes to make the window sync with the game. Any changes will be copied to the game, and vice versa.
    • If you are having issues with FailValidate, you can turn off the validation checkbox.
  • Pocket Item Offsets: Use the corresponding offset for the version of the game you are playing.

    • V1.0: ???
    • V1.1: AC3B90C0
    • V1.2: AC4723D0
    • V1.3: ABA526A8
    • V1.4: ABADD888
    • V1.5: ABC25840

Accessing these features without a save file

  • You don't need to load a save file to access the RAM/Item injectors. From the main window (the small window, not the editor), press CTRL-H to bring up the hex editor, or CTRL-I to bring up the item editor.

Troubleshooting

At the time this wiki was written, the Release version of sys-botbase you should use is v1.3, as dmnt-cheat compatibility is unstable.

Q - My read/writes appear invalid?

A - You likely have cheats enabled, Disable them as they will cause issues. This may require you to restart the game / reboot the console if you don't have cheats enabled. Known cheats are Atmosphere, EdiZon, Tesla, Checkpoint.

Q - How do I disable cheats?

A - To disable Atmosphere cheats temporarily for a specific title, hold L whilst launching.

Q - I'm getting error messages after connecting. How to troubleshoot?

A - Double check your WiFi settings, and ensure your console is close to your router. Try ping {ipaddress} in command prompt to ensure that the ping is low, and that your bot is not dropping packets.

Clone this wiki locally