@ Zeek350, so you want truly perfect swords and nothing but perfect swords?

Ok then..., the specs we're going to find in the "/VT PropertyDump" are: 36-60, +20%a, +20%md, Sword 400 to Wield

I have bolded them below, In my next post we'll make the rules...


[VTank] --------------Object dump--------------

[VTank] [Meta] Create count: 1

[VTank] [Meta] Create time: 1/21/2012 10:41 AM

[VTank] [Meta] Has identify data: True

[VTank] [Meta] Last ID time: 1/21/2012 11:13 AM

[VTank] [Meta] Worldfilter valid: True

[VTank] ID: BFF83AD3

[VTank] ObjectClass: MeleeWeapon

[VTank] (S) Name: Flaming Takuba

[VTank] (S) FullDescription: Flaming Takuba

[VTank] (I) CreateFlags1: -1860091240

[VTank] (I) Type: 3895

[VTank] (I) Icon: 5753

[VTank] (I) Category: 1

[VTank] (I) Behavior: 18

[VTank] (I) Value: 12112

[VTank] (I) Unknown10: 1

[VTank] (I) IconOutline: 33

[VTank] (I) EquipType: 1

[VTank] (I) Container: 1343144798

[VTank] (I) EquipableSlots: 1048576

[VTank] (I) Burden: 392

[VTank] (I) HookMask: 2

[VTank] (I) Material: 33

[VTank] (I) PhysicsDataFlags: 137345

[VTank] (I) WieldReqValue: 400

[VTank] (I) ActivationReqSkillId: 11

[VTank] (I) GemSettingQty: 4

[VTank] (I) GemSettingType: 49

[VTank] (I) SkillLevelReq: 252

[VTank] (I) Workmanship: 7

[VTank] (I) Spellcraft: 232

[VTank] (I) CurrentMana: 1001

[VTank] (I) DescriptionFormat: 5

[VTank] (I) MaximumMana: 1001

[VTank] (I) LoreRequirement: 113

[VTank] (I) WieldReqType: 2

[VTank] (I) RankRequirement: 0

[VTank] (I) 47: 6

[VTank] (I) WieldReqAttribute: 11

[VTank] (I) DamageType: 16

[VTank] (I) WeapSpeed: 38

[VTank] (I) EquipSkill: 11

[VTank] (I) MaxDamage: 60 ** I changed this to reflect "Perfect" **

[VTank] (D) SalvageWorkmanship: 7

[VTank] (D) MeleeDefenseBonus: 1.2

[VTank] (D) ManaRateOfChange: -0.05

[VTank] (D) Variance: 0.4 ** I changed this to reflect "Perfect" **

[VTank] (D) DamageBonus: 1

[VTank] (D) Range: 0

[VTank] (D) AttackBonus: 1.2

Ok, so what we're really looking for is:


WieldReqValue >= 400 ** We want 400+ swords. **

WieldReqAttribute == 11 ** Sword is 11, and we only want swords. So we're using == on this one. **

MaxDamage >= 60 ** Using >= here because you never know when turbine will up the max dmg. **


Variance <= 0.4 ** This is the property that gives us the MinDamage value of 36. And here we're using <= because if a lower variance exists, we want it!

The mathmatical equation for Variance is (Max - Min) / Max = Variance. (60-36)/60 = 0.4

MeleeDefenseBonus >= 1.2 ** This is just a rule to remember, always put a "1." infront of the MeleeDefenseBonuse value your looking for. 20 = 1.20 (ending zeros seem to get forgotton about though, and we end up with 1.2) **

AttackBonus >= 1.2 ** This is just a rule to remember, always put a "1." infront of the AttackBonuse value your looking for. **


Ok, so I'm still trying to prove myself wrong here, but It seems to me that properties (aka: Requirements) with Intergers are always found under LongValueKey and decimal points are always under DoubleValueKey. So our requirements would be:


"Long Value Key >=" "WieldRegValue" "400"

"Long Value Key ==" "WieldRegAttribute" "11"

"Long Value Key >=" "MaxDamage" "60"

"Double Value Key <=" "Variance" "0.4"

"Double Value Key >=" "MeleeDefenseBonus" "1.2"

"Double Value Key >=" "AttackBonus" "1.2"


-Picaro

You really don't need WieldReqValue.

Lets say a 370 sword meets your minimum requirements, what does it matter that its not a 400? If it meets your mins, it meets your mins...

Chances are your minimum requirements are greater or equal to only what 400 swords can generate anyway.

Thus, adding the wieldreqvalue >= 400 is not necessary.

Thanks Mag-nus. I'm removing that extra requirement from my rules now. I guess it would only be usefull if you were looking for noob weapons with a low wield req.


I love trimming usless requirements from my loot profile and making it more efficent!! =)


-Picaro

How would I set up a rule to loot Majors that are not on weapons and are not banes?

Also, is there any limit to how long a string can be in the String Value Pattern field? I'd like to set up a single rule for all trophies but I'm worried I might break something with a hugely long value filled with |'s.

So only on Armor, Undies, and Jewlery/Trinkets then?

Well, I think you'll want to use more then 1 rule to start with. Here are my reasons:


1) Armor with Majors, we'll want to be picky about AL, I wouldn't wear a super crapy peice of armor just because it had Epic MeleeDef on it.

Also, Armor should be split into 2 rules of it's own, "Body" & "Extremities". They have different Max AL. Body caps out at about 274 and Extremities at about 310.

