To help understand syntax used by kolbot in pickit lists

Source https://darcvigilante.site/showthread.php?tid=9
======================================================

Pickit walk-through

First off familiarize yourself with some important and useful information.

NTItemAlias.ntj will answer 99% of item names/stats questions

Everything in the mpqdata folder, particularly weapons.txt and armor.txt

You could also see the max stats of items using Arreat Summit ToGo v.1.2b.
NIP lines

NIP lines are of the format: {PROPERTIES} # {STATS} # {MAXQUANTITY}

[Item-parser Syntax Information]

    [Keyword] separates into two groups
    [Property Keywords] = [Type], [Name], [Class], [Quality], [Flag], [Level], [Prefix], [Suffix]
    [Stat Keywords] = [{Number or NTItemAlias keyword}] or [Description] (description allow access to any text found in the item hover)
    [Maxquantity Keywords] = [Maxquantity] (used to limit the quantity kept)


    [Keyword] must be surrounded by '[' and ']'
    [Property Keywords] must be placed first


    Insert '#' symbol between [Property Keywords] and [Stat Keywords]
    Use '+', '-', '*', '/', '(', ')', '&&', '||', '>', '>=', '<', '<=', '==', '!=' symbols for comparison
    Use '//' symbol for comment


There is no getting around learning the NIP syntax. You simply have to bite the bullet and do it. No one here can learn it for you. While it is not the most user-friendly language, it is fairly easy to understand once you start working with it.

The NIP files you are using are configured in your character configuration file. You can include/exclude NIP files on a per character basis within that file. Anything that appears on a NIP line past the "//" symbol is ignored (we call this a comment).

Each NIP has 3 sections separated by # signs where the keywords associated with that section are found: {PROPERTY} # {STATS} # {QUANTITY}. Each section is comprised of what are commonly called attribute-value pairs. An AV pair is a keyword name that is assigned a value using an operator like this: [type] == circlet. These AV pairs are then grouped using logical conjunctions like "&&' (for and) and "||" (for or) to create a NIP.

Now this was pretty straight forward to me, but to some it seems to be a little confusing.

Think Of [Property] Keywords as "constants" that will remain the same no matter what.

These all go before the # (was pretty easy for me as I already tend to use item #'s).

This doesn't mean that they can't vary, just means that no matter what end item is still gonna be "boots".

If you were writing a line for all rare boots, the constants would be

[Type] && [Quality], those aren't gonna change no matter what you do.

Now think of [Stat] Keywords as "variables" things that you may want to be flexible with.

Like above, it doesn't mean that it can't have a Set Value.

Again I'll use boots as an example, we already know we want "[Type] == Boots && [Quality] == rare" but we also want them to have some FasterRunwalk and a little Fire Res.

So now we have [Type] && [Quality] # [Stat] && [Stat]

And when added it would look like this

[Type] == boots && [Quality] == rare # [FRW] >= 10 && [FireResist] >= 10

Now if you can't determine what goes before the # and what goes after the # simply open up NTItemalias.ntj and CTRL+F what it is you're trying to find.

You can tell whether its a [Property] or a [Stat] simply by locating its alias, everything has an alias, just a matter of finding it.
Order of pickit lines

Things that go before the #

[Type], [Name], [Class], [Quality], [Flag], [Level], [Prefix], [Suffix]

    NTIPAliasType
    NTIPAliasClassID(name)
    NTIPAliasClass(Norm-elite)
    NTIPAliasQuality
    NTIPAliasFlag


Things that go after the #

[Stat Keywords] : [Number or Alias]

NTIPAliasStat(skills,stats etc)

The odd-man out seems to be [Level] as its used as [Property], but in NTAlias its listed as a [Stat]

[Level] != [ItemLevelreq]

There is only one comparison symbol I can think of that really needs explaining, but I'll try and briefly give a rundown

"||" basically means OR

"()" Basically means TOGETHER/GROUP

"!=" Basically means DOES NOT EQUAL

The rest are pretty self explanatory.

Now I'll use the same example for boots but this time I want rare boots with 30FRW and FR and either CR or LR or dex

[Type] == boots && [Quality] == rare # [FRW] >= 10 && [FireResist] >= 10 && ([LIghtResist] >= 10 || [ColdResist] >= 10 || [Dexterity] >=1)

It's the same premise for any item, so once you have it figured out its pretty easy.

Using the same example lets say I wanted only boots of exceptional quality.

Well Normal, Exceptional, Elite = Class. I know this because i opened up NTItemAlias.ntj and CTRL+F "exceptional"

I know that Class = Property so in turn I know it goes before the #

So the same boots, but only exceptional versions becomes

[Type] == boots && [Class] == Exceptional && [Quality] == rare # [FRW] >= 10 && [FireResist] >= 10 && ([LIghtResist] >= 10 || [ColdResist] >= 10 || [Dexterity] >=1)

