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

Item Rules QuickStart Guide

Anyone can make the rule for not keep the Gem such as "Square Ruby" ?
Although I don't have rule to keep these gem but DB always put them in stash. No way for me to choose.
 
can i know how to set a loot rule that pick up legendary, item set and rare item with ilvl 61 above?
 
Hi, I have one problem with one of my profiles, with this code it's supposed to pick up designs and plans... so for some reason it doesn't pick up them, even if I manually drop them.

PHP: 
      <!-- Pick up plans and designs, blacksmithing/jewelcrafting -->
      <ItemRule ruleType="PickUp" itemName="Plan*" stack="1" />
      <ItemRule ruleType="PickUp" itemName="Design*" stack="1" />

Thanks in advance.

edit: already fixed this problem :D
 
Last edited:
Code: 
<ItemRule itemBaseType="Weapon" twoHanded="true" description="High DPS 2h Weapons">
        <StatRules>
          <!-- Magic Weapons should have at least 1200 DPS -->
          <Rule stat="DPS" minValue="1200" quality="Magic1" />
          <!-- Rare weapons should have at least 1100 considering they provide extra stats most of the time. -->
          <Rule stat="DPS" minValue="1100" quality="Rare4" />
        </StatRules>
      </ItemRule>

Having something like that, would it not try to match an both a magic1 item and a rare4 item to 1 item (IE. NEVER happens?)

Or does it match each rule individually?

Code: 
<ItemRule itemType="Ring" >
			<StatRules>
				<Rule stat="MagicFind" minValue="18" />
			</StatRules>
		</ItemRule>
		
		<ItemRule itemType="Ring" >
			<StatRules>
				<Rule stat="GoldFind" minValue="18" />
			</StatRules>
		</ItemRule>

right now that is separate, would it also work if i put them under the same statrules like the weapon example?
 
I am also trying to wrap my head around making loot rules for certain things but with no item or anyway to test for sure, i need someone to tell me if this looks right/proper and would work:
Code: 
      <ItemRule itemBaseType="Armor" description="Rare armor with 2 sockets"
        <StatRules>
          <!-- Looking for 2 opensocket pants/chest with dexterity-->
         <Rule stat="Dexterity" minValue="70" quality="Rare4" />
         <Rule stat="Sockets" minValue="2" />
        </StatRules>
      </ItemRule>

will this nab any pants with 70+ dex and 2 open sockets(or 3 if possible?) also it could nab chest/cloaks as well i think?

heres another one i was looking at, even though i pasted it in the keep section. i saw everything else that was being kept had the itemrule type = keep in its line. so i changed it to this:
Code: 
                      [B][SIZE=3]<ItemRule ruleType="Keep"[/SIZE] [/B]itemBaseType="Armor" description="Rare armor with 2 sockets"
                                <StatRules>
                               <!-- Looking for 2 open socket pants/chest with dexterity-->
                                      <Rule stat="Dexterity" minValue="70" quality="Rare4" />
                                      <Rule stat="Sockets" minValue="2" />
                               </StatRules>
                        </ItemRule>

that should work 100% right?
 
Last edited:
A question for the devs mainly, but maybe players will point out the obvious reasoning to me if I've missed it... but wouldn't the "quality" stat be much more appropriate to set at <ItemRule> level rather than <Rule> level?

It just seems to really confuse how the rules work by setting the "quality" on every single individual rule within a ruleset, generally the entire ruleset should be specific to item quality?
 
GilesSmith said:
A question for the devs mainly, but maybe players will point out the obvious reasoning to me if I've missed it... but wouldn't the "quality" stat be much more appropriate to set at <ItemRule> level rather than <Rule> level?

It just seems to really confuse how the rules work by setting the "quality" on every single individual rule within a ruleset, generally the entire ruleset should be specific to item quality?
Click to expand...
I mentioned it to Apoc, he said that's the way it is and the way it'll stay since that's the item structure of Diablo3. You don't need to set the quality on every rule, just once at the top, and the rest will match it.
 
IeU said:
I did this and is working great for me.

Code: 
<?xml version="1.0" encoding="utf-8" ?>

