They are legendaries
I left scoring in for them because I find it quite funny seeing what terrible scores some legendaries get 
Not as far as I've seen, no, but I might have overlooked a stat somewhere - but I really don't think there is currently (I wouldn't put my life on it though, if anyone has spotted this variable, let me know
).[00:18:35.450 D] There are 6 plugins.
[00:18:44.466 N] [Items] Loaded Item Rules: Giles Stash Replacer Plugin Rules - ilvl 61+ BLUE FOR CRAFT MATS - ONLY USE WITH PLUGIN ENABLED
[00:18:52.284 N] [Unstucker v2.2.0] Enabled.
[00:18:52.850 N] [GilesWorldObjectHandler 1.3.1] ENABLED: Giles World Object Handler is now in effect!
[00:18:53.302 N] [GilesStashReplacer 1.6.4] Enabled! Now replacing DB's stash routine.
[00:18:53.758 N] [GilesMonsterPriorityChanger 1.4.3] ENABLED: Giles monster priority changer now in effect!
[00:18:54.230 N] [DebuffsEvasion 0.4] Loading config.
[00:18:54.231 N] [DebuffsEvasion 0.4] DebuffsEvasion enabled.
[00:19:04.365 N] Current bot set to Order Bot
[00:19:04.365 N] Loaded profile [Act1 - Inferno] Champion-Hunting 1.8.1 by 5avage and RadonicI'll take a look at the logs when I finish going through 4 bots with 3 pages each full of items tweaking scores even further for next test version
I'll take a look at the logs when I finish going through 4 bots with 3 pages each full of items tweaking scores even further for next test version
Until then though - I want to try and rule out something altogether - can you try running DB "normally/manually" and see if it works fine? I want to see if DB bugs out when being loaded from command-line rather than "direct"? Just want to rule this out as a possible cause of problems or not, if you could please!
Hi, this plugin is nothing to do with pickup. This is a bug within DemonBuddy itself and happens at random - nothing you can do about it, would happen even without any plugins in use and just a basic routine. We're all awaiting a new DB version which is meant to fix this item mis-reading problem
It does stash anything that is a legendary regardless of stats, it really does - but read the experiment I took linked in the post above (or click) - when I tracked the issue down DemonBuddy would not return ANYTHING on the item. The quality was listed as blue, the name was the name of another item which can sometimes come from your backpack, an equipped item, or even an item on sale in a nearby vendor. The stats were all blank. Even the internalname was listed wrong. There was no way at all for the plugin to detect it was a legendary, as DemonBuddy had everything about the item wrong (obviously it's memory pointer screwed up and was pointing at another item or a random block of memory). The only way to tell it was a legendary is by looking at Diablo 3 yourself with your own eyes - DB nor my plugin could do anything. We just really need DemonBuddy to fix this issue.
Hi, this plugin is nothing to do with pickup. This is a bug within DemonBuddy itself and happens at random - nothing you can do about it, would happen even without any plugins in use and just a basic routine. We're all awaiting a new DB version which is meant to fix this item mis-reading problem
Testing wise I just cheat and fill my backpack to full with items, then click start - and it'll immediately do the town-run and run to stash and I can watch it in action (and usually quickly hit "stop" before it salvages so I can manually check what it wants to salvage before it does it). Good reliable way to see the plugin is working! But profile wise, I think this needs to be down to the routine developers - and DB needs to add a "do townrun" command routine developers can slot in at various points in their profiles if they want. I don't see the point of it myself though, can sometimes do 3 or 4 runs of the act 1 inferno routine before it gets a full backpack, sometimes longer with bad luck, no point doing the town-run every loop!
<?xml version="1.0" encoding="utf-8" ?>
<ItemRules name="Giles Stash Replacer Plugin Rules - ilvl 61+ YELLOW - ONLY USE WITH PLUGIN ENABLED" useRoundedValues="false">
<Priority priority1="Sell" />
<Categories>
<!-- Pickup rules are still IMPORTANT with my plugin! -->
<!-- They should focus purely on quality and item levels BUT NO OTHER STATS to help avoid DB bugs -->
<Category ruleType="PickUp">
<ItemRule itemName="Mythic Health Potion" stack="1" />
<ItemRule itemName="Flawless Square Emerald" stack="1" />
<ItemRule itemName="Flawless Square Amethyst" stack="1" />
<ItemRule itemName="Flawless Square Ruby" stack="1" />
<ItemRule itemName="Flawless Square Topaz" stack="1" />
<ItemRule itemName="Tome of*" stack="1" />
<ItemRule itemName="Gold" stack="50" />
<ItemRule itemName="*Plan:*" stack="1" />
<ItemRule itemName="*Design:*" stack="1" />
<ItemRule description="Any rare item ilvl 61+">
<StatRules>
<Rule stat="Level" minValue="61" quality="Rare4" />
</StatRules>
</ItemRule>
<!-- All blues 63 -->
<ItemRule description="Any blue item ilvl 63+">
<StatRules>
<Rule stat="Level" minValue="63" quality="Magic1" />
</StatRules>
</ItemRule>
<ItemRule itemBaseType="Jewelry" description="Jewelry ilvl 59+">
<StatRules>
<Rule stat="Level" minValue="59" quality="Rare4" />
</StatRules>
</ItemRule>
<!-- All Legendary or Set items -->
<ItemRule description="Any set or legendary">
<StatRules>
<Rule quality="Legendary" />
</StatRules>
</ItemRule>
</Category>
<!-- Sell category shouldn't be needed, but there to tidy up any junk that didn't make the salvage due to DB bugs -->
<Category ruleType="Sell">
<ItemRule description="Sell leftover junk">
<StatRules>
<Rule stat="Level" minValue="1" />
</StatRules>
</ItemRule>
</Category>
</Categories>
</ItemRules>