Memory Tool menu

User Tag List

Thread: Memory Tool

Results 1 to 1 of 1
  1. #1
    Cosmo777's Avatar Active Member CoreCoins Purchaser
    Reputation
    36
    Join Date
    Oct 2016
    Posts
    25
    Thanks G/R
    1/19
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Memory Tool

    Hello,

    I have been using a tool I made to look up data structures recently and wanted to share it with the community. If you find it useful then great if not then thats ok too.

    You may required VS 2017 to compile it.

    I would advise building it in release mode as the performance is much better. Atm memory is an issue that I am looking at trying to resolve... with very large searched it can take a lot of ram, my pc has 64gbs and it has hit 30gbs on very large operations.

    I would also caution that going further than 2 levels deep can take a very long time.

    Basically you can add multiple memory addresses in different tabs, scan for a value that is a child of that address, specifying how how pointer levels deep to scan.

    Then once you have scanned a few addresses and found values you can hit match.

    Match will iterate through each of the open tabs and look for values that were a match for what you were looking for, then it will scan the next tab and do the same only keeping values if the match was correct in both tabs. This will repeat for each of the tabs.

    Example: I want to find if an item is corrupted. I suspect this is located from the base component of a poe entity.

    1. I find the address of 4 base components from poe entities 2 of which are corrupted and 2 which are not.
    2. I add 4 tabs to the spider and set the address to the address of each of the base component addresses.
    3. I set the value to 0 for the non corrupted tabs and 1 for the corrupted ones, I also set the data type to byte.
    4. I hit search on each of the tabs.
    5. I hit the find matches, which gives me 2 pointer trails, one trail is 216 the other is 256-416. So 216 is a direct offset from the base component, 256-416 is a pointer and then a direct offset from that pointer.
    6. I know that for all of those items 216 and (256-416) matched the 0 or 1 respectively for what i searched for and I am confident that is hhow I find the corrupted value in memory. (in this case 256-416 was also wrong as it wasn't correct for unqiues)
    7. I have my offset or pointer trail offset for what I was looking for pretty easily.

    There is also a samples directory in the repo, can can load those to see results how matching works.

    GitHub - cosmo777/DataSpider: Tool for crawling data structures

    Thanks,
    Cosmo

    Memory Tool
  2. Thanks Treasure_Box, noneyatemp, dlr5668, TehCheat, dodger, Stridemann, GameHelper (7 members gave Thanks to Cosmo777 for this useful post)

Similar Threads

  1. Replies: 2
    Last Post: 01-29-2011, 05:42 PM
  2. [Tool] MemoryTools - tool for watch memory, short disassemble, hex and search offsets
    By dunmcl in forum World of Warcraft Bots and Programs
    Replies: 0
    Last Post: 12-11-2010, 03:20 AM
  3. [PC] Gothian's Memory Tool (Contrib Version)
    By Gothian in forum World of Warcraft Bots and Programs
    Replies: 19
    Last Post: 08-22-2008, 11:41 AM
  4. [PC] Gothian's Memory Tool (Alpha 0.1.164)
    By Gothian in forum WoW Memory Editing
    Replies: 22
    Last Post: 12-19-2007, 09:58 PM
All times are GMT -5. The time now is 06:41 AM. Powered by vBulletin® Version 4.2.3
Copyright © 2024 vBulletin Solutions, Inc. All rights reserved. User Alert System provided by Advanced User Tagging (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
Digital Point modules: Sphinx-based search