Leaderboard

A single search is faster than group search. But editing those in one search is dangerous which could cause game crashing. So function xqmnb comes to work to make a checking for those result. If they meet the requirements you set , they will be edited else won't.

Count used memory by target process with group by region type local t = gg.getRangesList() local out = {} for i, v in ipairs(t) do local prev = out[v.state] if prev == nil then prev = 0 end out[v.state] = prev + (v['end'] - v.start) end print(out)

Yes sorry this is not very clear but I can't edit it anymore so I cannot change it now. These kind of values can be found with GG, but it is hard. For example, recoil may most likely be in a structure, most likely with firerate, maybe with max ammos or even current ammos around it. You might find it by searching for your current ammos, then browsing around in memory (maybe with some pointers). Wallhacks can be done quite easily in fact. In most games you'll find a "flag" value, toogling only when you touch a wall. If you find it you can just freeze it to its unto ogled state, so it will never tell the game you touched a wall, and you'll be able to wallhacks. Anyways, you can find tutorials on internet for wallhacks using memory editors, "cheat the game" does it on PC with cheat engine, but it will give you a good taste of how it's done. The main thing to remember is that related values are related in memory, because programmers do their games a logical way, with structures. When it gets too complicated just with GG, you can deassemble the game to get the full code, understand it and mod it, but it can be a long and hard thing to do.

my samsung galaxy light isnt vurnalable tothe exploits