Body = Chest,UpperArms,LowerArms,Abs,UpperLegs,LowerLegs

Extremities = Head,Hands,Feet

**NOTE: Then there's Covenant, I haven't found any good charts that show max AL of Extremities on Cov being any different then for the Body, but we still need at least 1 extra rule just for Cov due to max al being 500+ (if you want cov that is). We also want to make sure our normal 2 armor rules exclude Cov armor.


2) Undies, well, i'm picky about coverage, I bane my undies and don't want any gaps like missing lower legs or lower arms. I was SOOO happy when Turbine fixed Abs coverage on undies. That had bugged me for soo long! =)


3) Jewlery/Trinkets, well, there's not much to be picky about here, they have neither AL nor Coverage, but being picky on the first 2 item types forces us to make a seperate rule for this item type.



sorry, i don't know. I have seperate rules for trophies that are named after the general hunting area you get them from. I think the sample loot profile I started with came that way and I've just ran with it.


Anyhow; The requirement you want to use to make sure something has a Major on it is:

"Spell Match and Count"

You can put multiple words speerated by the 'or' symbol "|" (SHIFT + \ on most keyboards) on both the "Does Match" and the "Does NOT Match" fields. (I know you know this ColdAvaton, but maybe somebody else reading this thread doesn't)

"Minimum spells that match" allows you to get picky about finding Dual Majors and so on. I leave this at 1 because I haven't found enough Majors & Epics on good gear to be that picky yet.


More on next post...

Ok, so all the rules we make to loot majors (and Epics i assume) will start out with the Requirement Type: "Spell Match and Count"


On the "Does Match" field, we enter "Major|Epic". (if you want Minors too you'd enter "Minor|Major|Epic", **Note: the the order is NOT important, i'm just OCD! hehe**)


On the "Does NOT Match" field, we enter "Bane|Ward|Gain". **NOTE: here you can also start listing other buffs you don't want to find Majors for, like "Jumping".**


On the "Minimum spells that match" field, leave it a 1 unless you only want Dual Majors/Epics


Now you can clone this rule a couple times (like 5x), rename them, and add the specifics to them...


For the "Armor - Extremities" rule, we want to add the following requirements:

"Long Value Key >=" "Coverage" "16384" **NOTE: There is a chart on VI's Wiki showing coverage values for parts of the body, and values for multi-slot coverage too. 16384 and higher is Head, Hands, and Feet. 16128 and lower covers everything except Head, Hands and Feet.**

"Long Value Key >=" "ArmorLevel" "250" **NOTE: I look for 250+ AL, you can change 250 to what you want, refer to the ac wikki for a chart showing max values of various armor types.**

"Long Value Key Has Flags" "Unenchantable" "0" **NOTE: this excludes the Unenchantable Cov and Olthoi armor**


For the "Armor - Body" rule, we want to add the following requirements:

"Long Value Key <=" "Coverage" "16128"

"Long Value Key >=" "ArmorLevel" "290" **NOTE: again, you can change 290 to meet your needs.**

"Long Value Key Has Flags" "Unenchantable" "0" **NOTE: this excludes the Unenchantable Cov and Olthoi armor**


For the "Covenant Armor" rule, we want to add the following requirement:

"Long Value Key >=" "ArmorLevel" "450" **NOTE: this AL value alone pretty much guaranties it to be Cov/Olthoi armor, no need to add a requirement to make sure it's Unenchantable.**


For the "Undershirts" rule, we want to add the following requirement:

"Long Value Key ==" "Coverage" "104" **NOTE: this is the value for full shirt coverage; Chest,UpperArms,LowerArms.**


For the "Underpants" rule, we want to add the following requirement:

"Long Value Key ==" "Coverage" "22" **NOTE: this is the value for full pants coverage; Abs,UpperLegs,LowerLegs.**


For the Jewelry and Trinkets rule, we want to add the following requirement:

"ObjectClass" "Jewelry" **NOTE: Trinkets are of this same class.**


So with those 6 rules, you will loot Majors & Epics on "decent" armor, undies, and jewelry/trinkets, but not weapons.


-Picaro

Ok, here's a list of sample strings i've been working on, if they don't work please don't flame me.





Find This


This


Find This or That


This|That


Find NOT This


^((?!This).)*$


Find NOT This nor That


^((?!This|That).)*$

Quote:

---

Searching for the first word(s):

---

Find This


^This


Find This or That


^(This|That)

Quote:

---

Searching for the last word(s):

---

Find This


This$


Find This or That


(This|That)$

Quote:

---

Searching for the exact word(s) and no other words are allowed to exist:

---

Find This


^This$


Find This or That


^(This|That)$

Quote:

---

Searching for the last word(s) with a special condition that the first word(s) don't match other word(s):

---

Find This but NOT if it starts with That


^((?!That).)*(This)$


Find This or That, but NOT if it starts with These nor Those


^((?!These|Those).)*(This|That)$

Thank you! You rock the house down!

Name of requester: hggm

Details of item being looted: (essay question)
I'm trying to loot a specific color on all armor pieces I find for a guildmate. Everything I have tried has failed to produce a single item.

The color is 203A6D according to the hex

Sample “/VT PropertyDump” of a similar item:


Attempted Rule:

Tailoring - Haebrean Pauldrons

0;1;1;15
23
Haebrean Pauldrons
1
54
32
58
109
20
0.1
Haebrean Pauldrons (Ornaments)