Problem - FIXED: Warrior issues with new patch

[rodd996]

I am using mac v7.6.5,problem started after last set of patches


I am having issues with my warrior using any disc to pull with. Provoke, bellow, stone throw ect. Non of them work for pulling. There is also a pretty large delay if using melee to pull mobs with. I do not have this issue when using casters to pull however.

I should also add if I replace the mac file with one 3 patches ago this issue is no longer the case

I am also having a problem with the looting as well it quickly speed loots and doesn't pick up anything about 3/4th of the time. even if it goes back 20x it just wont pick up the items on the sell or keep list.

Thanks for the great job you all do for the people that use this service

 

[scotsbiker]

Re: Warrior issues with new patch

try latests kissassist 7.6.6 been a few fixes n tweeks

 

[rodd996]

Re: Warrior issues with new patch

Nope still doesn't work correctly. Can't use any of the above abilities to pull with

have to use 7.4.1 in order to get the pulls to work

 

[Maskoi]

Re: Warrior issues with new patch

open kiss in an editor and find this line

/if (${Me.CombatAbility[${castWhat}]} && !${Me.CombatAbilityTimer[${castWhat}]} && ${CombatAbilityReady[${castWhat}]}) {

change it to this

/if (${Me.CombatAbility[${castWhat}]} && !${Me.CombatAbilityTimer[${castWhat}]}) {

see if that works

 

[rodd996]

Re: Warrior issues with new patch

It took me a while to find the code but yes, this fixed the pull issue.. thank you very much

Still having the loot issue where as I loot occasionally I have items that even though they are on the loot file listed as sell, I am unable to loot it. Even if it tries to loot it over and over again. about every 3rd mob has at least 1 item that does this

 

[Maskoi]

Re: Warrior issues with new patch

are they lore? do you them defined in your loot.ini?

 

[ctaylor22]

Re: Warrior issues with new patch

It took me a while to find the code but yes, this fixed the pull issue.. thank you very much

Still having the loot issue where as I loot occasionally I have items that even though they are on the loot file listed as sell, I am unable to loot it. Even if it tries to loot it over and over again. about every 3rd mob has at least 1 item that does this

I noticed the same problem on my enchanter yesterday, could not get her to loot a Dream Sapphire. I had it set to sell as well I changed it to keep. Not sure if that fixed it or not, but so far so good.

 

[Maskoi]

Re: Warrior issues with new patch

Still may be a bug or 2 with new compile. there is a new release dealing with item tags. i will try to get that up today. it may solve the issue.

 

[r0rb]

Re: Warrior issues with new patch

I also am having issues with looting dream sapphires, sometimes they loot sometimes they don't.

 

[rodd996]

Re: Warrior issues with new patch

I am having issues looting things from alligator eggs, sections of fine snake pancreas, pearlescent crocodilian tooth, misc gems, as well as misc pieces of armor. It seems to be random but when it happens it just refuses to do as the loot file directs it to do with the loot.

 

[Maskoi]

Re: Warrior issues with new patch

There are still some bugs in the source code since the release of the new expansion. Expect a new compile in the next day or 2 with a fix.

 

[rodd996]

Re: Warrior issues with new patch

Found the issue, somewhere along the line the settings from the top of the page in the loot file duplicated itself to the end causing a conflict. Corrected and works great.. Thank you

 

[TreeHuginDruid]

Issue resolved / Problem being closed: RE: Code issue with combatabilityready check. Code fixed and posted on download thread.

 

[Maskoi]

The actual fix was posted by lanceval

this :

/if (${Me.CombatAbility[${castWhat}]} && !${Me.CombatAbilityTimer[${castWhat}]} && ${CombatAbilityReady[${castWhat}]}) {

should be - Me. added to ${CombatAbilityReady[${castWhat}]}

/if (${Me.CombatAbility[${castWhat}]} && !${Me.CombatAbilityTimer[${castWhat}]} && ${Me.CombatAbilityReady[${castWhat}]}) {

 

[TreeHuginDruid]

Aye Aye .. thanks to lanceval for catching it .... issue still resolved and updated code pushed / archived.

The actual fix was posted by lanceval

this :

/if (${Me.CombatAbility[${castWhat}]} && !${Me.CombatAbilityTimer[${castWhat}]} && ${CombatAbilityReady[${castWhat}]}) {

should be - Me. added to ${CombatAbilityReady[${castWhat}]}

/if (${Me.CombatAbility[${castWhat}]} && !${Me.CombatAbilityTimer[${castWhat}]} && ${Me.CombatAbilityReady[${castWhat}]}) {