[Plugin] "Item Rules 2" File based scripting language!

ooasauron · Feb 3, 2013

Edit:This works great for me, only thing is how to set it to ignore all 2H weapons?

this i still try to figure out

Mystery^^ · Feb 3, 2013

ooasauron said:
this i still try to figure out

Me too.. still want to know how to ignore all 2hand weapon

genis09 · Feb 3, 2013

Mystery^^ said:
Me too.. still want to know how to ignore all 2hand weapon

[QUALITY] == "Rare" && [TWOHAND] == true -> [IGNORE]

Works for me. You just have to remove the rule exceptions for weapons.

Mystery^^ · Feb 3, 2013

thx man now it's working for me

Kurgan · Feb 4, 2013

[QUALITY] == "Rare" && [LEVEL] > 58 && [BASETYPE] == "Weapon"
//ignore rule
[QUALITY] == "Rare" && [LEVEL] <= 58 && [BASETYPE] == "Weapon" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Helm" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Chest" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Shield" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Pants" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Bow" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Crossbow" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Legs" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Belt" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "FollowerSpecial" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "HandCrossbow" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Quiver" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Boots" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "WizardHat" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Orb" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Cloak" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "HandCrossbow" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "VoodooMask" -> [IGNORE]

Well, with this configuration all works fine, but I have a fail, bot takes, Bows, Crossbows and HandCrossbows, any have the same problem?

Mystery^^ · Feb 4, 2013

Kurgan said:
[QUALITY] == "Rare" && [LEVEL] > 58 && [BASETYPE] == "Weapon"
//ignore rule
[QUALITY] == "Rare" && [LEVEL] <= 58 && [BASETYPE] == "Weapon" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Helm" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Chest" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Shield" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Pants" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Bow" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Crossbow" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Legs" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Belt" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "FollowerSpecial" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "HandCrossbow" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Quiver" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Boots" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "WizardHat" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Orb" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Cloak" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "HandCrossbow" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "VoodooMask" -> [IGNORE]

Well, with this configuration all works fine, but I have a fail, bot takes, Bows, Crossbows and HandCrossbows, any have the same problem?

edit like

[QUALITY] == "Rare" && [LEVEL] <= 58 && [BASETYPE] == "Weapon" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Helm" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Chest" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Shield" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Pants" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Bow" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Crossbow" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Legs" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Belt" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "FollowerSpecial" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "HandCrossbow" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Quiver" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Boots" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "WizardHat" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Orb" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Cloak" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "HandCrossbow" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "VoodooMask" -> [IGNORE]

[QUALITY] == "Rare" && [LEVEL] > 58 && [BASETYPE] == "Weapon"

try it

Julen · Feb 4, 2013

really [ARCONCRIT] instead [ARCANCRIT] ?

Mystery^^ · Feb 6, 2013

https://riouxsvn.com/svn/dbplugins/

can't open it now

yura · Feb 6, 2013

