deathlimited
New Member
- Joined
- Feb 1, 2012
- Messages
- 249
- Reaction score
- 0
same here i made 200$ from a skorn and bout 100m in 2 days yet i still saw it miss loot.
Mine is not skipping any items.
Mine has plans from 4 prop to 6 prop to legendary in storage.
Mine has multiple legendaries from 54 to 63 in storage.
Mine made $400 over the three day weekend, most of it in high end legendary or set items.
Mine picks up and sales/salvages everything correctly.
What am I doing right that you are doing wrong?
Act 3 champ farm.
Radsmanager
Giles combat and loots.
Plenty of people are using an identical profile/plugin setup and still experience the bot ignoring loot.
Are some skips due to avoidance issues caused by interaction between combat replacer and stash replacer? yes. are others unavoidable? yes.
Giles himself will tell you that DB misreads memory and will skip items. If you haven't experienced it, it's pure luck.
Not to mention the fact that finding that many quality legendaries in that span of time is ridiculously lucky as well.
edit* On the bright side, Giles new top secret project seems to greatly improve loot collection, so you all have something to look forward to!!
There is more than just avoidance or item misread. It was like the bot was following another command after killing the elite, usually attacking a few other mobs. But then the loot func seems to be 'turned off' until it triggers by another 'event'. I tried manually walk the bot back, it stills ignore the 63 rares and gold piles and runs to its dedicated direction. So I believe there could be a minor bug in the combat coding to let it ignore looting until it resets to 'normal'.
I'm using giles combat/worldobject/stash and profilemanager with Act 1 Cham profile. All standard.
Try Giles Trinity,
It actually has the capability of disabling combat to loot (in combat looting, really), which will result in you missing many less items.
Is this something that's on by default? I didn't see any options for it in the config.
My Barb just skipped a legendary too...
...hope the devs fix this shit soon!
Dose the latest DB 227 fix this issue????