Some Stuff in the ini file is getting scuffled around, and a routine was added to clean up old entries that need to be removed.
New section is being added: [Spells] There are several entries from the [General] section that are getting moved to this section,
and [MySpells] section is getting merged with the new section.
**Note: It is not recommended to revert to an older version of kiss after running this version. YOU HAVE BEEN WARNED!
There is now an option for using DanNet. DanNetOn=0/1 Default is 0. If both EQBCOn and DanNetOn are on, DanNet is turned off and Kissassist
defaults to EQBC.
What does turning on DanNet change:
Anything that the Kissassist_Buffs.ini file is used for, will use DanNet queries now.
Messages sent through DanNet show in the MQ window.
Does NOT unload MQ2Eqbc plugin. You can still use all your hotkeys that are dependant on EQBC.
Whats New:
Debug for chainpulling.
Use /debugchainpull to toggle messages on and off. /debugchainpull 1 and /debugchainpull 0 work as well.
/debugchainpull is not part of DebugAll, this is intentional and is to be used separately from all other debugging.
DebugChainPull Messages and explanation(s):
Chain Pull Failed 0:
Role is NOT Puller, or ChainPull=0
Chain Pull Failed 1:
PullHold is on, or more than 1 mob in camp, or Second autohater Xtarget has mob ID, or Named is in camp.
Chain Pull Failed 2:
No Target, or Current Targets HP's not low enough.
Chain Pull Failed 3:
No Mob ID returned from FindMobtopull, or pull Experience check turned on and pullmob is to far from camp,
or Current CombatTarget has ME targeted, or My aggro is too high to leave camp.
This is to help when trying to figure out, why your puller is not doing what you think they should be doing.
-------------------------------------------------------------------------------------------------------------------------------------------
You can now maintain a list of characters to buff. Kiss will buff anyone on the list.
This is in addition to what kissassist buffs already.
New Command: /TooBuffList
The new command needs 2 parameters.
First parameter is an action to take and can be 1 of the following: add, remove, reset, or clear
Second Parameter is the ID of the character you want to add to the list.
Read on. A full explanation of these parameters is listed below.
Using this command will allow you to add anyone to the list.
In addition to the command, there were events created to trigger adding to the list by an outside source.
To trigger the events, part of the message must be "Buffs Please!" exactly like that without the double-quotes.
Example:
If I want to get buffs from another character. I would send them a tell:
/tell SomeCharacter Buffs Please!
You could also just run into the middle of a group and use:
/say Buffs Please!
Now before everyone freaks out about the event-driven option, there have been some additional checks put in place.
So not just anyone can run in and get added to your buff list.
Here is what is checked to ignore characters that do NOT qualify to be added to the list:
This only applies to the event-driven option and not the direct /TooBuffList command.
The event ignores you if you:
Are in my current group or NOT a Member of my Raid, and NOT a member of my fellowship, and NOT a member of my guild, and NOT on my friends' list.
So basically you cannot be in the same group, and you must be in ONE of the mentioned lists(Raid, Fellowship, Guild, Friends).
I went through all that first, to explain the /TooBuffList parameters.
First parameter can be:
add - Add to list.
remove - Remove from list.
clear - clear the list and start over.
reset - This one checks the list and will remove anyone on the list
that doesn't show up as a valid spawn in the current zone.
Second parameter can be:
Any spawn ID. Use your common sense and don't go adding NPC's pets and stuff.
Special note here: If you have DanNet turned on and the spawn is found in the DanNet peers[all] list.
Then the spawn is ignored and NOT added to the list.
-------------------------------------------------------------------------------------------------------------------------------------------
Here is a list of some of the miscellaneous changes:
Added Additional check-in CastBuffsSpellCheck if the spelltocast is an AA and has a trigger spell.
Like Lupine Spirit AA, the Buff is a different name spirit of Tala'Tak.
FD/Invis issue when chain pulling.
Buffs routine not being called when chain pulling and no mobs in camp
Issue was CombatReset was never getting called when chain pulling.
Problem with Non-Melee(MeleeOn=0)/Non-DPS(DPSOn=0) toons calling combatreset continuously.
Found issue in Combatreset where pullreset was being called even if you are not a puller.
Also changed where combatreset is being called, and only if CombatStart was set on.
Pull routine is now aware of the puller being FD as well as sitting.
Add code to use new BlockedBuff and BlockedPetBuff member.
No longer have to open the Blocked Buff Window.
I moved the pipe(|) from the front of the string to its proper location so the string ends with the Pipe(|).
Example: Was |Buff1|Buff2|Buff3 Now: Buff1|Buff2|Buff3| <-- This is the proper format.
Changes made to CheckIniBuffs, WriteBuffs, WriteBuffsMerc, and WriteBuffsPet to use the new format.
Made some code tweaks to get rid of some /goto's and :LineLabels
There were other changes, but I forgot to make note of them as I made the change.
