giles glitch?

I was watching my boot periodically through out the day and I have seen him skip over some loot. ilvl 62 ring and ilvl 62 bracers. After they dropped he just kept running, I gave him about 20 seconds to go back but he didnt.

using db .259
giles 6.2
radsatom

 

The trinity record tells me that it rarely 'skips' loot, but Giles has advised that it could be because DB misread items. i.e. rare lvl63 dropped > rare lvl63 picked up provided you picks up all the rare 63. Other members have reported the same issue too. I'm not saying it is Giles' fault but I do believe the system is missing loot rarely atm. If the system misread item dropped, it should still pick them up right?

I don't monitor my boot all the time. The only instance I can prove is when I saw it missed a tome. Only when I dragged it to around 14-20 yard, it is able to pick it up.

Running:
db.259
giles 1.6
radsprofilemanager

In older version 1.4.6.1 with old DB, it never missed a single loot. I still use the old version sometimes becoz it is more stable IMO. I know somebody already did but if one day I missed a legendary, I will switch back lol.

 

the bot is missing loot, but its like 1% (i have this number from looking at my log files). imo this number is so insignificant that there is no need to look for a reason and any solution

and this "error" rate is consistent with all build and plugins. i still have some folders with 242 and 1.4. logs and its the same 1%

 

Yeah I agree it is pretty insignificant. But in 1.4.6.1 I have never noticed a single skip.

 

It'll happen in every build - regardless. It's not actually anything in the code anywhere - it's when DB happens to cache bad actor data from D3, and as far as I can tell - it's actually D3 at fault. It won't affect you "playing manually", but anything relying on reading specific memory addresses and memory flags will have these quirks.

I'm positive that this is what also causes the bot to sometimes "ignore" a monster before it's been killed - and refuses to acknowledge it's there, until you stop and restart DB (which refreshes everything).

I consider it an acceptable loss, and for me I think it's less than 1% on average - 1% I'm more than prepared to live with for 100% time not playing manually (and multiple accounts at the same time)

 

Well fair enough. Thanks again for creating such wonderful plugin! I think most of us just want to contribute some feedbacks