Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Hex editor improperly displays the values of addresses when a cheat size smaller than the data size is applied to one of the addresses #1026
This one is trickier to solve then the other one.
For reference, the problem lies in GenerateMemoryViewString, line 512 of HexEditor.cs
The code pulls in the displayed number of bytes even if a cheat only effects one byte. I'm not sure when I'll sort this out but that's the place to start if anyone is interested.