Memory Hacking Software

i was using my LSS script just fine like always, then it wouldnt work. no matter what i did. i did not change the script in any way. other hotkeys would work that were not script, but not the hotkeys in my scripts. i tried another version and the same thing! the only thing thats the same with the 2 versions was the defprof.ini file. so i deleted MHS and unzipped a new one. viola it worked fine. about an hour or 2 later, wouldnt work again. now i cant make it work even on a fresh unzip. ive tested with versions 4.0.0.14, 5.001, and 5.002.
nobody else has ever had a problem like this that i have talked to. makes me think its a problem on my side but i dont know what it could be. any ideas?

If you open another MHS that uses the same Hotkeys it will unregister the ones used by the first.

And try Polling Method when they stop working.


L. Spiro

i only use 1 MHS at a time and polling method never works for me in games. i have always had a problem of the LSS hotkeys not working sometimes, usually when i first make the hotkey, but usually it fixes itself. when it used to happen i thought i was doing the coding wrong and thats y it wasnt working, but i know the code is correct because it was working fine and i havent changed it at all. i have rewritten the code, tried using different hotkeys, nothing will work now. hotkeys such as lock/unlock address, subsearch, etc. work perfectly. only script function hotkeys wont work >.<

There is no difference in the interface between Hotkeys can each of their functions. That is, the interface to make Lock/Unlock work is the same as the one for calling script functions.

So be sure the function is actually being called.
If the scripts fail to compile or if their functionality is blocked they will not work.


L. Spiro

ok figured out what the problem was (thx to compmstr). the base address had changed and in my table i use module+offset but in the script i cant use that so when it changed i didnt know. can u make it so we can use the module+offset in scripts on a future release plz?

External variables already use module+offset for addressing. That is the whole point of the { "", OFFSET } format.

However you must realize that when MHS starts up and it compiles the scripts, that module does not exist, so the addresses of globals can not be correctly resolved.
Therefore this syntax can only be used with external variables declared inside functions (because the address will be resolved each time it is declared, which means each time the function is called). If you are using them outside of functions, you need to move them.


L. Spiro

ooohhhhhh, i understand now. thanks.