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

[Plugin] Giles Stash & Loot Rule Replacer

Hey Giles! Still safe to use rules from #337?? (or they miss something with new DB) i need em to use with Stove plugin :D

I think they need updating for newer versions of DemonBuddy, as the way the quality stat is done and a few other things changed a bit in the .XML format. Should be fairly easy to update, if you want to do it and upload the changes I'm sure other users of Stove's would appreciate it!

A little suggestion regarding shields.
Shields with close to max block chance can actually sell for a bit even if they roll half decent stats (i63 shields). Saw my bot trying to sell a shield worth at least 500k easy and stopped it in time!

Does anyone with a bit of experience in shields know some values for the "total block chance %" I can work on? Eg what is considered the "limit" where anything above it should give a huge score bonus to almost guarantee a keep (unless it has like no other stats whatsoever)? What's a sort of "average" block chance % where maybe a bit of score bonus... and is there a limit where anything below that is either never worth keeping, or deserves a huge negative to score (so only absolutely uber stats in other ways could overcome the low block chance)?

I ask because you can't actually search the AH for total block %, so I'm struggling to get good ideas for values in my head - hopefully people with experience of shields can help out here!
 
Last edited:
Possible to differentiate on BS plans? If possible, I would like to be able to disable 4 stat plans, and only pickup 5 stats or better plus of course legendary plans.
 
Possible to differentiate on BS plans? If possible, I would like to be able to disable 4 stat plans, and only pickup 5 stats or better plus of course legendary plans.

At the moment, the only way I can find to disable the 4 stat plans is by their client-based name (which is also language dependent), and I want the plugin to be "multi-language-friendly". It's easier (and more reliable) to just let it stash ALL items classified as a plan/design type item - they stack so you can ignore the 4 or 5 spaces in your stash that build up with the "junk" designs - I put mine in the lowest-far-right corner of page 3 and surrounded the with gems, so good designs/plans go elsewhere and are easy to see :P
 
Giles, ever thought of integrating an ilvl63 UNID feature built-in to this? I know there's some laying around but would be great to keep everything in one plugin. :)

Probably an extra window with checkboxes of "keep all" or which i63 items to keep UNID.
........
 
Yes ;) (I plan to do it, but I'm just a one-man-band with a lot of things I work on with all the plugins, not to mention have my own botting to do, and my own life to live, but I'm trying to put in as much as I can for the sake of t3h awesome!). But yeah, I expect I'll get around to integrating a simple "keep all ilvl 63 unid" within the next version or two!
 
Regarding shields, scared shields can go up to 20% block base, with a max of +9% block.

Anywhere from 27-29% block total with crappy (not sure how to define this) stats are still sellable.
Crit chance on shield is a big score bonus, even more so when stacked with a 27-29% shield.

PS : A 29% shield with moderate shield stats are easily worth over 10m (Just sold a couple this week)
 
Regarding shields, scared shields can go up to 20% block base, with a max of +9% block.
Anywhere from 27-29% block total with crappy (not sure how to define this) stats are still sellable.
Crit chance on shield is a big score bonus, even more so when stacked with a 27-29% shield.
PS : A 29% shield with moderate shield stats are easily worth over 10m (Just sold a couple this week)

Great, exactly the kind of info I needed, thank you. I'll try and get some good scoring for shield block % along these lines in for another update tonight!
 
I noticed that salvaging items now takes a very very long time, is that DB case or plugin case?
 
Only the iLvl 62 and 63 (Dread Shield and Sacred Shield, respectively) are worth keeping for block tanks (Barbs and Monks). For Wizards/WDs that choose to use shields, it's only the stats that matter. Total Block Value (TBV) only matters for block tanks, whereas for casters it's only a stat stick so I'd suggest any high Int/Crit/Life% shields should be kept without regard to shield quality or TBV.

For actual tanking shields, regardless of having a mainstat such as DEX or STR, you'd run the gamut of 20% block rate with monster stats (Crit/ResAll/RA+high single/Life%/Crit), up to 25%+ with just solid resists. I'm using, and have sold, Chromatic Sacred Shield of Invulnerability (TBV 25+) for around a million, up to several million for a 79/29 so I know the market is there.

I'd break it down into 2 categories. Any shield with caster stats (any TBV) vs shields with tanking stats (20%+ with very, very good modifiers - to 26%+ with average modifiers).
 
I noticed that salvaging items now takes a very very long time, is that DB case or plugin case?

How long is "very very" long? It should average 1-3 seconds per item or so at most (human sort of speed looking through their items making sure things should be salvaged). About how long is it taking for each item to stash/salvage/sell for you would you say on average?
 