often svn site down(((

Kurgan · Feb 6, 2013

Why my bot salvage legendaries when I choose "File based scrip rules"?, I have in townRuns-legendaries-all levels, when I choose "trinity scoring only" bot keep all legendaries, but when I choose "File based scrip rules", bot salvage legendaries, Why?...

peshmarie · Feb 6, 2013

down since 30h ...

Kakaru · Feb 7, 2013

Darkfriend,

what are the orders of operators?

A && B || C
will do first A && B and the result will be || with C, or the viceversa?

Concrete:
[QUALITY] == "Legendary" && [NAME] == "Triumvirate" # [AVGDMG] > 190 && [ARCONCRIT] > 0 || ([AVGDMG] > 200 && [INT] > 169 || [INTVIT] > 210)

What is this rule doing? I can't understand it without the rules of precedence between operators.

darkfriend77 · Feb 7, 2013

peshmarie said:
down since 30h ...

its back again .. sry

- - - Updated - - -

peshmarie said:
down since 30h ...

its back again .. sry

Mystery^^ · Feb 7, 2013

wating for item rules for Trinity .20 translation..

darkfriend77 · Feb 7, 2013

Kakaru said:
Darkfriend,

what are the orders of operators?

A && B || C
will do first A && B and the result will be || with C, or the viceversa?

Concrete:
[QUALITY] == "Legendary" && [NAME] == "Triumvirate" # [AVGDMG] > 190 && [ARCONCRIT] > 0 || ([AVGDMG] > 200 && [INT] > 169 || [INTVIT] > 210)

What is this rule doing? I can't understand it without the rules of precedence between operators.

Code:

// |  LOGICAL OPERATOR:
// |  -----------------
// |  OR          "||"       true || false   -> true
// |  AND         "&&"       true && false   -> false
// |  EQUAL       "=="         10 == 11      -> false
// |  NOTEQUAL    "!="         10 != 11      -> true
// |  LESSEREQUAL "<="         10 <= 10      -> true
// |  BIGGEREQUAL ">="         10 >= 10      -> true
// |  LESSTHEN    "<"          10 <  10      -> false
// |  BIGGERTHEN  ">"          10 >  10      -> false
// |  PLUS/MINUS  "+-"          1 +  2       -> 3
// |  MULT/DIV    "*/"          1 *  2       -> 2
// |  BRACKETS    "()"    (5+5)*2 == 5+(5*2) -> false

from bottom to top ...

darkfriend77 · Feb 7, 2013

Code:

// +---------------------------------------------------------------------------+
// | ______ __                             __              
// ||      |  |--.---.-.-----.-----.-----.|  |.-----.-----.
// ||   ---|     |  _  |     |  _  |  -__||  ||  _  |  _  |
// ||______|__|__|___._|__|__|___  |_____||__||_____|___  |
// |                                                |_____| 
// +---------------------------------------------------------------------------+
// | 2.210(beta) Item Rules 2 (only use with Beta DB .159+)
// | - added translation ofr legendary names, USEITEMIDS in the GUI.
// |   (non-english clients can use org. legendary.dis with that flag checked!)
// | - moved onto latest Trinity 1.7.2.00 thx to rrix
// +---------------------------------------------------------------------------+

only use with newest rules ... if u find a TranslationFix.log file in he TrinityLogs folder plz post this file on the forum or send it to me.
legendarys that couldn't be translated are KEEPED and will be logged out into that file ...

Code:

// +---------------------------------------------------------------------------+
// |  ______         __             ______ __                                  
// | |   __ \.--.--.|  |.-----.    |      |  |--.---.-.-----.-----.-----.-----.
// | |      <|  |  ||  ||  -__|    |   ---|     |  _  |     |  _  |  -__|__ --|
// | |___|__||_____||__||_____|    |______|__|__|___._|__|__|___  |_____|_____|
// |                                                        |_____|           
// +---------------------------------------------------------------------------+
// +-04.02.2013 ---------------------------------------------------------------+
// | - added some black weapon rules (hard)
// | - new pickups.dis which is far more accurate and better customizable (hard)
// | - added a safty rule that catches missed legendarys (hard)
// | - changed some rules in legendary and rare (hard)
// | - prepared the rules for the translation patch and for next trinity rel.
// +---------------------------------------------------------------------------+

available on beta repository. LINK

Kakaru · Feb 7, 2013

You're still not clear.

if BOTTOM TO TOP means AND is processed before OR then:

[QUALITY] == "Legendary" && [NAME] == "Triumvirate" # [AVGDMG] > 190 && [ARCONCRIT] > 0 || ([AVGDMG] > 200 && [INT] > 169 || [INTVIT] > 210)
is the same as

[QUALITY] == "Legendary" && [NAME] == "Triumvirate" # [AVGDMG] > 190 && [ARCONCRIT] > 0
[QUALITY] == "Legendary" && [NAME] == "Triumvirate" # [AVGDMG] > 200 && [INT] > 169
[QUALITY] == "Legendary" && [NAME] == "Triumvirate" # [INTVIT] > 210

If not, and it's top to bottom

[QUALITY] == "Legendary" && [NAME] == "Triumvirate" # [AVGDMG] > 190 && [ARCONCRIT] > 0
[QUALITY] == "Legendary" && [NAME] == "Triumvirate" # [AVGDMG] > 200 && [INT] > 169
[QUALITY] == "Legendary" && [NAME] == "Triumvirate" # [AVGDMG] > 200 && [INTVIT] > 210

Can you clarify it?

- - - Updated - - -

Also, latest 2.210 made the rules for some legendaries (eg helms) softer than previous hard rules. Is this a bug or intended?

Kurgan · Feb 7, 2013

Someone knows how to keep all legendaries with "items based rules" on?...

darkfriend77 · Feb 7, 2013

Kakaru said:
You're still not clear.

if BOTTOM TO TOP means AND is processed before OR then:

[QUALITY] == "Legendary" && [NAME] == "Triumvirate" # [AVGDMG] > 190 && [ARCONCRIT] > 0 || ([AVGDMG] > 200 && [INT] > 169 || [INTVIT] > 210)
is the same as

[QUALITY] == "Legendary" && [NAME] == "Triumvirate" # [AVGDMG] > 190 && [ARCONCRIT] > 0
[QUALITY] == "Legendary" && [NAME] == "Triumvirate" # [AVGDMG] > 200 && [INT] > 169
[QUALITY] == "Legendary" && [NAME] == "Triumvirate" # [INTVIT] > 210

If not, and it's top to bottom

[QUALITY] == "Legendary" && [NAME] == "Triumvirate" # [AVGDMG] > 190 && [ARCONCRIT] > 0
[QUALITY] == "Legendary" && [NAME] == "Triumvirate" # [AVGDMG] > 200 && [INT] > 169
[QUALITY] == "Legendary" && [NAME] == "Triumvirate" # [AVGDMG] > 200 && [INTVIT] > 210

Can you clarify it?

- - - Updated - - -

Also, latest 2.210 made the rules for some legendaries (eg helms) softer than previous hard rules. Is this a bug or intended?

AND is processed before OR

can u give an example ... of what got keeped ?

what changed: it will keep now any legendary that is found and has no rule in legendary.dis ... so if u have set keep legendarys 58+ and there is no rule for an item u found... it will keep it ...

777MAX777 · Feb 7, 2013

darkfriend77 said:
only use with newest rules ... if u find a TranslationFix.log file in he TrinityLogs folder plz post this file on the forum or send it to me.
legendarys that couldn't be translated are KEEPED and will be logged out into that file ...

Missing: 432930588;Стенания
Missing: 392131593;Султан слепящих песков
Missing: 592915675;Утренняя заря
Missing: 469402902;Пепельный мундир
Missing: -498215480;Dark Mage's Shade

[Plugin] "Item Rules 2" File based scripting language!

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member

Member

New Member

New Member

New Member

Member

New Member

Member

Member

New Member

New Member

Member

Member