What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

[Plugin] Giles Stash & Loot Rule Replacer

FYI, with this plugin, I have seen this bot pass right by TWO legendaries now. Heads up to everyone. I think they must have updated items so the bot doestn recognize them anymore
 
roflcopter said:
Does anyone have any loot rules that are updated to pick up the new legendaries?
Click to expand...

I have picked up a legendary (new one) with this plugin. I am pretty sure it is an issue with how DB is doing something and not the plugin itself.
 
Jackie1234 said:
my bot will kill a champ pack start running way points kill one mob run back to where it killed the champ pack loot 1 item then start running way points agian then stop run back loot a 2nd item then start running waypoints then turn around again and loot again. it does this every time stuff drops the bot is suppose to loot.
Click to expand...


this +1
edit: also saw it not loot 2 rares taht dropped at the end of a run where the next step was to TP to town. the bot started tping as soon as the elite died.. then i had to cancel the tp once, then it picked up 1 rare.. then it started tping again.. then i cancelled it again, then it looted the other rare.. it seems like once it loots 1 item, it goes back to what the profile says instead of looking for more loot on the ground
 
Last edited:
Thirdi said:
Nope, still skips stuff. Here is the bit of code from right as it skipped the items (was a doomcaster, I have it set to loot iLvl 62+ Weapons)
Click to expand...

Can you show more of the log? I can't see any of the new log lines anywhere in the bits you pasted - open it up to a much larger range. You should find lines like these (taken from my own logs);
Code: 
[19:58:34.434 D] [GilesStashReplacer 1.9.8] We want this item: pants_norm_base_flippy-2633, going to attempt a pickup [used Giles Filters]
[19:58:38.224 D] [GilesStashReplacer 1.9.8] Picked up (interacted with) item [pants_norm_base_flippy-2633]
[19:58:38.302 V] Blacklisting 818E002C for 00:09:59
[19:58:38.307 V] Blacklisting 818B002F for 00:09:59
[19:58:38.309 D] [WorldObjectHandler] Blacklisting a container [LootType2_Adventurer_C_Corpse_01-2655] because we never want to open it.
[19:58:38.309 V] Blacklisting 81950044 for 00:10:00
[19:58:38.311 V] Blacklisting 81AD001E for 00:09:59
[19:58:38.312 V] Blacklisting 81AE002B for 00:09:59
[19:58:38.320 D] [GilesStashReplacer 1.9.8] GSError: Probably trying to pick this item up twice in quick succession, blacklisting for 2 minutes anyway [pants_norm_base_flippy-2633]