<ItemRules name="Default Item Rules" useRoundedValues="true">

	<Priority priority1="Keep" priority2="Salvage" priority3="Sell" />

	<Categories>
		<Category ruleType="PickUp">
      
			<ItemRule>
				<StatRules>
					<Rule quality="Magic1" />
				</StatRules>
			</ItemRule>

			<ItemRule itemName="Gold" stack="250" />
      
			<ItemRule itemName="Page of*" stack="1" />
			<ItemRule itemName="Tome of*" stack="1" />
      
			<ItemRule itemName="*Ruby*" stack="1" />
			<ItemRule itemName="*Emerald*" stack="1" />
			<ItemRule itemName="*Topaz*" stack="1" />
			<ItemRule itemName="*Amethyst*" stack="1" />

			<ItemRule itemName="*Health Potion*" stack="1" />
		</Category>

		<Category ruleType="Keep">
      
			<ItemRule itemBaseType="Weapon" twoHanded="true" description="High DPS 2h Weapons">
				<StatRules>
					<Rule stat="DPS" minValue="1200" quality="Magic1" />
					<Rule stat="DPS" minValue="1100" quality="Rare4" />
				</StatRules>
			</ItemRule>

			<ItemRule itemBaseType="Weapon" twoHanded="false" description="High DPS 1h Weapons">
				<StatRules>
					<Rule stat="DPS" minValue="1000" quality="Magic1" />
					<Rule stat="DPS" minValue="900" quality="Rare4" />
				</StatRules>
			</ItemRule>

			<ItemRule itemBaseType="Armor" description="Rare armor">
				<StatRules>
					<Rule stat="Intelligence" minValue="160" quality="Rare4" />
					<Rule stat="Vitality" minValue="160" quality="Rare4" />
					<Rule stat="Dexterity" minValue="160" quality="Rare4" />
					<Rule stat="Strength" minValue="160" quality="Rare4" />
					<Rule stat="ResistAll" minValue="50" quality="Rare4" />
				</StatRules>
			</ItemRule>
      
			<ItemRule itemBaseType="Jewelry" description="Rare jewelry">
				<StatRules>
					<Rule stat="Intelligence" minValue="80" quality="Rare4" />
					<Rule stat="Vitality" minValue="80" quality="Rare4" />
					<Rule stat="Dexterity" minValue="80" quality="Rare4" />
					<Rule stat="Strength" minValue="80" quality="Rare4" />
					<Rule stat="ResistAll" minValue="30" quality="Rare4" />
					<Rule stat="AttackSpeedPercent" minValue="17" quality="Rare4" />
				</StatRules>
			</ItemRule>

			<ItemRule ruleType="Keep" description="Legendary">
				<StatRules>
					<Rule quality="Legendary" />
				</StatRules>
			</ItemRule>
      
		</Category>
	
		<Category ruleType="Salvage">
			<ItemRule description="Salvage level 60 gear">
				<StatRules>
					<Rule stat="Level" minValue="61" quality="Magic1" />
				</StatRules>
			</ItemRule>
		</Category>	

		<Category ruleType="Sell">
			<ItemRule description="Sell Everything">
				<StatRules>
					<Rule quality="Magic1" />
				</StatRules>
			</ItemRule>
		</Category>
		
	</Categories>

</ItemRules>
Click to expand...


Hi , I tried to use this code but it wont pick up any blues. I'm running the Arreat profile in Nightmare. But shouldn't it be picking up the blues and selling them? o.o
 
Is it posible for me to determine whether I wanna pick up a magic based on its sell value ? Or do I need to use ilvl for that ? :)
 
