View previous topic :: View next topic |
Author |
Message |
Rammwurst How do I cheat? Reputation: 0
Joined: 18 Jul 2017 Posts: 8
|
Posted: Wed Jul 19, 2017 12:19 pm Post subject: Prevent memory viewer from opening during Lua Debugging? |
|
|
I'm executing the following script, but everytime I do the memory viewer opens up, is there a way to prevent this or a command that closes it again?
Code: | [ENABLE]
{$LUA}
debug_removeBreakpoint(address);
debug_setBreakpoint(address, 4, bptWrite);
function debugger_onBreakpoint()
lockAddress = RIP-2
writeBytes(lockAddress, 56, 00)
debug_continueFromBreakpoint(co_run)
return 0;
end
[DISABLE]
{$LUA}
writeBytes(lockAddress, 00, 00)
debug_removeBreakpoint(address);
lockAddress=0 |
|
|
Back to top |
|
|
FreeER Grandmaster Cheater Supreme Reputation: 53
Joined: 09 Aug 2013 Posts: 1091
|
Posted: Wed Jul 19, 2017 2:08 pm Post subject: |
|
|
this may work...not tested however
Code: | getMemoryViewForm().Visible = false |
|
|
Back to top |
|
|
Dark Byte Site Admin Reputation: 458
Joined: 09 May 2003 Posts: 25287 Location: The netherlands
|
Posted: Wed Jul 19, 2017 2:28 pm Post subject: |
|
|
change return 0 to return 1 (looks like the behavior is inverted for bp specific handlers)
or
Code: |
debug_removeBreakpoint(address);
debug_setBreakpoint(address, 4, bptWrite, function()
function debugger_onBreakpoint()
lockAddress = RIP-2
writeBytes(lockAddress, 56, 00)
debug_continueFromBreakpoint(co_run)
return 0;
end )
|
_________________
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 |
|
|
Rammwurst How do I cheat? Reputation: 0
Joined: 18 Jul 2017 Posts: 8
|
Posted: Wed Jul 19, 2017 2:50 pm Post subject: |
|
|
FreeER wrote: | this may work...not tested however
Code: | getMemoryViewForm().Visible = false |
|
That works if used in a script after the script that opened the memory viewer, for me anyway.
Dark Byte wrote: | change return 0 to return 1 (looks like the behavior is inverted for bp specific handlers)
or
Code: |
debug_removeBreakpoint(address);
debug_setBreakpoint(address, 4, bptWrite, function()
function debugger_onBreakpoint()
lockAddress = RIP-2
writeBytes(lockAddress, 56, 00)
debug_continueFromBreakpoint(co_run)
return 0;
end )
|
|
Thank you that worked perfectly, i used it like this
Code: | debug_continueFromBreakpoint(co_run)
return 1;
end |
|
|
Back to top |
|
|
|