Jump to content

Search the Community

Showing results for tags 'Bug reports'.

  • Search By Tags

    Type tags separated by commas.
    For example, the common name of the game: PUBG, Free Fire, Rules of Survival, Critical Ops, Mobile Legends: Bang Bang, etc.
  • Search By Author

Content Type


Forums

  • GameGuardian
    • Requests
    • Help
    • Guides
    • Cheats
    • Video Tutorials
    • Unintended Effects
  • General
    • General Discussion
    • Introduce yourself (:
    • Announcements
    • Website suggestions/Bugs
  • Downloads Support
    • Apps
    • LUA scripts
  • Online Multiplayer Mods
    • Altering Online Games with Gameguardian
    • Download Mods
  • Other Hacks
    • Tutorials
    • Non-GameGuardian
  • Archive
    • Archived topics

Categories

  • Official Downloads
  • Virtual spaces (no root)
  • LUA scripts
    • Forward Assault
    • Free Fire
    • PUBG
    • Rules of Survival
    • Templates
    • Tools
  • Test applications
  • Other

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Device


Discord ID

Found 1 result

  1. Greetings. In this topic I will share my suggestions about possible ways to improve GG features as well as examples of unintended behaviour of the app. Will update the topic with new findings as soon as I prepare proper explanation for them. Pointer search It's a great feature which saves us time when need to find pointers to an address or a range of addresses. However, current implementation for searchimg a range of addresses (when we specify non-zero offset) seems not best for me. In current implementation search is performed from address - offset value to adrress value. Good way to illustrate this is to show a part of "pointer_scan.lua" script (released by Enyby) where search string is being constructed: local search = (address - offset)..'~'..address gg.searchNumber(search, gg.TYPE_DWORD) My suggestion is to change this feature's implementation a bit, so the search may be performed in 1 of 3 modes: from address - offset to address (current implementation); from address to address + offset; from address - offset to address + offset. One possible way is to add something like "multi-choice" containing two options with offset directions. Total combinations of possible user inputs will be equal to 4 in this case (3 "modes" that were described above and the option when nothing is selected, in this case offset value may be ignored). In my opinion, this will add more flexibility to the feature as well as making it more "understandable" for the user. Let me know, what do you think about it. Сheers.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.