Connecting to a console
Click File > Connect to console... or press CTRL+O. It will open up a dialog for connecting to a console. By default, XBDM is selected.
-
Binary File treats a file as a console. This is useful for searching a memory dump file, but I'd still recommend using cheat engine as it's significantly faster (just note that cheat engine is little-endian only).
-
XBDM uses the Xbox Debug Monitor's command system. It provides the most features that Memory Engine uses and is well tested, but seems slightly slower than XDevkit when reading values
-
XDevkit uses COM objects, implemented by
xbdm.dllwhich you get when you install Xbox 360 neighbourhood. This connection is only really here as a point of concept; the XBDM connection can do almost everything this one can, since XDevkit uses XBDM behind the scenes anyway
There's also a debug connection called "Test", that either does nothing, or throws an IO or timeout exception when attempting to read/write. This is used to ensure errors are handled properly
Memory Engine is designed to be pretty flexible. It allows you to register any number of connection types, e.g. for a PS3. So feel free to try writing one for yourself! See MemEngine360.Xbox360XBDM for examples.
Some things, such as Task Sequences, the Debugger, and Lua Scripts, support a "dedicated connection", which is literally just a new connection separate from the engine's connection. It usually has the same icon as the normal connect icon except with a gold arrow