How long is "very very" long? It should average 1-3 seconds per item or so at most (human sort of speed looking through their items making sure things should be salvaged). About how long is it taking for each item to stash/salvage/sell for you would you say on average?

I have no problem with human way of analysing and salvaging items : ) I just was suprised, since I didn't bot for 3 weeks :) It was big change and i didn't know was it DB or plugin change. Comparing time spent for salvaginh 3weeks ago and now - it takes now very very long )
 
I have no problem with human way of analysing and salvaging items : ) I just was suprised, since I didn't bot for 3 weeks :) It was big change and i didn't know was it DB or plugin change. Comparing time spent for salvaginh 3weeks ago and now - it takes now very very long )

LOL! Yes, still only a matter of seconds though. I wanted it to still go quickly (ie - not spend 30 seconds "looking" at each item), but also make it impossible to detect from Blizzard-end - so it now takes 1-3 seconds per item, randomized one very single item, as of version 1.9.4+ - much much slower than before (before it did things 1-at-a-time still unlike default DB which is all-at-once, but it was still like lightning speed), but still fast enough to not be irritating, and slow enough to be undetectable! :D Just trying to minimize all the possible areas Blizzard might randomly decide to start trying to track people on (quite a few users requested an increased delay, or a randomized delay, which is why I did it!).
 
Hey Giles, Ive been using this for a while, and its great except i wanna know how you score mf and gf items. the score your giving mf and especially gf items are extremely low. I was using custom loot rules a few days ago and i had it pick up +18 mf%, so i got a 25% gf belt with 140 str and it sold for 850k on ah, what would you score that kind of belt?

I think you should pick a option avaiable if it should pick up all gear +15% gf and/or gf, or 17%, etc. Thanks
 
Last edited:
Hey Giles, Ive been using this for a while, and its great except i wanna know how you score mf and gf items. the score your giving mf and especially gf items are extremely low. I was using custom loot rules a few days ago and i had it pick up +18 mf%, so i got a 25% gf belt with 140 str and it sold for 850k on ah, what would you score that kind of belt?
I think you should pick a option avaiable if it should pick up all gear +15% gf and/or gf, or 17%, etc. Thanks
MF and GF approaching the "max limits" start getting very large score bonuses - particularly on jewelry (which guarantees a keep even if it has no other stat at all if MF/GF/LOH/AllResist is close to or at the cap for the item type). +15% GF/MF alone on a belt is worth nothing - search for 15% GF on a belt right now and you'll find hundreds of items valued at 2k gold. But close to cap they get big score boosts. (Your example item - a 25% GF belt with 140 strength would probably score about 20,000-25,000 at a rough guess).
 
I'm quite curious if anyone else is getting a problem picking up hand crossbows that are ilvl 61+ rare? I pick up every other ilvl 61+ rare weapon, but never the hand crossbows is there any reason behind it?
 
I'm quite curious if anyone else is getting a problem picking up hand crossbows that are ilvl 61+ rare? I pick up every other ilvl 61+ rare weapon, but never the hand crossbows is there any reason behind it?
What version of the plugin & DemonBuddy are you using? And have you definitely set the config to pickup ilvl 61+ yellow weapons? (just making sure! :P). DB does struggle a bit recognizing hand xbows more than any other item for whatever reasons, but my plugin should recognize them without any issues!
 
Demonbuddy v1.0.880.204
GilesStashReplacer v1.9.3
gW4RC.webp


I just notice v1.9.4 came out, I'll update to that one and see if that does the trick.
 
I think i screwed up somewhere, but the bot is picking up everything. So i switched back to 1.9.3.

Using build #204
 
I think i screwed up somewhere, but the bot is picking up everything. So i switched back to 1.9.3.
Using build #204

Yes, you probably did ;) 1.9.4 will work perfectly with #204 (won't work with previous DB versions though). If it's picking up whites whereas 1.9.3 didn't then that's a sure sign that you've not installed it correctly (eg have not installed to the proper folder name in DB), or that you simply needed to restart DB and double-check the config window in the plugin (making sure "Use Giles Filters" is selected etc.). Also remember that whenever a plugin is updated, you need to re-enable it in the plugins tab in DB (it's automatically disabled when the version number changes on any plugin).

You could also try deleting the "CompiledAssemblies" folder within the DemonBuddy folder and restarting DB - this is the next-best thing to using a totally clean DB install (a totally clean install in a new folder is best, but simply deleting CompiledAssemblies folder and letting DB run and re-create it can sometimes be a quicker fix for problems). Post-back if you find what the problem was, I'm sure it was something very simple & obvious! (somebody in IRC last night said "Urgh new stash replacer doesn't work! :(" when new version came out, then 2 minutes later "Oh, I restarted DB and it all works perfect now, never mind!" :D).
 
Back
Top