Search found 37 matches
- Sat Dec 19, 2020 12:06 pm
- Forum: Cheat Engine Lua Scripting
- Topic: Trainer Works When In CT Form But Not Standalone EXE
- Replies: 3
- Views: 8889
Re: Trainer Works When In CT Form But Not Standalone EXE
If you do not want to mess with windows registry, you can change Cheat Engine's memory. You can find addresses the similar way I did for CE6.6 - attach CE to itself, open "referenced strings" window. This time, search for first reference of string "Can Step Kernelcode" and look at the code above. Th...
- Fri Dec 18, 2020 3:36 pm
- Forum: Cheat Engine Lua Scripting
- Topic: Trainer Works When In CT Form But Not Standalone EXE
- Replies: 3
- Views: 8889
Re: Trainer Works When In CT Form But Not Standalone EXE
Similar topic from CEF: https://forum.cheatengine.org/viewtopic.php?t=602775 use this Lua script: function set_MEM_MAPPED() local s = getSettings() local oldValue = s.Value['MEM_MAPPED'] s.Value['MEM_MAPPED'] = 1 reloadSettingsFromRegistry() s.Value['MEM_MAPPED'] = oldValue s.destroy() end set_MEM_M...
- Sun Sep 27, 2020 3:39 pm
- Forum: Cheat Engine Lua Scripting
- Topic: Trying to understand createMemScan() on an old RE7 item script.
- Replies: 2
- Views: 7413
Re: Trying to understand createMemScan() on an old RE7 item script.
Code: Select all
local myVariable = 'test1234'
print( #myVariable )
print( string.len(myVariable) )
print( myVariable:len() )
8
8
8
- Wed Jul 29, 2020 9:29 pm
- Forum: Cheat Engine
- Topic: CE 7.1 Script Problems
- Replies: 12
- Views: 4311
Re: CE 7.1 Script Problems
@l0wb1t, do you still have problems when you use "jne short code2"? Or you just do not like the look of multibyte NOP (I mean this "nop dword ptr [rax]"). Well, other disassemblers also show "0F 1F 00" as "nop dword ptr [rax]" x64dbg: https://i.imgur.com/LtDJV6O.png In that case, you can override CE...
- Wed Jul 29, 2020 2:55 pm
- Forum: Cheat Engine
- Topic: CE 7.1 Script Problems
- Replies: 12
- Views: 4311
Re: CE 7.1 Script Problems
Multibyte nops are normal things these days. Many modern compilers use those. Just attach CE to your game and do assemblyscan for "nop *" (without "). You will find plenty of them. I know that nop x is a replacement by nops. For example nop 3 represents 3 times nop "nop 3" will use "3 bytes nop", wh...
- Wed May 27, 2020 1:06 am
- Forum: General Gamehacking
- Topic: To avoid the injection code
- Replies: 3
- Views: 2616
To avoid the injection code
It is possible to use code caves filled with 0x00. But:<br /> - it can happen you just found a structure with many vars and those vars are initialized with zeros. Altering it will cause unpredictable behavior.<br /> - when you found code cave filled with 0x00 in memory, let's say cave size is 300-50...
- Sat May 23, 2020 3:01 pm
- Forum: General Gamehacking
- Topic: To avoid the injection code
- Replies: 3
- Views: 2616
To avoid the injection code
Find a cave filled with "90" or "cc" as close as possible.<br /> You can also find caves filled with many kinds of nop with "Assemblyscan" (memory viewer -> search -> find assembly code)<br /> <br /> Use a call instead of jump. Last instruction should be ret.<br /> <br /> <br /> <br /> Example with ...
- Thu May 14, 2020 7:06 pm
- Forum: Generic Tutorials
- Topic: DOSBox Static Addresses
- Replies: 53
- Views: 574236
Re: DOSBox Static Addresses
I got a PC when Windows Me was released. Before that I had only C64 :) I didn't do much with programming in DOS - simple tasks in Turbo Pascal 7 (with graph library) and some very basic executable modifications with Hiew 6.50. To sum this up - DOS is not my thing. GameMemoryStart, VideoMemory, GameO...
- Wed May 13, 2020 2:18 pm
- Forum: Cheat Engine
- Topic: Bug 7.1 CE version
- Replies: 31
- Views: 11254
Re: Bug 7.1 CE version
Guys thank you all - it's working :) Do have to translate all the tables this way ? Only those with memory records with descriptions: "float", "fLoAt",..., "FLOAT", "double", "dOuBlE",..., "DOUBLE", "int", "iNt", ..., "INT". Add this to cheat engine autorun folder (as ".lua" file, not ".lua.txt"): ...
- Wed May 13, 2020 12:09 pm
- Forum: Cheat Engine
- Topic: Bug 7.1 CE version
- Replies: 31
- Views: 11254
Re: Bug 7.1 CE version
As mentioned previously you have a memory record with description "float". Just open your CT file with notepad++ or other decent text editor and search for <Description>"float"</Description> and change that to <Description>"float value"</Description> Then save the changes. Or load your CT file and e...
- Wed May 13, 2020 1:00 am
- Forum: Cheat Engine
- Topic: Bug 7.1 CE version
- Replies: 31
- Views: 11254
Re: Bug 7.1 CE version
Probably this is the cause. In his last last video ( 5:47 ), hex value is +1 and then +100 to some other value.
"(float)1" got converted to "somevalue+1" and "somevalue+100"
"(float)1" got converted to "somevalue+1" and "somevalue+100"
- Tue May 12, 2020 7:31 pm
- Forum: Cheat Engine
- Topic: Bug 7.1 CE version
- Replies: 31
- Views: 11254
Re: Bug 7.1 CE version
Too bad you didn't check the "dd (float)1" with single-line assembler and "(FLOAT)1" used as pointer offset. That would give us much more info. e.g. "dd (float)1" is one of few things processed at the very beginning of TSingleLineAssembler.Assemble function. "(FLOAT)1" used as pointer offset would t...
- Tue May 12, 2020 3:33 pm
- Forum: Cheat Engine
- Topic: Bug 7.1 CE version
- Replies: 31
- Views: 11254
Re: Bug 7.1 CE version
float conversion to hex is made in this simple piece of code (ConvertHexStrToRealStr function inside parsers.pas): if copy(s,1,7)='(FLOAT)' then begin t:=copy(s,8); val(t, f,j); if j=0 then begin result:='$'+inttohex(pdword(@f)^,8); if s[1]='-' then result:='-'+result; if s[1]='+' then result:='+'+r...
- Mon May 11, 2020 5:32 pm
- Forum: Cheat Engine
- Topic: Bug 7.1 CE version
- Replies: 31
- Views: 11254
Re: Bug 7.1 CE version
Does it happen when you use a single-line assembler?
- Mon May 11, 2020 1:26 pm
- Forum: Cheat Engine
- Topic: Bug 7.1 CE version
- Replies: 31
- Views: 11254
Re: Bug 7.1 CE version
What happens when you use single line assembler and not AA script?
In memory viewer double click on any "add [rax],al" and type in:
and also try this:
and check if it sets bytes to 80 3F 00 00
In memory viewer double click on any "add [rax],al" and type in:
Code: Select all
mov [rax+70],(float)1
Code: Select all
dd (float)1