[Plugin] Giles Item Pickup Stats

[GilesSmith]

This plugin is now defunct, old, and has been superseded!

Item Pickup Stats has now been integrated into my Stash Replacer plugin, and can now track items dropped, not only items picked up, plus can track potion drops, gem drops etc.

Please disable & delete the old Item Stats plugin (it may cause conflicts in future if you keep using it), and use Stash Replacer instead.

Downloads left attached to this post for reference only, or incase anyone finds a use for them in the future.

 

[cdmichaelb]

Nice

 

[gukku]

thanks for another nice plugin

 

[Radonic]

Thank you!!!!!!!!!!!!!!

 

[speculoos]

Ok now we want a DONATE button Gilles Please

 

[griovejas]

The boss of plugins strikes true again. Very useful.
Now let us optionally ignore all the low Magic Find/Gold Find drops in your Loot Rule Replacer plugin. Pretty please =]

 

[Radonic]

This plugin multiply the loots sometimes :S Dont know why, i had 4 ilvl 61, 2 ilvl 62, 1ilvl 63. The plugin told me i had 8,4,2 ....

 

[sojufiend]

lol this bot should be named gilesbuddy. thanks for the awesome plugin agian!

 

[GilesSmith]

This plugin multiply the loots sometimes :S Dont know why, i had 4 ilvl 61, 2 ilvl 62, 1ilvl 63. The plugin told me i had 8,4,2 ....

Could just be DemonBuddy item mis-reads at times. I've got it storing the DynamicID of items to detect if it's already been "looked at" before - was/is the most reliable way of doing it, without editing actual item pickup code - though it's still the first/initial version so I'll see if there's anything obvious I can do to stop that/anything I missed in the code!

Over the next few days though I may start looking at DB's internal item pickup stuff, see if there's any way I can tap into that and replace it with my own - if I can, then I'll move this plugin over to that, and do the stat counting at actual pickup stage, which would be more reliable - no risk of it ever looking at the same thing in your backpack twice and accidentally re-counting it! (atm it should be storing a blacklist of all dynamicid's of items in your backpack as it looks at them, so it doesn't count them twice)

 

[Radonic]

Could just be DemonBuddy item mis-reads at times. I've got it storing the DynamicID of items to detect if it's already been "looked at" before - was/is the most reliable way of doing it, without editing actual item pickup code - though it's still the first/initial version so I'll see if there's anything obvious I can do to stop that/anything I missed in the code!

Over the next few days though I may start looking at DB's internal item pickup stuff, see if there's any way I can tap into that and replace it with my own - if I can, then I'll move this plugin over to that, and do the stat counting at actual pickup stage, which would be more reliable - no risk of it ever looking at the same thing in your backpack twice and accidentally re-counting it! (atm it should be storing a blacklist of all dynamicid's of items in your backpack as it looks at them, so it doesn't count them twice)

sounds nice!

 

[sojufiend]

yep definitely counting them twice for me too

 

[griovejas]

Counting properly for me.

 

[sojufiend]

Counting properly for me.

wait till u run it for like 1.5 hrs

 

[Radonic]

Yeah its importent that i get correct counting for lets say, 24 hours. So i really can test zones and profile versions out so i dont just produce smooth profile, i want to produce profiles with high rare/h

 

[sojufiend]

Yeah its importent that i get correct counting for lets say, 24 hours. So i really can test zones and profile versions out so i dont just produce smooth profile, i want to produce profiles with high rare/h

hmm..? different zones have different drop rates? A1 rare/champion mobs should all be same monsterlevel and have same drop rates? or am i wrong

 

[Radonic]

hmm..? different zones have different drop rates? A1 rare/champion mobs should all be same monsterlevel and have same drop rates? or am i wrong

Yeah but some zones takes alot of time to run through and you might find 1 or 2 packs, its not enough to make up for the time you lost. What im thinking is that its also a nice thing to put up next to the original profile in the randomizer so you run 2 complete different profiles

 

[GilesSmith]

Yeah its importent that i get correct counting for lets say, 24 hours. So i really can test zones and profile versions out so i dont just produce smooth profile, i want to produce profiles with high rare/h

Ok, I'll see if I can think of a more robust way of doing it, will see if I can do something tonight! (not sure what the duplication issue is off-hand but I haven't had a chance to look at the code again since posting the first version!).

 

[griovejas]

wait till u run it for like 1.5 hrs

Still working fine for me, not sure what increases the chance of double count occuring.

 

[GilesSmith]

v0.2.1 uploaded:
-- Changed internal code to prevent stat-duplication when leaving and rejoining games.

^^ I found that the "DynamicId" field for items changes every time you leave and resume a game - so items currently in the backpack were being counted as newly picked up when you joined a new game. I hope this'll catch it - it clears the stored blacklist of items when you re-join a game, and adds anything in your backpack at time of game creation to the new blacklist.

While finding this, I did notice DynamicID's appear to be trying to store a value larger than they can hold - so they "overflow" and go into huge negatives. I suspect they should be doubles/floats internally in DemonBuddy, rather than an int. I wonder if this is the cause of random bug-outs of reading item stats? No idea, I don't really know how DemonBuddy works at the very core of reading Diablo 3's memory! We'll see if, when Apoc releases his item-fixes, DynamicID's have a different data-type and don't randomly roll into huge negatives!

 

[Radonic]

v0.2.1 uploaded:
-- Changed internal code to prevent stat-duplication when leaving and rejoining games.

^^ I found that the "DynamicId" field for items changes every time you leave and resume a game - so items currently in the backpack were being counted as newly picked up when you joined a new game. I hope this'll catch it - it clears the stored blacklist of items when you re-join a game, and adds anything in your backpack at time of game creation to the new blacklist.

While finding this, I did notice DynamicID's appear to be trying to store a value larger than they can hold - so they "overflow" and go into huge negatives. I suspect they should be doubles/floats internally in DemonBuddy, rather than an int. I wonder if this is the cause of random bug-outs of reading item stats? No idea, I don't really know how DemonBuddy works at the very core of reading Diablo 3's memory! We'll see if, when Apoc releases his item-fixes, DynamicID's have a different data-type and don't randomly roll into huge negatives!

Ill try it out! Thanks!