Trasd

No, they are server-side and intentionally designed that way. Look for modded APKs of the games you are interested in.

I would say that varies by individual. You can start with the 6 month package and see if it's right for you.

Welcome!

Hi and welcome.

Welcome!

I became a moderator for technical reasons (I'm an Admin on the Dev site), not because of any connection with GG. I ended up here because GG is the best and only memory editor I use IMHO, and I'm working on a crusade to rid Android of (most) IAP before the OS is ruined (like rock and roll in the '70s). If I can help others learn to edit their games (you'll see I rarely give answers, but show people how to find this stuff themselves), IAP will become obsolete or less cost effective. These forums are a wonderful soapbox and I can help out with the site, too.

Actually, searching for a hex value should be easier as it takes less conversions, if entered as hex. Plus, with floating point data, the first 4 bytes don't change based on the mantissa and doubles can be found as well. It's a win-win thing. I've also seen where some of the "other" memory editors have found values GG couldn't; this is because they convert values to hex for at least one of their passes and the values were stored as floating point (Townsmen, in these forums is, I believe, one of them). Now, my disclaimer: This is all based on 30+ years PC programming experience (C/C++, Assembly) and 0 years (Java) programming for the Android, or anything else....

No, I haven't. At first I thought it was d2, then I figured the developer read this forum. I tried searching for another "official" forum, but that was a bust. Should I send the developer an official request?

Welcome, glad you found us!

I doubt it. Many developers use hack-proof tricks specifically to prevent memory editors from gaining access to their data. They're getting wise to us! It can still be done, but it is not easy. One simple trick some of them use is to store integer data as floating point. You would have to convert the number you are searching for into a base 10 decimal representation of the float and search for it that way. You have to convert all the numbers ahead of time or keep a floating point conversion system close at hand. Most use 0s for the mantissa, but the smart ones don't and simply round it or ignore it making this nearly impossible to find if you cannot do If everyone follows this link and Likes the post, maybe the GG developer will add this ability! Good luck.

Welcom CyrusX!

! TY

I thought this game looked interesting, so I decided to check it out. I like it! So of course, I began to try to increase certain stuff.... no luck. It usually doesn't take me very long with the tougher taking up to an hour or so, but 10 minutes is probably my average. Now, I consider this a challenge. They've obviously prepared for folks like us. So, I am asking for help (sometimes we all must eat humble pie), but the help I'd like, if someone figures this out, is just a nudge in the right direction. Most of the time I have more fun figuring out developers' anti-hacking schemes than actually playing the games. I know this game is not server-side as an internet connection is not required. I think, at this point, it may take reading the code, but as I've stated, I don't know Android programming nearly well enough yet. Thanks.

Welcome...

Hey Kevin, welcome!

Welcome!

Hello and welcome!

Welcome DJ.

There is nothing you can do on your device as the data is kept on a Gameloft server somewhere. This is called server-side and these are generally, not hackable. You'll have to spend some cash, find another game, or look for a modded apk. I have no way to verify this though, as it will not install on my tablet.

You need to look around the forums. You cannot get to any area that involves a paid subscription.

Memory editors, like GG, cannot work without root access, so no, you will not find an apk that will work on a non-rooted phone. Try doing a Google search for an android memory editor that will work without root access and I don't think you will find any available. But hey, I could be wrong...

I reread your original post and I don't think I quite understood what you were saying. But, now I do and unfortunately, I don't think I can help you. Someone with a bit more knowledge of GG's internals will have to tackle this one. But, like any normal, narcissistic, self-proclaimed know it all, I have a theory! Big shock there, right? My theory is as follows: GG found the number and reported the result as a 4-byte value, but it also found the same result as 1 and 2-byte values. I'm thinking your search size was set to automatic, not set manually. The reason it reported three results was because they all (1, 2, and 4-byte results) are contained within the same address space as the 4-byte result. This would assume GG does multiple passes when it is searching with size set to automatic and reports the final results as the largest data size available (4 bytes). Here's an example: Given the 4-byte value of 16 (0x00000010) is at address 0x1000FCD4 and you are searching for it: With the search size set to automatic, on the first pass, GG finds the 1-byte 16 at address 0x1000FCD7 and increments the 'number of results found' counter and logs the address. On the second pass GG finds a 2-byte 16 at address 0x1000FCD6 then logs and increments again. Finally, on the third pass, GG finds 16 as a 4-byte value at 0x1000FCD4 again logging and incrementing. Now, since the final 4-byte pass found an address result that includes the other addresses, it only displays the largest (byte-wise) result because you can edit the value, regardless. If you know the game and possible value range, it would be logical to assume you know enough not to overwrite the value's size maximum. Please remember, this is only a guess - a thought exercise for me - because I do not know enough about GG's internals or, androids memory management and structure. For example, does android use Big-Endian or Little-Endian, and will that make a difference to GG? I will learn this eventually as I learn more about android programming, but right now I'm just guessing. I'm probably also over-thinking this and there is a simpler, more logical answer. You can actually test this theory, though! Manually set your search size to each available choice and compare the different results. If you do, please post the results as this would go a long way in helping me understand GG. This, in turn, will enable me to help more people. Does anyone know the actual answer for this problem?

Welcome merc.

Did you Set Search Range to More Regions? I'd try that first.

If you search on automatic for size, the search results are shown by the size GG used to identify the number. If you try to change a 2 byte memory space to 4, you are making the app 2 bytes larger or writing over the next 2 byte memory space. There is no reason, in fact it would be very harmful, to change the byte size, that's why the other sizes are grayed out. If you want to find the same number, but at 4 bytes, you'll have to select 4 bytes when you initiate the search. If it doesn't find it at 4 bytes and shows it as 2, that's the number of bytes it is stored in. It is showing you the size for informational purposes only. I hope this makes sense!