Adding too many qualifiers to any one line will make it harder for a novice to find any mistakes they have made.

Remember the simpler it is for you to read, the better.

Don't be afraid of using simple qualifiers. I hate writing rings/ammys/circlets and usually just use a couple of your standard catch-all lines.

[Type] == circlet && [Quality] == rare # ([ItemAddClassSkills] >= 2 || [ItemAddSkillTab] >= 2) && [FCR] == 20 && ([Strength] >= 10 || [Dexterity] >= 10 || [FRW] >= 30 || [Sockets] == 2 || [MaxHP]+[MaxMana] >= 35)

Now is that gonna grab junk? yea probably but look at this line

[Type] == circlet && [Quality] == rare # ([ItemAddClassSkills] >= 2 || [ItemAddSkillTab] >= 2) && [FCR] == 20 && ([Strength] >= 15 || [Dexterity] >= 15) && ([FRW] >= 30 || [Sockets] == 2 || [MaxHP]+[MaxMana] >= 35)

Guess what happens if your bot finds a rare Circlet with 2skills/20fcr/12str OR 12dex and 2soc?

A good basic catch all should simply have 2stats you want & a selction of other stats.

For instance I use this in my pickit for rare Amazon helms

[Type] == circlet && [Quality] == rare && [Flag] != ethereal # [AmazonSkills] == 2 && [FRW] == 30 && [Sockets] == 2

Remember Magic items can only get 2 affix, 1 prefix and 1 suffix

Rares Get 6 affix, 3 prefix and 3 suffix

Crafts Get 4 affix + craft mods, still limited to 3 prefix Or suffix max

That's pretty much all there is to writing a pickit in D2Etal. Remember that everyone makes simple mistakes, I ported my entire pickit from 1.7 and thought the new parser couldn't read it due to lots of #codes and name IDs...So I redid the whole thing and turns out I just had an odd syntax caused by a stray ^^.

Guess I should go into pickit and syntax errors, but unfortunately I very rarely get them and when I do it's usually an extra "[" or ")" missing.

Try searching for [Keyword] and (xxx || xxx) in your pickit.

Bot really seems to hate extra and missing "()"
Common bot pickit errors

    Syntax error 64

Usally means problem is after #​

    Syntax Error 64 (missing ; )

Missing or extra "][" or ")("​

    Syntax Error 64 (invalid left hand assignment)

having "=" instead of "=="">=""<="​

    Syntax Error 64 (xxx isn't defined)

having keyword missing "[]" or typo​

    Syntax Error 60

Usually means Problem is before #​

    Syntax Error 60 (xxx isn't defined)

having keyword missing "[]" or typo​

    Syntax Error 60 (missing ; )

Misplaced or missing "#"(usually see a bunch of white writing)​

    Syntax Error 60 (Syntax error)

Missing or extra "][" or ")("​

    Syntax Error 111

This is not an error in your pickit, but has to do with potions, usually grabbing + drinking.
And keep in mind just because you're not getting any errors from bot, that doesn't mean that your pickit isn't without mistakes.​
FAQ pickit

Q: Why does my bot pick up and stash junk?
A: Because it's on your pickit.

Q: How do I make bot keep "XXX" unid?
A: By having no qualifying [Stat]. Example: [Name] == Corona && [Quality] == Unique

Q: How do I add trap claws?
A: Same way you add anything else, only they are like orbs and have 2x different types. I use names just like I do with orbs.
[Name] == GreaterClaws
[Name] == GreaterTalons
[Name] == ScissorsQuhab
([Name] >= Handscythe && [Name] <= ScissorsSuwayyah)

Q: I noticed you use "[Name] >= && [Name] <=" just wondering why?
A: Simply easier than writing out each individual item name, but it has its drawbacks, for instance in the case of orbs I also wind up picking up all normal/exceptional amazon weapons(because they are between orbs) not a biggie on orbs but imagine if you put >= Crystalsword(#29) and <= Phaseblade(#225)

Q: Why does my bot keep picking up magic items when I have none on my pickit?
A: If you're certain you don't have any magics on your pickt it is usually caused by >= or <= on normal or rares

Q: How can I pick and sell items for gold
A: By adding only an impossible affix after the #
[class] == elite # [strength] >= 1000

Q: How come for viperskin you only have FireRes?
A: Unique items with all res only need one res to look for. If i have [FireResist] == 35, there is no need for it to look at any other qualifiers, Not like maras/vipers/metalgrids can spawn with 35fr,30LR,21Pr,30cr Same goes for charms, you only need 2 of the 4 Res to pickup an all res SC.

Q: What is the difference between [Itemlevelreq] and [Level]?
A: Well [Level] is kinda odd as although its listed as a [Stat] in NTitemAlias its actually used as a [Property], so If you want items under a certain level you would use [Name] && [Quality] # [ItemLevelReq] <=
If you want to keep items of a certain Ilvl you would use [Name] && [Quality] && [Level]