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

[Plugin] Giles Stash & Loot Rule Replacer

Giles is it possible to have an option NOT to auto save all legendary items?
basically if they are lv 59+ just salvage them if they are crap (mats worth alot) under that just sell.
i just get my stash full of crap legendary items :p frustrating

I think there needs to be some "legendary action list" or something. I would still rather have some legendaries stashed (so default action for the list should still be "stash if not said otherwise), just to make sure I don't miss out on the expensive ones (and also it's not there are really that many of them), but the really always bad ones (like "ivory tower", I got like 5 of those already) should be disposed off accordingly (chance for a brimstone -> salvage, no brimstone -> sell). I could possibly try to help with making the list if Giles is interested to incorporate it into the "scoring process".
 
just catch the bot in infinite loop trying to place an item in the stash , last version of Db and the plugin , it was placing enchantress token in the stash , then placing an unique helm on the token place , then placing the token in the helm place , and this for good 10 mins , and there was plently of space on the same tab
 
I also use GilesWorldObjects and GilesEquipper and have DisableLootRules=False on GilesWorldObjects and on GilesStashReplacer to use my custom loot rules to pick up all magic+ items for my level up bot. With those settings, for example, sometimes my early act 1 quest if backpack is full, it doesn't always go to the miner for vending. Instead it goes to the west vendor which is blocked on early quests. So I'm assuming it used DB's townrun because I didn't see your message on the log when it detects backpack is full. Sometimes I see your backpack full message and sometimes I don't, which is why I'm confused.

Hi, this is a sign that the plugin is not being loaded properly - are you waiting for the plugins to be fully loaded before trying to click "Start", and always checking they are ticked in the plugins tab first? (sometimes plugins uncheck themselves in DB :(). Are you using any other plugins that might be incompatible (can you list all your plugins)? Are you using any form of relauncher, relogger, command-line tool, or batch file to start D3 and DemonBuddy? Are you launching DB while D3 is still on the login screen (this sometimes messes Db up with plugins - always launch Db after you reach the character screen where you can change quest/resume game etc.). If you're ever getting it run to the west vendor, or not get the message from the stash replacer about doing a town-run, then it's definitely a sign of something going wrong with the install/DemonBuddy. Failing all-else, a freshly installed DemonBuddy in a new, clean, empty folder can fix oddities.

I think there needs to be some "legendary action list" or something. I would still rather have some legendaries stashed (so default action for the list should still be "stash if not said otherwise), just to make sure I don't miss out on the expensive ones (and also it's not there are really that many of them), but the really always bad ones (like "ivory tower", I got like 5 of those already) should be disposed off accordingly (chance for a brimstone -> salvage, no brimstone -> sell). I could possibly try to help with making the list if Giles is interested to incorporate it into the "scoring process".

I'd definitely appreciate such a list. If somebody can rule out all the "definites" - the legendaries that drop but are ALWAYS worthless (or worth less than 100k anyway) no matter what... etc., I'd like to incorporate that (those junk legendaries annoy me too :P). I think it'll have to be a specific blacklist, so when unknown legendaries come along (eg with a Diablo patch), they are auto-kept.

just catch the bot in infinite loop trying to place an item in the stash , last version of Db and the plugin , it was placing enchantress token in the stash , then placing an unique helm on the token place , then placing the token in the helm place , and this for good 10 mins , and there was plently of space on the same tab

Can you give me a paste/upload of the DemonBuddy log from the point where the town-run started (eg the start of the StashReplacer message saying "Inventory may be full, now doing a town-run" or whatever) down to where it got stuck (and paste a chunk of the "stuck loop"). It does sometimes feel like however much I do, DemonBuddy is determined to find a new way to screw up and get stuck in infinite loops :)

how do i turn off gold pickup? running goblin hunter and its kinda killin my goblin findin :(

Use world object handler and set the minimum gold pickup pile to like 2k in the world object handler config.
 
v1.9.7 uploaded:
-- Added a system to try and prevent any possibility of infinite stash loops caused by DemonBuddy item mis-reads;
If it detects it is trying to stash the same item more than once, it will forcefully treat that item as a 2-square item in the stash process.
If it detects the same item being stashed more than six times, it will re-map the stash treating as many items as possible as 2-square items to find very clear open spaces.
If it still detects the same thing being stashed more than 15 times, it will emergency stop the bot to prevent getting stuck.

Hopefully this will stop anyone ever getting stuck in an infinite stash loop again, no matter what's happening memory-read or item-mis-read wise :P (though if the item mis-reading is happening that bad, chances are it's trying to stash the wrong things anyway! All we can do for THAT is keep waiting on DB improvements!).
 
Giles, the newest version keeps going back to town unnecessarily wasting a lot of time trying to port out near range mobs, etc. If there's multiple drops of the same object close together, it will blacklist the object and force a town run.

[GilesStashReplacer 1.9.7] GSError: Tried to interact with an item too many times in a row, blacklisting and attempting a forced town-run [CorePickup-3 healthPotion_Mythic-15213]
[GilesStashReplacer 1.9.7] GSError: Tried to interact with an item too many times in a row, blacklisting and attempting a forced town-run [CorePickup-3 Axe_norm_base_flippy_06-12225]
[GilesStashReplacer 1.9.7] GSError: Tried to interact with an item too many times in a row, blacklisting and attempting a forced town-run [CorePickup-3 Lore_Book_Flippy-7293]

Edit: Seems to be all normal items too:
[GilesStashReplacer 1.9.7] GSError: Tried to interact with an item too many times in a row, blacklisting and attempting a forced town-run [CorePickup-3 Quiver_norm_base_flippy_01-19161]
 
Last edited:
Giles, the newest version keeps going back to town unnecessarily wasting a lot of time trying to port out near range mobs, etc. If there's multiple drops of the same object close together, it will blacklist the object and force a town run.
[GilesStashReplacer 1.9.7] GSError: Tried to interact with an item too many times in a row, blacklisting and attempting a forced town-run [CorePickup-3 healthPotion_Mythic-15213]
[GilesStashReplacer 1.9.7] GSError: Tried to interact with an item too many times in a row, blacklisting and attempting a forced town-run [CorePickup-3 Axe_norm_base_flippy_06-12225]
[GilesStashReplacer 1.9.7] GSError: Tried to interact with an item too many times in a row, blacklisting and attempting a forced town-run [CorePickup-3 Lore_Book_Flippy-7293]
Edit: Seems to be all normal items too:
[GilesStashReplacer 1.9.7] GSError: Tried to interact with an item too many times in a row, blacklisting and attempting a forced town-run [CorePickup-3 Quiver_norm_base_flippy_01-19161]

That's nothing new with 1.9.7 - that's generally a sign that something is going wrong with DB (on occassion DemonBuddy seems to screw up badly with items until you restart it, or sometimes even reinstall it). Those "interaction fails" will happen now and then by themselves, but if you are getting LOTS, it's a sign that there's a problem with DB. Simply restarting DB might fix it, updating plugins, removing old/dodgy plugins, or a fresh install of DB (hell even a PC reboot/D3 client restart). Let me know whether or not any of those things clear them up, I'd like to know!
 
That's nothing new with 1.9.7 - that's generally a sign that something is going wrong with DB (on occassion DemonBuddy seems to screw up badly with items until you restart it, or sometimes even reinstall it). Those "interaction fails" will happen now and then by themselves, but if you are getting LOTS, it's a sign that there's a problem with DB. Simply restarting DB might fix it, updating plugins, removing old/dodgy plugins, or a fresh install of DB (hell even a PC reboot/D3 client restart). Let me know whether or not any of those things clear them up, I'd like to know!

Certainly, will try doing the whole reinstall, etc. If it helps, I upgraded from v1.9.5.1 (skipped over 1.9.6) and there weren't any issues that version. As for the frequency, it was happening roughly every 3 minute or so and on more than one bot.
 
The latest version is spitting out these errors randomly:
Code:
[09:35:33.433 V] Using power Walk clickPos:<1881.395, 1100.714, 170.9336> worldDynamicId:1999568897 targetACDGuid:-1
[09:35:33.683 D] [GilesStashReplacer 1.9.7] Blacklisting item: HealthGlobe_02-3599 because it is a health-globe and shouldn't have a loot-attempt.
[09:35:33.683 V] Blacklisting 85840033 for 00:09:50
[09:35:33.851 D] [GilesStashReplacer 1.9.7] Blacklisting item: mightyWeapon_2H_norm_base_flippy_04-3605 because it is a white weapon.
[09:35:33.851 V] Blacklisting 858A002A for 00:09:50
[09:35:33.886 V] Blacklisting 8590006E for 00:09:59
[09:35:33.989 V] Blacklisting 85930009 for 00:09:59
[09:35:34.080 D] [GilesStashReplacer 1.9.7] Blacklisting item: Helm_norm_base_flippy-3617 because it is a white armor/offhand.
[09:35:34.080 V] Blacklisting 85960080 for 00:09:50
[09:35:34.090 D] System.NullReferenceException: Object reference not set to an instance of an object.
   at GilesStashReplacer.GilesStashReplacer.GilesPickupOverlord(Object ret)
   at Zeta.TreeSharp.Decorator.CanRun(Object context)
   at Zeta.TreeSharp.Decorator..MoveNext()
   at (Object )
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector..MoveNext()
   at (Object )
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector..MoveNext()
   at (Object )
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.Decorator..MoveNext()
   at (Object )
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector..MoveNext()
   at (Object )
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.Common.HookExecutor.Run(Object context)
   at Zeta.TreeSharp.Action.RunAction(Object context)
   at Zeta.TreeSharp.Action..MoveNext()
   at (Object )
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector..MoveNext()
   at (Object )
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.CommonBot.BotMain.()
[09:35:34.371 D] [GilesStashReplacer 1.9.7] Blacklisting item: Amethyst_07-3624 because it is not a gem we want.
[09:35:34.371 V] Blacklisting 859D0033 for 00:09:50
[09:35:34.395 V] Using power Walk clickPos:<1877.78, 1094.709, 171.9564> worldDynamicId:1999568897 targetACDGuid:-1

Seems to be working just fine apart from a minor hickup when it errors. I've tried clearing the compiled assemblies folder, as well.
 
Last edited:
Any chance of a process backpack button next to the test backpack scores button, this would process everything in you stash on demand.

G
 
Any chance of a process backpack button next to the test backpack scores button, this would process everything in you stash on demand.

G

You can do a workaround version of this with a profile.

something like:

Code:
<Profile>
  <Name>Empty Backpack</Name>
  <GameParams quest="87700" step="50" act="A1" difficulty="Normal" resumeFromSave="False" isPrivate="True" numGames="-1"  />
 <Order>
	    <!-- Force a Town run  -->
	<ForceRepair questId="1" minFreeBagSlots="60" />
	
	
  <LeaveGame reason="done" />
  </Order>
  <KillMonsters>False</KillMonsters>
  <PickupLoot>False</PickupLoot>
 </Profile>

Have GilesStash running and DBEnhancements, sand save this code somewhere as "EmptyBag.xml" it'll log in and force a Town Run, and then sit there looping the Town run till you stop it. Not elegant, but it'll empty your bags.
 
I know that in the directions you do not mention chest.
Is there any way for this to loot chest or is there someother plugin that will do it.
I have changed everything I can and he will smash barrels and loot corpses (neither I want) but it works but he will walk right by a chest and never touch them.

Any help or ideas are very welcome
 
Last edited:
hi, i always get this
[22:00:11.694 N] [GilesStashReplacer 1.9.7] GSError: Tried to interact with an item too many times in a row, blacklisting and attempting a forced town-run [CorePickup-3 healthPotion_Mythic-549]
is it normal?because sometimes its happend every run
 
hi, i always get this
[22:00:11.694 N] [GilesStashReplacer 1.9.7] GSError: Tried to interact with an item too many times in a row, blacklisting and attempting a forced town-run [CorePickup-3 healthPotion_Mythic-549]
is it normal?because sometimes its happend every run
It's nothing to worry about unless you actually notice problems happening - it's a safety feature. Generally the item was already picked up, but the plugin looped so fast that it's trying to pick the item up twice in a row, so it generates that error (the error is a safety to stop Db crashing out or doing anything horrible like standing on the spot doing nothing trying to pick up an item that is already gone).

I know that in the directions you do not mention chest.
Is there any way for this to loot chest or is there someother plugin that will do it.
I have changed everything I can and he will smash barrels and loot corpses (neither I want) but it works but he will walk right by a chest and never touch them.
Any help or ideas are very welcome

The new DB disables opening of chests, but gives people no simple GUY setting to enable it again (clever move, right!?). However, try world object handler plugin (see link in sig), you can set a range for it to open chests, and this will over-ride the new DB setting that disable chest looting etc. and allow you to pick different ranges for different types of objects, too.

The latest version is spitting out these errors randomly:

Yeah this is DB again, I don't think they're anything to worry about. It seems to be one of the few memory mis-reads I haven't (yet) found a reliable way to catch to give a "friendlier" error, mainly because I haven't seen that one much myself, I don't think it's anything to worry about unless it's coming up every minute or two.
 
Giles do you think that you cold implement a log that shows also the number of affixes, or an average of affixes found on items? ;)
 
Giles do you think that you cold implement a log that shows also the number of affixes, or an average of affixes found on items? ;)

Urrr, probably, you'll have to tell me what for though, I don't like doing things blindly! And do you just mean a sort of global aggregate stat? And on what, ALL items picked up (actually bit hard since we don't see that til the identify in a town-run)... all items stashed? Sold/salvaged? Although actually it's going to be unreliable, as we still can't read a number of the weirder possible affixes, like if it increases damage of a specific class skill and all those sorts of things, and a few of the more "Normal" but generally ignored stats still aren't readable... so actually, now I think about it, that info would be pretty useless if you couldn't make it 100% reliable :P
 
Back
Top