Is there an OR for statrules? So if I wanted (100dex OR 100int OR 100str )AND 100vit, how could I do the ors? I currently just have one full item rule per stat :(
 
yes that seems to be the case :( which turns into LONG ASS loot rules
 
Few things that seem to be missing/are unclear;

1: LifeOnHit stat, globe&gold pickup radius bonus stat - neither of these are not listed - how can we filter them?

2: "WizardHat" has it's own item-type entry, implying it WON'T be filtered in the "Helm" itemType. However other unique itemtypes are missing, so I don't know if specific itemtype filters will catch them or not;
- Cloaks (a type of demon hunter chest armour).
- Mighty Belt (a type of barbarian belt).
- Spirit Stone (a type of monk helm).
- Voodoo mask (a type of witch doctor helm).
Since "WizardHat" has it's own itemtype, I'm suspicious that "cloaks" for example may always be ignored in any "Chest" itemType filters. Can we have some clarification here, or have these other specific itemtypes added?

3: It really makes no sense to have the "Quality" entry listed at <Rule> level instead of <itemRule> level. Quality should be taken off <Rule> and either given it's own unique XML entry, or stapled on as an optional extra on "itemRule". It doesn't matter how Diablo 3 items are internally, DemonBuddy handles the itemRules.xml itself and so can be coded any way the devs want.
 
GilesSmith said:
Few things that seem to be missing/are unclear;

1: LifeOnHit stat, globe&gold pickup radius bonus stat - neither of these are not listed - how can we filter them?

2: "WizardHat" has it's own item-type entry, implying it WON'T be filtered in the "Helm" itemType. However other unique itemtypes are missing, so I don't know if specific itemtype filters will catch them or not;
- Cloaks (a type of demon hunter chest armour).
- Mighty Belt (a type of barbarian belt).
- Spirit Stone (a type of monk helm).
- Voodoo mask (a type of witch doctor helm).
Since "WizardHat" has it's own itemtype, I'm suspicious that "cloaks" for example may always be ignored in any "Chest" itemType filters. Can we have some clarification here, or have these other specific itemtypes added?

3: It really makes no sense to have the "Quality" entry listed at <Rule> level instead of <itemRule> level. Quality should be taken off <Rule> and either given it's own unique XML entry, or stapled on as an optional extra on "itemRule". It doesn't matter how Diablo 3 items are internally, DemonBuddy handles the itemRules.xml itself and so can be coded any way the devs want.
Click to expand...

Any new on this?
 
SMcCloud said:
It is DEFINITELY AND and not OR and everything works as intended. I have tested several different cases such as this one using the following item
Click to expand...

IeU said:
I got to confirm the same.
Click to expand...

So, if you 2 are correct, doesn't that mean the default rules are written like shit?

Code: 
      <ItemRule itemBaseType="Weapon" twoHanded="true" description="High DPS 2h Weapons">
        <StatRules>
          <!-- Magic Weapons should have at least 1200 DPS -->
          <Rule stat="DPS" minValue="1200" quality="Magic1" />
          <!-- Rare weapons should have at least 1100 considering they provide extra stats most of the time. -->
          <Rule stat="DPS" minValue="1100" quality="Rare4" />
        </StatRules>
      </ItemRule>

      <ItemRule itemBaseType="Weapon" twoHanded="false" description="High DPS 1h Weapons">
        <StatRules>
          <Rule stat="DPS" minValue="1000" quality="Magic1" />
          <Rule stat="DPS" minValue="900" quality="Rare4" />
        </StatRules>
      </ItemRule>

So from this, it would only pick up rare 2h over 1200 dps and rare 1h over 1000 dps?
 
I've been writing my rules as AND's working under the belief they are AND statements not OR statements, if they are OR statements' it'll make filtering for multiple stats on an item quite hard. I can understand if its taken as an OR if the stat appears twice in a rule, but i think we need either a statement from the team as to which it is or more testing to find out. Fingers crossed for AND's because if its OR then my rules are fecked :P


So while looking at the default rules, I think its OR when a stat is repeated, and AND when its a new stat

We still need tags for LoH and LifeLeech xD

I also think we need a tag like Prime or something so we dont need 3 ItemRules when we want armor with either Str/Int/Dex + another stat where Str/Int/Dex has the same minValue. Would be nice and would save on so much repeated code.

Can we also get Arcane Power on Crit for wands?
and maybe a ResistAny flag which means we dont have to repeat the resistances rules when we are going for a single resist + all resist (monk gear)

oh oh oh and pickup range o/
 
Last edited:
You must log in or register to reply here.
Back
Top