Leaderboard

UPDATE!!! SPEED HACK, UNLIMITED RESOURCE AND TRAIN STRONGEST DRAGON!!! TRAIN SUPER MONGOL AND ONYX MASTER!!! Train Nuclear Ram... Train Bull Demon... Here we go... Train Kazuyo Bonus Troop Here we go... feature: samurai 1 hit KO. require: Gameguardian floating point converter for android Use this at your own risk

If any app makes accidentally reboot ROM then ROM is bugged. Any actions inside any app must not reboot device. Try change ROM.

It is very special and very bad realization - store key around value. Encrypted search can find any xor operation. Does not matter how and were stored key. For this games exist very simple check: Need two pair with value in memory and value in game. Like this: Calculate xor for each row: 9559 xor 453963 = 444444 9459 xor 453871 = 444444 We get same value then it mean used xor with this value. Now we can simple calculate need amount for set: 1234567 xor 444444 = 1318555 We set to memory 1318555 and get in game 1234567. If we see value 444444 near our value we can set to 0 it. number xor 0 = number After that you can set value in memory same as in game. But this happens only if game dev stupid enough. In most cases key stored in different place or written in code.

6:38 No converter need. Just simple search "12F;90;68" with selected Dword. First number automatically search as Float because we set it type to "F" - Float. 7:30 You can use offset calculator for faster goto to need values instead of count items in memory editor. In your case offset: 91AC6D20 - 91AC6CEC = 34 (13 items * 4 bytes for each item = 52 bytes in dec = 34 in hex) Just long tap on last founded item (DPS), select offset calculator, input offset 34 and press "goto". Now you stay on your "Damage".

Show logcat. https://gameguardian.net/forum/topic/7398-gathering-information-about-gg-errors/ Maybe you select memory access another from normal. if it true - select normal. Or remove GG and install from scratch without change any settings. All must work.

We know about that. False positive or specially added GG into virus list by game devs complains. GG from official source not contain any viruses.

Log files are special files created by the Android system and installed app. They contain important information that can help us identify the cause of the problem you’re experiencing and find out the best solution for you. For most cases you can record logcat inside GG: Start GG, Press "fix it" button, select "record logcat", wait for restart gg, reproduce issue, close gg, sent logcat file to me. If GG crash or you not able record logcat via GG, or GG not get root, you must use third-party apps for this: You need to record the logcat using any program that can record logcat during the issue. I mean record logcat! Simple, one moment save of the log is not enough! All programs require root on Android above 4.1! Therefore, if you do not have root, you can not even try, the log will not contain any useful information! Programs that do not fit exactly, because do not know how to write the log: aLogcat Syslog Ultimate logcat Ghost log aLogrec Spoiler Run. Press on record (Record). Go to the desired application. Reproduce issue / run desired action. Open the curtain, choose aLogrec. You remember the name of the file. Press Stop (Stop). You go for the stored path, find a file, send it to where it is necessary, preferably in the archive. CatLog Spoiler Run CatLog. Press the menu button. They choose the Record / Record. A dialog appears select the name of the log. You can rename a file or just click OK. After that you can press the home button. CatLog will continue to record a log in the background. Go to the desired application. Reproduce issue / run desired action. Switch to CatLog, press Menu, select Stop Recording / Stop record. This will be reported to the file name where the log is stored. The resulting log send to whom and where it is necessary. It is desirable in the archive. Logcat Extreme Spoiler You run the application. Click on the top left menu. Choose Floating Logcat. Confirm selection. You press the round record button. It should be red. Go to the desired application. Reproduce issue / run desired action. You press the record button again. It should be white. Close the floating window. Open the program again. Go to the section saved logs - Saved Logs. Choose the desired log. Choose to send as an attachment (Send as attachment). You choose what and how to send (or save a log file). Logcat recorder Spoiler Run. Put a tick in the recording (Recording). Go to the desired application. Reproduce issue / run desired action. Returns to the log recording application. You remember the name of the file. Recording a record check (Recording). You go for the stored path, find a file, send it to where it is necessary, preferably in the archive. LogViewer Spoiler Run. Press the menu button. They choose the Record / Record. Remember the name of the file. Click Record (recording). Go to the desired application. Reproduce issue / run desired action. Switch to log recording application, press Menu, select Stop Recording / Stop record. You go for the stored path, find a file, send it to where it is necessary, preferably in the archive. LogScript Spoiler Run. You press the record button in the upper right corner. Choose a place to save. Go to the desired application. Reproduce issue / run desired action. Switch to log recording application, press the button to stop the recording in the top right corner. You go for the stored path, find the file (file name logcat_data.txt), send it to where it is necessary, preferably in the archive. Logcat Recorder Spoiler No guide yet. Search in similar programs Market Search in similar programs Market Programs that do not fit exactly, because do not know how to write the log: aLogcat Syslog Ultimate logcat Ghost log Spoiler (If your device freezes or reboots) If the device hangs or is overloaded, it is necessary to remove a log on the computer by connecting the usb cable device. 1. Open a command prompt. 2. Run the following commands: Code c:\adb\adb.exe logcat > c:\adb\logcat.txt 3. Reproduce issue / run desired action. 4. After finishing playback, return to the console, press Ctrl + C, to stop recording. 5. You go for the stored path ( c:\adb\logcat.txt ), find a file, send it to where it is necessary, preferably in the archive. In such cases (hang or overload) is sometimes more useful to log the core system, through the same adb: 1. Open a command prompt. 2. Run the following commands: Code c:\adb\adb.exe shell su cat /proc/kmsg 3. Reproduce issue / run desired action. 4. Copy the contents of the console in a file (right-click on the title bar - change - mark - highlight the text with the mouse - press of Enter - insert into a text file), and refer the request at the place. Spoiler (via command line / terminal) If you are a lover hardcore command line, logcat, you can get there. Open the command line in any way: From a computer by connecting the device as usb: Start -> Run -> cmd -> cd /d c:\adb\ -> adb -d shell On the device, through any terminal, such as: Android terminal In the terminal, write: Code su logcat > /sdcard/somefile.txt /sdcard/somefile.txt Where is the path to the file which will log. Then we reproduce the error. After finishing playback, return to the terminal, press Ctrl + C, to stop recording. Log take away from the specified file to the archive pack and where to send. If you do not have root, then you can get logcat only through adb: From the computer, connecting the device to usb: (it is assumed that adb.exe you have in the folder c:\adb\) 1. Press Start 2. Choose Run... 3. cmd 4. cd /d c:\adb\ 5. adb -d logcat > c:\1.txt After reproducing the problem, close the console window and take the log from c:\1.txt - sending out who needs and where it is necessary.