kiynox

[ @salim_000 ]
---
While performing search, you need to freeze the game. Go enable "Autopause Game" feature to "Yes". Or using a script:
gg.processPause() gg.searchNumber(12, gg.TYPE_FLOAT) gg.processResume() ---

[ @angel88888 ]
---
I think what @nok1a meant before is that: you shouldn't use GG inbuilt speedhack but rather change the speed properties of that player inside the game. You can modify speed stats or items that can buff your speed to higher value. Game Guardian inbuilt speed-hack is speeding up your entire game, which will cause desync as explained earlier.
---

[ @GuyLian ]
---
The reason I ask you is because:
Software/Hardware sets the register value at current state, meaning that you need to change all/specific instruction that does "mov w21, 0xB0FF" to "mov w21, 0xB0CC" Since the value on the register is often changing (based on current execution), meaning that you need to always hook the register/watch any changes into register. You can't done this using Game Guardian, it is only for Memory editing not debugging. You need to use Memory Debugging app like GDB or Ghidra. Your ARM64 Assembly OPCode: ("cmp w21, #0xb0ff ...") will not affect anything since it is not being executed. Beside using Memory Debugger, you can also create seperate thread within the App (Like Mod Menu) to always constantly check for Register value. Although this is bad, constantly checking register means that it is resource extensive and the thread will likely killed by the OS. Yes, Android have auto-prevention that will shut threads/apps that resource extensive (Phantom processes). ---
Albeit, constantly checking Register value is bad in general and not doable in Game Guardian for reasons above. Better just changing any "mov w21, 0xB0FF" instruction into "mov w21, 0xB0CC".

[ @KezzaFr ]
---
You can use Magisk on LDPlayer, then use these LSPosed modules:
- HideMyAppList - Shamiko - XPrivacyLua - SudoHide After that, do the following on Game Guardian:
- Prevent Unload: level 1-4 - Hide Game Guardian from the Game: 1-4 - Bypass PTrace: Restore/Freeze ----
Goodluck.

[ @Koolie ]
---
You just need to save the earlier results into memory:
function increments(memo) gg.clearResults() memo_temp = {} second_memo = gg.getValues(memo) for k, v in ipairs(second_memo) do memo_temp[k] = { ['address'] = v.address, ['flags'] = v.flags, ['value'] = tonumber(v.value) + 1 } end gg.setValues(memo_temp) end gg.searchNumber('10', gg.TYPE_DWORD) memo = gg.getResults( gg.getResultsCount() ) --First Increment increments(memo) --Second Increment increments(memo) ... ---
*Fixed. I forgot something