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

TheDo · Jan 23, 2013

Logviewer should be there and i am not sure but i think its called anotherlogviewer

PainfulDeath · Jan 23, 2013

TheDo said:
Logviewer should be there and i am not sure but i think its called anotherlogviewer

True that.
I am dumb/blind once again -_-

PainfulDeath · Jan 23, 2013

Ok, I've tried using the logviewer. After it crashes for the first time - it refuses to open again ever -_-
For me it crashed while trying to load my 2mb log (which I can't attach due to forum restrictions).

After some looking through it by hand I now know for a fact that it has been trashing all the legendaries by my clean up rule, not triggering any of the actual legendary check lines. What's really strange my russian leg file works fine at my home PC (I tested it ofc) and correctly sorts through legs, but when I move the DB folder to another PC - it doesn't work. Also the dis files on that other PC when opened doesn't contain cyrillic symbols and instead contain jibberish (some codepage problems on that pc?.. dunno, but it has always been this way and it worked despite this.) but now it doesn't work. What changed?

t0b1as · Jan 23, 2013

[10:54:35.021 N] Demonbuddy v1.0.1309.298 started
[10:54:36.164 N] Logging in...
[10:54:36.522 N] Attached to Diablo III with pid: 1236
[10:54:36.564 N] Flashing window
[10:54:38.635 N] Compiler Error: c:\Users\Tobias\Desktop\DemonBuddy\Plugins\GilesTrinity\AbilitySelector.cs(19,46) : warning CS0618: Zeta.Internals.Actors.DiaActivePlayer.GetHotbarPowerId(Zeta.Internals.Actors.HotbarSlot) is verouderd: This function is obsolete and will be removed in a future build, please use ZetaDia.CPlayer.GetPowerForSlot instead.
[10:54:38.635 N] Compiler Error: c:\Users\Tobias\Desktop\DemonBuddy\Plugins\GilesTrinity\GilesTrinity.cs(36,44) : error CS1061: Zeta.Internals.Actors.DiaActivePlayer bevat geen definitie voor Attack en er is geen extensiemethode Attack gevonden waarmee het eerste argument van het type Zeta.Internals.Actors.DiaActivePlayer wordt geaccepteerd (mogelijk ontbreekt er een gebruiksinstructie of een assembly-verwijzing)
[10:54:38.635 N] Compiler Error: c:\Users\Tobias\Desktop\DemonBuddy\Plugins\GilesTrinity\Movement.cs(458,17) : warning CS0219: De variabele maxZDiff is toegewezen maar de waarde ervan wordt nooit gebruikt
[10:54:38.635 N] Compiler Error: c:\Users\Tobias\Desktop\DemonBuddy\Plugins\GilesTrinity\RefreshDiaObject.cs(1093,17) : warning CS0219: De variabele rangedMinimumStackSize is toegewezen maar de waarde ervan wordt nooit gebruikt
[10:54:39.976 N] Current bot set to Order Bot
[10:54:39.977 N] Loaded profile YAR Profile Kickstart: Ultimate SkyHigh Max v1.0.xml

I am getting this error. I did this with a fresh install of DemonBuddy.
What am I doing wrong?

PainfulDeath · Jan 23, 2013

More feedback on legendary + russian.
It seems that since your last "fix" to regex it now reads the "type" in Russian in the "Name field. Hence all of my problems with the leggies recently.
For example:

Code:

201301221406400820.asdf;LOG;TRASH;[KEY]:-1897987947;[BASETYPE]:Armor;[TYPE]:MightyBelt;[QUALITY]:Legendary;[NAME]:Мощныйпояс
;[LEVEL]:63,00;[ONEHAND]:False;[TWOHAND]:False;[UNIDENT]:False;[INTNAME]:Belt_norm_base_flippy-14165;[STR]:268,00;[INT]:60,00;[LS%]:2,90;[ALLRES]:75,00;[ARMOR]:352,00;[ARMORTOT]:352,00;[MAXFURY]:14,00;[MAXSTAT]:268,00;[MAXSTATVIT]:268,00;[STRVIT]:268,00;[INTVIT]:60,00;[TOTRES]:75,00;[DEFSTATS]:2,00;[QUALITY]=="Legendary"->[TRASH]

Notice [NAME]:Мощныйпояс. That's translated as [NAME]:Mightybelt instead of what should be [NAME]:Lamentation(or IK belt, w/e that was). This goes on throughout all of my 1.5 week of logs. I knew this wasn't jsut bad luck, lol -_-

PainfulDeath · Jan 23, 2013

It doesn't seem to be that particular regex line, I've reverted it to te original + custom fix with russian characters the result is still the same. The parser of the item populates the NAME field with the value from TYPE field.

PainfulDeath · Jan 23, 2013

I tested the exact same DB folder (copied it) back on my home PC and it reads the Name properly on all legendaries. I am baffled as to what's going on. It definitely was not doing this before the 220 version.

boombaqc · Jan 23, 2013

This is support specific unid Legendary ?
or
Are u planning to do it ?
or
Work but only for donator ?

Thx

darkfriend77 · Jan 23, 2013

Roleplayer said:
Ok, I've tried using the logviewer. After it crashes for the first time - it refuses to open again ever -_-
For me it crashed while trying to load my 2mb log (which I can't attach due to forum restrictions).

After some looking through it by hand I now know for a fact that it has been trashing all the legendaries by my clean up rule, not triggering any of the actual legendary check lines. What's really strange my russian leg file works fine at my home PC (I tested it ofc) and correctly sorts through legs, but when I move the DB folder to another PC - it doesn't work. Also the dis files on that other PC when opened doesn't contain cyrillic symbols and instead contain jibberish (some codepage problems on that pc?.. dunno, but it has always been this way and it worked despite this.) but now it doesn't work. What changed?

are u using any other plugins? ... like buddystats? and what kind of names are in ur log for legendarys .... ? what version are u using?

darkfriend77 · Jan 23, 2013

Roleplayer said:
It doesn't seem to be that particular regex line, I've reverted it to te original + custom fix with russian characters the result is still the same. The parser of the item populates the NAME field with the value from TYPE field.

this is the name bug .... there are a few possibility why this happens ....

1. ur using a demonbuddy version where the name is chached for example .295 and lower ... with a beta version from the itemrules donators repository -> solution use either the newest DB version ... or and older itemrules version
2. ur using buddystats .. buddystats used to get the name from unidnetified items ... which was causing also the name bug ...
3. ... an other combination ^^

this build should fix ur problem ...

http://www.thebuddyforum.com/demonb...e-demonbuddy-demonic-tuesday-build-298-a.html

Changelog .298
Alot of performance bottlenecks fixed.
Tal rasha's brace and some other legendary belts now has the correct item type / base type.
Loot scoring added, more information can be found here: Item Weights QuickStart guide
Item rules are now reloaded when you start the bot.
MoveToMarker tag added can be used for moving to markers. example: <MoveToMarker questId="1" markerHash="-4324543" />
Pause Bot and Force Townrun buttons added to the gui and the tray icon.
Now ignores shrines if they are too far below or above the player's z-axis.
No longer caches ACDItem.Name for unidentifed items.
No longer caches ACDItem.ItemLink for unidentifed items.

narc0tix · Jan 23, 2013

Was HappyAuction removed from the donator repository? For some reason, it's not showing up for me.

PainfulDeath · Jan 24, 2013

darkfriend77 said:
this is the name bug .... there are a few possibility why this happens ....

1. ur using a demonbuddy version where the name is chached for example .295 and lower ... with a beta version from the itemrules donators repository -> solution use either the newest DB version ... or and older itemrules version
2. ur using buddystats .. buddystats used to get the name from unidnetified items ... which was causing also the name bug ...
3. ... an other combination ^^

this build should fix ur problem ...

http://www.thebuddyforum.com/demonb...e-demonbuddy-demonic-tuesday-build-298-a.html

Changelog .298
Alot of performance bottlenecks fixed.
Tal rasha's brace and some other legendary belts now has the correct item type / base type.
Loot scoring added, more information can be found here: Item Weights QuickStart guide
Item rules are now reloaded when you start the bot.
MoveToMarker tag added can be used for moving to markers. example: <MoveToMarker questId="1" markerHash="-4324543" />
Pause Bot and Force Townrun buttons added to the gui and the tray icon.
Now ignores shrines if they are too far below or above the player's z-axis.
No longer caches ACDItem.Name for unidentifed items.
No longer caches ACDItem.ItemLink for unidentifed items.

Thanks for the answer. I will try updating DB first (but I am pretty sure I was using a beta which already has all those changes)
So you say your itemrules are incompatible with buddystats? That's a bummer =( I am indeed using those and I like it =(

thekingkong · Jan 24, 2013

Caught the bot skipping archon gauntlets...is that normal? Im sure this isnt the first time either. I am using hard script.

tom157 · Jan 24, 2013

Hard rules:

Code:

[QUALITY] == "Legendary" && [NAME] == "Inna's Temperance" # [DEXVIT] > 200 || [INTVIT] > 90 || [TOTRES] > 50 || [LIFE%] > 5

Imho it should keep all inna's temperance because the cheapiest is 3.5mln on the eu now.

Code:

[QUALITY] == "Legendary" && [NAME] == "Inna's Temperance"

PainfulDeath · Jan 24, 2013

tom157 said:
Hard rules:

Code:

[QUALITY] == "Legendary" && [NAME] == "Inna's Temperance" # [DEXVIT] > 200 || [INTVIT] > 90 || [TOTRES] > 50 || [LIFE%] > 5

Imho it should keep all inna's temperance because the cheapiest is 3.5mln on the eu now.

Code:

[QUALITY] == "Legendary" && [NAME] == "Inna's Temperance"

Have you read what hard rules are supposed to be? It's target is 10+ mil, not 3.5

Though that rule seems incomplete to me. STR innas and STRVIT innas are worth alot too.

tom157 · Jan 24, 2013

Roleplayer said:
Have you read what hard rules are supposed to be? It's target is 10+ mil, not 3.5

Though that rule seems incomplete to me. STR innas and STRVIT innas are worth alot too.

I havent read about 10+ mil, where it is?

I'm wondering because from my experience most of the hard rules keep items worth 500+ k / 1+ m.

No hard feelings.

Kakaru · Jan 24, 2013

FIRST PAGE:
- rules
|- soft only best selling stuff is beeing pickt up probably 1+ Million
|- medium only best selling stuff is beeing pickt up probably 5+ Million
|- hard only best selling stuff is beeing pickt up probably 10+ Million

tom157 · Jan 24, 2013

If that was (and still is because there is no mention about 10+ in the first post) the purpose of hard rules, most of them need huge modifications because they really are 1+ and even below.

tonari · Jan 24, 2013

tonari said:
Could someone help me how to set it so id doesn't pick up 2h weapons, rare heads and chests?
I have tried editing the pickup.dis but still didn't manage to get it to work.
Thanks for the help.

Kakaru said:
[QUALITY] == "Rare" && [BASETYPE] == "Weapon" && [TWOHAND] -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Helm" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Chest" -> [IGNORE]

Class specific heads and chests:
[QUALITY] == "Rare" && [TYPE] == "SpiritStone" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "VoodooMask" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "WizardHat" -> [IGNORE]
[QUALITY] == "Rare" && [TYPE] == "Cloak" -> [IGNORE]

After some days, this still doesn't work. Tried putting it in pickup.dis and sof/hard.dis.

So anyone has an idea where to put all rare 2handers, chests,heads and all belts to ignore list?

Kakaru · Jan 24, 2013

They do work as they are in my pickup.dis file and I'm not getting any of those items.

Did you read the instructions? Are you modifying the correct pickup.dis? Or better yet, did you activate it the rules in the first place?!?

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

New Member

Member

Member

Member

Member

Member

Member

New Member

Member

Member

New Member

Member

New Member

New Member

Member

New Member

New Member

New Member

New Member

New Member