![]() C7 is the opcode, 85 is an r/m32 byte (technically bits 3-5 in the r/m32 byte are part of the opcode: C7 /0 ), and imm32 is some 32-bit number. If C7 85 equals 'mov rbp', then why are most line with 'mov' in the trace starting with 48 instead of C7?Ĭ7 85 means "mov ,imm32". This doesn't matter in the case of that mov instruction, but there exist location-dependent instructions where using readmem like that would crash the game when the code gets executed. Minor nitpick on the author of that script, but under lblResOrig, it should be using reassemble(FASTRESEARCH) instead of readmem(FASTRESEARCH,7). It even says that in the comment above those pseudoinstructions: "db C7 85, readmem(addr,4), dd 0" is equivalent to "mov ,0". Lua could also be used but is unnecessary in these simple cases. Assembling instructions manually with pseudoinstructions is the most direct way of solving that. You don't know what the offset is: it was replaced with wildcards in the aob pattern. What does the 'db C7 85', readmem, dd 0 do? Why write it in bytes instead of assembly instructions? "? 00 00" in the pattern is the offset +B8 in the instruction. The ? used in the scan is probably for compatibility with different versions I think? "Frostpunk.exe"+12491D9: E8 D2 DB FF FF - call Frostpunk.exe+1246DB0 "Frostpunk.exe"+12491B5: FF 15 D5 DC 9F 00 - call qword ptr ORIGINAL CODE - INJECTION POINT: "Frostpunk.exe"+12491EB "Writes the memory at the specified address with the specified size to the current location." I checked for a timer with all kinds of increase/decrease scans but there were just too many results.Īobscanmodule(FASTRESEARCH,Frostpunk.exe,48 8B 85 ?0000 48 89 44 24 ? F3) // should be unique The script looks simple enough, but I wonder how the creator found this part of assembly to change in the first place. I found this trainer that works, but don't understand some parts: I made some cheats for Frostpunk, but after a day of messing around in the code I couldn't find out how to speed up the 'research tech' process. ![]() No not mono just normal pointer scan just below the "generate pointermap" in 7.Posted: Mon 11:52 am Post subject: Help me understand this CE script Reported to DB, but I can't track it down on my own. I have isses with mono in CE 7.2 - the auto-assembler can't generate the code for some reason.
0 Comments
Leave a Reply. |