The server is acting up again, disconnecting as soon as it reconnects on an endless loop.

werrdd

doing the same to me on both of my ac accounts... eveb tried logging out and in to see if it fixed the problem but it doesnt..

classic loot question here, I've spent a long time getting all my rules set up right, and I've figured out everything except one.


I have for high AL set pieces, but I cant figure out how to differentiate them between extremeties and body.


Like i want 1 rule for non extremeties al 240+, and 1 rule for extremeties 300+


Any way I can do this?

 

-----signature-----

Ok, I see that you either updated your advanced tips wiki or I've been blind for months, but ty for the chart!


my new question is can i do an extremety rule for extremeties with an 'or' like i can with string names? with the '|' key?

 

-----signature-----

Are there any plans to simplify/integrate loot management into the VTank interface? Right now I use the Alinco integration, simply because its so easy to add/remove enable/disable looting at any time from within the game.

 

-----signature-----

Nooo! Leave it out, leave it out!

I felt the same way as you before I switched, but now I see it is way better to have it out. (well, if you play in "window mode" at least. If you play full screen then i guess it'd be a pain, go get a $200 netbook and edit your loot profile from that. hehe)


FYI: enable/disable looting as a whole is done ingame, as is choosing which loot profile to run from. It's only the editing of the loot rules in a loot profile that is done out of the game.

Umm, are you talking upper 'OR' lower legs? or are you talking upper leg 'OR' upper arm?

hehe

To start off, make sure you include a condition for all these rules that states your looking for armor, and not clothes: "ObjectClass=Armor"


if it's the first, then you use the greater then less then symbols to loot something in the range. But thne you'd still have to have seperate rules for arms vrs legs.

For example, in 1 loot rule entry, you put both of these conditions, both must end up being true for the item to be looted:

Req Type: "Long Value >=" Acts On: "Coverage" Long Value: 256

Req Type: "Long Value <=" Acts On: "Coverage" Long Value: 512


There is a gotcha with the lower arms and the fact that upper arms, chest & abs can be added together and the result is less then lower arms but greater then upper arms. You'd have to add two more conditions to NOT loot those combinations so you'd have 4 total conditions as follows:

Req Type: "Long Value >=" Acts On: "Coverage" Long Value: 4096

Req Type: "Long Value <=" Acts On: "Coverage" Long Value: 8192

Req Type: "Long Value !=" Acts On: "Coverage" Long Value: 5120

Req Type: "Long Value !=" Acts On: "Coverage" Long Value: 7168


So really, it seems easier to just create a seperate rule for each extremity.


if it's the second, sorry, i think you have to create two seperate rule entrys.


^

^ Before Coffee


v After Coffee =)

v


OOOOHHHHH WAIT A MIN!!!! hehe, judging by the AL example your giving 240 for body and 300 for extremities, you mean head,hand,feet don't you? LoL

Ok, then you make 2 rules as follows:


Extremities (this loots head,hands,feet):

Req Type: "Long Value >=" Acts On: "Coverage" Long Value: 16384


Body (this loots any combination of body coverage excluding head,hands,feet):

Req Type: "Long Value <=" Acts On: "Coverage" Long Value: 15360

Yes the second bit is what i was referring to, ty

 

-----signature-----

NP


one urgent issue I just discovered though, just because something has AL on it doesn't make it ObjectClass=Armor. So you might want to replace the "ObjectClass=Armor" condition with something like:

Req Type: "Long Value >=" Acts On: "Coverage" Long Value: 256


On all "Body" rule set. The "Extremities" one doesn't need it since it is already looking for greather then 16k. But the "Body" rule is looking for less then 15k without a minimum value. So create the minimum value of 256 to not have undies trigger the rule. (Course, on the otherhand, if undies don't have AL, then your AL=240+ condition would exclude undies. hmm...)


Ok, maybe just drop that "ObjectClass=Armor" condition entirely. =)


P.S. I found this issue when I ran a VT PropertyDump against my helmet, which is a Armet tailored over a Fez hat or something. It states "ObjectClass=Clothing". ieie!!!

Dang thing has awesome starting AL and Prots too. So with tailoring available to fix the looks, i'm adjusting my loot rules to not be picky about "ObjectClass" anymore.