| View previous topic :: View next topic |
| Author |
Message |
kickclock Advanced Cheater
Reputation: 0
Joined: 15 Jan 2008 Posts: 73
|
Posted: Tue Jul 13, 2010 2:31 am Post subject: a bug in Readmem(xx,xx) |
|
|
an example script
[ENABLE]
globalalloc(mytestmem,0x1000)
mytestmem:
db 'Cheatengine!'
db 00
mytestmem+10:
readmem(mytestmem,0x10)
[DISABLE]
after enable script, mytestmem+10 is 0 .
in my plan, script will run my code one by one .
but looks like readmem is runing as first .
is there some thing can fix this bug ?
maybe a new order like this could useful
[ENABLE]
[first]
globalalloc(mytestmem,0x1000)
mytestmem:
db 'Cheatengine!'
db 00
[/first]
mytestmem+10:
readmem(mytestmem,0x10)
[DISABLE]
_________________
Love CE |
|
| Back to top |
|
 |
Dark Byte Site Admin
Reputation: 471
Joined: 09 May 2003 Posts: 25832 Location: The netherlands
|
Posted: Tue Jul 13, 2010 4:50 am Post subject: |
|
|
it's not a bug, it's designed like this. Writing to the memory is only done after everything in the script has been assembled into code and bytes, reading mytestmem and writing the bytes at the specific position just won't work
best solution is split it up into two script
Also, ask yourself why you need it, perhaps there is a different better way to solve the problem.
_________________
Do not ask me about online cheats. I don't know any and wont help finding them.
Like my help? Join me on Patreon so i can keep helping |
|
| Back to top |
|
 |
kickclock Advanced Cheater
Reputation: 0
Joined: 15 Jan 2008 Posts: 73
|
Posted: Tue Jul 13, 2010 5:53 am Post subject: |
|
|
i see.
i will write them into two scipts.
_________________
Love CE |
|
| Back to top |
|
 |
|