Cheat Engine

[h3x1c]

When modifying code in the disassembler, I've run into scenarios where changing the Assembly back to what an instruction originally was, results in a different byte representation (like a more optimized version of an instruction or something that uses the same number of bytes). This has a tendency to break scripts I'm working on, as well as add more steps in what I have to document during the reversing/script-writing process.

I like to work using bytes as much as possible when writing cheats, etc., so if it seems like a feasible addition, it would be really awesome to have the option to input bytes instead of Assembly in the assembler box (perhaps have 2 input boxes, one for entering Assembly and the other for bytes).

Thoughts?

[Dark Byte]

if you use code injection template scripts, you'll find that the generator also generates a commented out line saying :"alt db xx xx xx xx"

if you use that db line it will generate the exact bytes

You are also free to use 'db' everywhere else, but I don't suggest it

[ParkourPenguin]

The db pseudoinstruction is a thing that exists.

[h3x1c]

Oh, wow! That works great. I didn't realize I could use db to write bytes directly in the disassembler like that.

To clarify for others, my opening post was in reference to this box in the disassembler:



Instead of that, typing something akin to this would work: