Leaderboard

Hello, today summoners war begin to detect GG, any staff is aware about this? This is the message you will receive : "Please close any apps that might negatively affect the game"

Oke, i understand. I advice you to search a other value, a stable one that does not require to be searched every new match, then you can make a proper group search, for that try to search the value in the lobby and modify it and see if it works in the match. Try to search the values in qword instead of float or dword, there is always a chance that qword will narrow the search results, but for do that you must know which values are doing the hack. use it as a filter. As my previous quiestion i was asking if the values your searching are all the same? [added 3 minutes later] Because if so, you need to narrow down and while your in the match find the specific values that are doing the hacks and go to its adresses and copy a fuew values and search it again in the next matches, it will narrow your resuls and make it more efficient to add it in to a script. you know what i mean? If you not follow i can make a video of it.

bro... either u checked too much values for "group search" or the values you chose to make "group search" they are far from base value - thats why group size increased solution - first, just copy base value search it... if the results very less, directly edit them (u might face crash, but its worth trying) sec. - run couple match and restart game... check static values around your base value... then group search it... (dont choose too much values) Also choose option - "Add type" & "group size" & select "ordered" hope its help

x = --value you want gg.searchNumber(x,gg.TYPE_DWORD) local t1 = gg.getResults(100) for i=1, 100 do a = { address = t1[1].address + offset , address = t1[1].address + offset2, -- do until you satisfied } end gg.addListItems(a) This can save address of different offset. (MAYBE?)

This can not be formalized. The application can not read minds. Therefore, you can not do this automatically. Learn programming, API and write manually. All good things are always done by hand.

A script entry can not record all of your actions in a portable form. Everything that can not be written in a general form is not recorded. You can not record the offset, because it should be written in a general form, and so you can not do it. You can not say - apply an offset to the 3 result of the search, because tomorrow it will not be the third search result. Even on your device or on another device. If you save the memory address in the script, the script will become useless even after the game is restarted. In general, writing a script is not intended to make a ready script, it is impossible by definition, but to provide some workpiece, for later manual editing. Well, or for writing VERY simple scripts. Something like found a group search and replaced / frozen everything. Not more difficult than this. _______________________________________________ added 1 minute later And what you are talking about (shifting) requires a fine and precise work. Cycles, a clear understanding of what is happening, and why.

Okey. Let go with example. We have class Player with field "gold". Field stored at 0x140 from object begin. Then if object have pointer = 0x123000, then gold have address = 0x123140. Pointer + offset. Now we have one object of player. It created with operator "new" of C. This operator create new or use exists anonymous memory region and allocate on it memory. Because of ALSR it can be in any place of memory. Because of operator "new" it do not have any concrete name or have common name like "malloc". Pointer to this memory can be saved in stack of main loop or in .bss or .data segment of memory. This too present some offset from start of memory region. 0x140 not present in memory in most cases. It is hard-coded in assembler operands. Like "mov r0, [r3, 0x140]" We can find value of gold in memory. Okey. We find it in some way. It is have address 0x4567890. Now we need find pointer but how? We do not know need offset in Player object. If we known it we can calculate 0x4567890 - 0x140 and search this value in memory, but we do not know it. And in next build of game this offset can be different. And this I only show general problem. Let go deeper. Assembler. In arm assembler all offset calculated from current point. In x86 we can use on base for all offsets. Arm. load string look like: get pc register + some offset constant - result put in register. It will pointer to string. Because offset rely on PC register - then offset for one string in different places is different. Okey. X86. Load string look like: get segment address + some offset constant - result put in constant. it will be pointer of string. Because offset rely to segment address (they stay same in most cases) - then offset to one string in different places will be same. Okey. Return to Arm. Arm have limitations to load big numbers in one instructions. If offset too big it can not be loaded with one instructions. It can be loaded with two instructions: 1. Or as load low part + load high part - data stored in instructions. 2. Or as load small offset to number placed near (usually after function code) and second command used this loaded number as relative offset. both of them rely to PC register. Both of them rely to position of current command. Nice things? Tell me what you mean by offset in this case and how we can found it.

Because who is talking do not know what is that. Everyone mean it different. May knowledge say me: impossible. And word offset can mean too many: offset between values, offset from pointer, offset in structure and so on. I do not see any case who worked in general terms with pointers. May be I do not understand something. Explain to me of that happens. You are not logged in or you do not have permission to access this page. This could be due to one of several reasons: