Memory reading : export item tooltips

[extern]

Hi guys,

First of all, I would like to thank all members who share for very interesting stuff here.
Here is a tool that can helps you to export d3 items stats to XML or SQLite.
It's not a great deal, just a tooltip-based-pattern-matching-memory-reading tool, but I thought it may be interesting for few of us (or not?).

https://github.com/d3dev/d3_tooltips
Youtube demo : d3 tooltips - YouTube

My two cents

[Vengfull]

Will be quite usefull for something im working on at the moment. Cheers Extern +Rep

[sandcho]

Very useful tool, only sockets are missing.

[extern]

Very useful tool, only sockets are missing.

I couldn't agree more
I have planned to add sockets, but I am wondering if I should'nt merge them. (ie there is one tooltip per socket ; with a maximum socket number up to 3).

By the way, I will take a closer look to "enchantment" and "flavor", because I did not figured out what the point with these fields.
And I do not care of the "comparator with equiped items" fields.

[sandcho]

only one thing is needed the amount of socket's nothing more and one more thing - export all items from character with one button

[Venk2012]

...and one more thing - export all items from character with one button

Yes please!

[extern]

Guys,

This program is designed to export what the mouse is pointing at, and the mouse is unlikely to be pointing at all items at a time.
Thus it can not export all items from a character with one button.

IMHO, the best way to do so is to inject code and deal with objectmanager / getint / getfloat / etc, but updating offsets is very painfull from a developer point of view. (That's why I choose memory scanning)

[sandcho]

Guys,

This program is designed to export what the mouse is pointing at, and the mouse is unlikely to be pointing at all items at a time.

i can live with that thanks again for the tool a socket version will be much appreciated

[extern]

v0.2 is out, with new ToolTips support like sockets. Available on github.

[sandcho]

Thank you !

[AGPS]

great job!

[infotech1]

Guys,

IMHO, the best way to do so is to inject code and deal with objectmanager / getint / getfloat / etc, but updating offsets is very painfull from a developer point of view. (That's why I choose memory scanning)

Reading memory without offsets?
Also no need to inject to itterate objman, can check each item if its equipped etc and grab stats just mem reading.

[extern]

You'r right, no need to inject to iterate objman, I reply a bit too fast. (Some people say that injected code allow to read memory a bit faster than using ReadProcessMemory).

But we need statics offsets to do so, and thus you found that objman is at 0x1543B9C on 1.0.4. (by the way, thank you for sharing that).
To get rid of statics offsets, I decided to scan the memory searching for patterns (big structure begining with a 8 bytes hash), and then grab values with relatives offsets.
I agree that it's not user friendly, but it's patch-agnostic. (until they path tooltip structure itself).
I briefly explain that here : https://github.com/d3dev/d3_tooltips/wiki/How-it-works

Thank you for rectify my words.

[sunblood]

Nice tool!
I'm interested in making something that would be useful running real-time alongside the player. I'd love to see a quick output for this tool that could, say, copy the stats to the clipboard in an easily splittable way, or writing to a temp file that could be read by another program. Is that something you could do in the future?

[Honski]

could you go into more detail for reading the random stats of the item? stuff like +57 int etc

so far i've simply used static offsets relative to the d3.exe that i found with cheatengine, but it doesn't seem to be 100% accurate and the memory region is also used for other things if no tooltip is displayed.
i've tried displaying the value of all ui elements that are listed in the source code, but none contained the things i wanted. durability etc worked fine.