What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

[Plugin Addon] "Item Rules" with a file based scripting language

can u guys post your rare ring/amulet loot setting?
I got too many trash by the default rules - -
thx a lot
 
alexglade said:
can u guys post your rare ring/amulet loot setting?
I got too many trash by the default rules - -
thx a lot
Click to expand...

I would love this along with better rules for quivers - so if anyone got that, please share - would be MUCH appreciated :D!
 
darkfriend77 said:
hi guys ... sry ...

i forgot to tell jubisman (Unified Giles) about the interpreter.init() command that needs to be in the OnEnable() GilesPlugin ... to get item rules readed on each plugin enable ...

the actul version should work now ...
Click to expand...

I may be missing something, but even with your newest 1.0.1a (with init() being initialized in the onenabled() section), the bot still just stands in town. I have to stick with .39 to get anything working.
 
should be fixed now .... the init() in the interpreter needed also to be uncommented ^^

Code: 
// +--------------------------------------------------------------------------------------+
// |   __|  |  |    \     \ |   __|  __|  |      _ \   __| 
// |  (     __ |   _ \   .  |  (_ |  _|   |     (   | (_ | 
// | \___| _| _| _/  _\ _|\_| \___| ___| ____| \___/ \___|                                                        
// +--------------------------------------------------------------------------------------+
// | 1.02a:
// | - changed [DMGFACTOR] = attackspeed + critchance*2 + critdmg/5
// |   ... sry for that change ... but it seems more accurate now ..
// |   ex. item has 6% [CRIT%], 50% [CRITDMG%], 7% [AS%] & 60 [AVGDMG] ... DMGFACTOR would be ..
// |	   = 12 + 10 + 7 + 3  = 32
// | - hard rare rules for rings and amulets ... check before u use
// +--------------------------------------------------------------------------------------+
 
Eeek, the changes to [DMGFACTOR] is giving me a headache, have to go back and change all the rule scores again ><
 
darkfriend77 said:
should be fixed now .... the init() in the interpreter needed also to be uncommented ^^

Code: 
// +--------------------------------------------------------------------------------------+
// |   __|  |  |    \     \ |   __|  __|  |      _ \   __| 
// |  (     __ |   _ \   .  |  (_ |  _|   |     (   | (_ | 
// | \___| _| _| _/  _\ _|\_| \___| ___| ____| \___/ \___|                                                        
// +--------------------------------------------------------------------------------------+
// | 1.02a:
// | - changed [DMGFACTOR] = attackspeed + critchance*2 + critdmg/5
// |   ... sry for that change ... but it seems more accurate now ..
// |   ex. item has 6% [CRIT%], 50% [CRITDMG%], 7% [AS%] & 60 [AVGDMG] ... DMGFACTOR would be ..
// |	   = 12 + 10 + 7 + 3  = 32
// | - hard rare rules for rings and amulets ... check before u use
// +--------------------------------------------------------------------------------------+
Click to expand...

in files is still:

return item.Stats.AttackSpeedPercent / 2 + item.Stats.CritPercent * 2 + item.Stats.CritDamagePercent / 5 + (item.Stats.MinDamage + item.Stats.MaxDamage) / 20;

so as/2 + crit*2 + critdmg/5 + avgdmg / 20
 
how to I prevent this plugin pick up a lot of trash quiver that doesn't have right stat ( Strenght, intel instead Dex ) ?
 
htnt7919 said:
how to I prevent this plugin pick up a lot of trash quiver that doesn't have right stat ( Strenght, intel instead Dex ) ?
Click to expand...

just repair offhand section...

// +---------------------------------------------------------------------------+
// | -- Quivers
[QUALITY] == Rare && [TYPE] == Quiver # [DEX] >= 150 && [AS%] >= 15 && [CRIT%] >= 8 && [MAXDISCIP] >= 9 # [KEEP]
[QUALITY] == Rare && [TYPE] == Quiver # True # [TRASH]

// +---------------------------------------------------------------------------+
// | -- Mojos
[QUALITY] == Rare && [TYPE] == Mojo # [INT] >= 100 && [CRIT%] >= 8 && [MINDMG] >= 60 && [MAXDMG] >= 300 && ([MAXMANA] >= 80 || [MANAREG] >= 9) # [KEEP]
[QUALITY] == Rare && [TYPE] == Mojo # True # [TRASH]

// +---------------------------------------------------------------------------+
// | -- Orbs
[QUALITY] == Rare && [TYPE] == Orb # [INT] >= 100 && [CRIT%] >= 8 && [MINDMG] >= 60 && [MAXDMG] >= 300 # [KEEP]
[QUALITY] == Rare && [TYPE] == Orb # True # [TRASH]

// +---------------------------------------------------------------------------+
// | -- Shields

[QUALITY] == Rare && [TYPE] == Shield # [MAXSTATVIT] >= 150 && [CRIT%] >= 8 && [LIFE%] >= 8 && [ALLRES] >= 60 # [KEEP]
[QUALITY] == Rare && [TYPE] == Shield # True # [TRASH]
 
Can anyone give an update on how strict these loot rules are. Are they only for Yellows, im assuming that all legendaries still have to be filtered by hand?
I am familiar with d2's pickit files so I was wondering if their was a guide to set this up anywhere or a pre-set file (im assuming the one on the original post is the pre-made file with decent settings) to use. Also will this item rules files work with RU client?
 
I'd appreciate if someone could upload a russian translated dis for the legendaries and keep it on the svn since alot of users do have mixed clients.

I remember reading about someone who translated it, would be great if it was uploaded so the OP of this thread could keep it as a sticky,

Cheers
 
tOAsD said:
Do I need to check "Use Custom Loot Rules" in GilesTrinity?
Click to expand...

I was wondering the same thing because I can't get it to stop trashing set and legendary items.

[GilesTrinity] ItemRuleSet: Vile Ward [shoulderPads_norm_unique_03-219] = (TRASH)
[GilesTrinity] ItemRuleSet: Natalya's Embrace [Cloak_norm_set_03-265] = (TRASH)
 
VDBBot said:
I was wondering the same thing because I can't get it to stop trashing set and legendary items.

[GilesTrinity] ItemRuleSet: Vile Ward [shoulderPads_norm_unique_03-219] = (TRASH)
[GilesTrinity] ItemRuleSet: Natalya's Embrace [Cloak_norm_set_03-265] = (TRASH)
Click to expand...

the bot only keeps good legendary rools ... at least it should ... if u want to keep each legendary/set ... then ...uncomment the line in legendary.dis at the begining ... that will keep all legendarys/set!!!
 
darkfriend77 said:
the bot only keeps good legendary rools ... at least it should ... if u want to keep each legendary/set ... then ...uncomment the line in legendary.dis at the begining ... that will keep all legendarys/set!!!
Click to expand...

I left the following in. Are you saying I should remove it?

// keep all legendarys and special items
// this is a saftey line ... as long it isn't removed it will keep all items
// specifyed by the rule ... the action of commenting it out
// will apply all following rules ... this set of rules is no where of complete
//[QUALITY] == Legendary || [QUALITY] == Special # True # [KEEP]

// keep all Weapon for now
//[QUALITY] == Legendary && [BASETYPE] == Weapon # True # [KEEP]

// keep all Armor for now
//[QUALITY] == Legendary && [BASETYPE] == Armor # True # [KEEP]

// keep all jewelerys for now
//[QUALITY] == Legendary && [BASETYPE] == Jewelry # True # [KEEP]
 
You must log in or register to reply here.
Back
Top