(above you can see it failed to pickup pants - but if you look a bit higher up, you see it had already picked them up, it was just DB not keeping the loot list as up-to-date as it needs to be which is why I've had to code in safeties for it trying to loot the same item twice).
 
sojufiend2 said:
this +1
edit: also saw it not loot 2 rares taht dropped at the end of a run where the next step was to TP to town. the bot started tping as soon as the elite died.. then i had to cancel the tp once, then it picked up 1 rare.. then it started tping again.. then i cancelled it again, then it looted the other rare.. it seems like once it loots 1 item, it goes back to what the profile says instead of looking for more loot on the ground
Click to expand...

Sadly this is the way default DB works, and the way behavior trees in DB work - you get one "pulse" (so handle one thing), then DB "pulses" all the other parts of the behavior tree (so it can check for new monsters in range etc. etc.).

I did have it a bit faster before which worked well and forced DB to hold onto loot control for longer (kinda, not really but in layman's terms) - but since patch 1.04, DB got horribly sensitive to having lots of memory reads and became very buggy if you hit Diablo 3 memory frequently/in quick succession, so I've had to go back to the slow way, the way default DB works. I may try and find a workaround that gives us the best of both worlds, but for now - less crashing/memory read errors seemed the safer bet (perhaps a DB update will let me go back to the faster way again :)).
 
I didnt realize Giles made an update today. Im trying out th enew version now, hopefully it will pick legendaries/sets
 
GilesSmith said:
Sadly this is the way default DB works, and the way behavior trees in DB work - you get one "pulse" (so handle one thing), then DB "pulses" all the other parts of the behavior tree (so it can check for new monsters in range etc. etc.).

I did have it a bit faster before which worked well and forced DB to hold onto loot control for longer (kinda, not really but in layman's terms) - but since patch 1.04, DB got horribly sensitive to having lots of memory reads and became very buggy if you hit Diablo 3 memory frequently/in quick succession, so I've had to go back to the slow way, the way default DB works. I may try and find a workaround that gives us the best of both worlds, but for now - less crashing/memory read errors seemed the safer bet (perhaps a DB update will let me go back to the faster way again :)).
Click to expand...

Here is the full log from the run I have been doing on the bot that seems to miss the most items.
 

Attachments

GilesSmith said:
Sadly this is the way default DB works, and the way behavior trees in DB work - you get one "pulse" (so handle one thing), then DB "pulses" all the other parts of the behavior tree (so it can check for new monsters in range etc. etc.).

I did have it a bit faster before which worked well and forced DB to hold onto loot control for longer (kinda, not really but in layman's terms) - but since patch 1.04, DB got horribly sensitive to having lots of memory reads and became very buggy if you hit Diablo 3 memory frequently/in quick succession, so I've had to go back to the slow way, the way default DB works. I may try and find a workaround that gives us the best of both worlds, but for now - less crashing/memory read errors seemed the safer bet (perhaps a DB update will let me go back to the faster way again :)).
Click to expand...

so 1.9.7.3 causes crashes? i was just gonna try and use that version

edit: coz when i was using that version everything picked up all at once
 
Nope even with the new version its still missing a lot of items. One of the best examples is gems because they are so common. I would say the bot missed over one half of the gems that drop. I havent seen any legendaries drop, so I Cant comment there.
 
so most of the issues we are seeing right now are coming from DB's end not the plugins. This version of db has been the buggest ive seen yet. I really hope things get fixed soon. Im going to be playing GW2 by hand and i want to be able to have my bots go fully afkable.
 
latest version causes DB_Run: Command-line based Anti-Crash and Relogger to crash everytime starting
 
v1.9.9 uploaded:
-- A lot of further re-workings in item pickup handling code, should result in faster item pickups and less skipped items.
-- Better handling of gold pile pickups.
-- Minimum gold stack pile now an option within Stash Replacer config, default of 300 (World Object Handler 1.7+ no longer has this option).

A small changelog for what actually amounted to many more hours of debugging and work.

Please also update to the latest World Object Handler (1.7), which will no longer manage your gold pickups, since stash replacer now does.

NOTE: This is the last update from me on any of my plugins until September 3rd or so, ON HOLIDAY! :P
 
Last edited:
GilesSmith said:
That crash was actually caused by DemonBuddy messing up, but try and update to Stash Replacer 1.9.8, it may help. Always keep your plugins up-to-date - I have been known to update my plugins twice a day at times (and other times, once every week or two, depending if it needs lots of changes or not!).



Does +XP gear stats roll on high-end items? I thought you couldn't get +XP on ilvl 60+ gear? I might be wrong.



Hopefully this should just be a rare circumstance. Can you check the logs, and search for the string "GSError". You'll find lots and most of them won't actually be missed loot - I have tried to word the lines very carefully, and if you look a few lines above an error that says "tried to interact with an item twice", you should see new logs I added in 1.9.8 saying it was already picked up - but if you have a good look through the logs from the point the item dropped to the ground, to the point the bot blatantly missed the item and is no longer fighting but just walking past ignoring it, see if you can find any log-entries referring to that item and paste them up for me (along with the few lines above and below).



Where abouts in the Act 2 town-run does it get stuck? Can you describe the order of events to me? Also look in the log-file for the string "GSDebug" - you should find log entries from my plugin saying which part of the town-run routine it is on, so you can tell where it got stuck. Please give me detailed information or I really can't help!

Also yes lag does cause a LOT of issues - but nothing anyone can do about that really :P The way I cache all data before I start stashing/salvaging/selling items should reduce problems caused by lag though.
Click to expand...

yeah it doesn't roll on high end gear. max item level is 55 for +XP gear but there is still a ton of level 55 gear that drops on the act 1 inferno runs i do.
 
Latest version of the plugin makes the bot just run back and forth after picking up an item and looking for the next one. Anyone have a previous version they can upload?

edit: seems to be running better after restarting, hopefully doesn't do it again.

edit2: nah still doing it. seems to be an issue with picking up gold?
 
Last edited:
Valmere90 said:
Latest version of the plugin makes the bot just run back and forth after picking up an item. Anyone have a previous version they can upload?
Click to expand...

same it just paces back and forth.

Can anyone do a simple fix for this?? If not we will need an old version.
 
Last edited:
Code: 
[05:33:16.030 D] [GilesStashReplacer 1.9.9] We want this pile of 734gold, going to attempt a pickup [used Giles Filters]
[05:33:32.710 D] [GilesStashReplacer 1.9.9] GSError: Failed to reach item in time, blacklisting for 1m30s [took too long? GoldMedium-7308]
 
Just paces back and forth when picking up items. Anyone have the previous versions?
 
You must log in or register to reply here.
Back
Top