Question - Future "must have" features for KissAssist ?????

[TreeHuginDruid]

I've been a member of this community since 2004...
I've been writing and contributing macros to this community since that time...
I've been on the payroll and actively working for RedGuides as a developer for years as well....
I've seen the evolution of KissAssist from it's initial inception.. while helping to establish it as the beautiful macro must have it is today....

And one thing I can say for certain... is that there are only two real factors that have played a role in the expansion/growth of Kiss since its beginning:

1) In game additions/changes that establish "must have" features for Kiss to handle and automate.
2) User/community input of what functions and "must have" features they request to make their life easier in game.


This has been the general norm for the entire life history of Kiss.
There have been tons off "requests" to add certain features in over the years, and some have been really great requests.... which we delivered for you.
While others simply were only to accommodate the need of one or two people and did not warrant any real consideration on the dev team's part.

And still other requests were so widely wanted, but did not fit into the scope of KissAsssist itself.. we (the devs/creators) took it upon ourselves to deliver your needs in the form of separate macros .. Example: KeepToonsBuffed.mac (For the express usage of Pl'ing lower toons).

I have read through all the requests in the past several months.. and a few of them were so overwhelmingly beneficial.. that the "Kiss Team" made it a priority to make these requests a reality.
Example(s): Additional options for loading spell-sets / spells/songs .... Incorporating rez level accept limits..... Clicky Item pulling .... Clicky Item usage for DebuffAll procedures ..... PetTank, PullerPetTank & HunterPetTank roles

So I feel it is a good time to now pose the following question to the community:

What additional NEW features.... or current feature enhancements do you feel are a "MUST HAVE" for future versions of KissAssist.

Keep in mind.... the same rule appies... its the dev teams decision if a new or enhanced feature is truly worth the time and effort to bring to life... but if its a great idea... we most likely will agree and slate it for development.

So please, add to this thread your most wanted feature or enhancement.... one that you simply "must have" ... and for those who don't have an idea to contribute.... please show your agreement with those who do post ideas by giving them "THANKS" ... the more thanks we see on an idea... the better we know that others share in wanting that idea to come to life as well.

I'm pushing for the THANKS method to show your approval/vote for an idea.... rather than asking you to add a reply on an idea.... because it CAN and WILL get this thread bloated with back and forth comments on each of the separate ideas that are posted.....

a simple "THANKS" to the user who posts the feature/enhancement you also want is all it takes to let us know its value.

Looking forward to seeing the ideas....
and remember the most important thing .. this is KISS .... ( Keep It Simple Stupid ).

Your friendly neighborhood tree humper.....
( Keep the oak tree's knot-hole away from me !!! )

 

[kaen01]

buffs, dps, burn

and other sections that take a me/ma/melee/mob

have a common system

me, pet, ma, mt, puller, melee, caster, merc, name.

all with ! infront to not target that option.

so i would like to cast buffs on all members except mercs buff1=bufftocast|!merc

or a specific name each time, no matter what that person is tagged |monkname

******
Keep in mind we will NOT add any functionality that will encourage the use of Character Names in any of the Kiss ini files.
******

 

[Sinn69]

more that 1 rez option for druids and shamans, more xtar heal slots would be great.

 

[toots]

I would appreciate an active disc section that had conditionals. It would be nice to speed up and shrink my dps section by putting defensive discs or dps discs somewhere else.


*****
This may be possible using the MASH tag. Anything with the MASH tag is moved to a different array and removed from the DPS array. We may need to move the /call to the Mash routine to a different location, but will need to give users the option to choose the priority of the Mash routine /call over the DPS section. Like we did with the DebuffAll routine.
*****

 

[Mara]

<sub>Ability to interrupt a cast to use a heal.

Ideally it would stop a cast to use a heal (or even another spell)

Eg.
Druid is nuking and mid cast when squishy tank takes spike damage. As it is at the moment druid will finish the cast before using a heal potentially causing a wipe.

With this they'd stop the cast to use a heal based on the heal section. Maybe add two global hp % triggers (group % single %) to determine if you should stop the cast.</sub>

 

[VorpalChicken]

Re: Future &amp;quot;must have&amp;quot; features for KissAssist ?????

<sub>Ability to interrupt a cast to use a heal.

Ideally it would stop a cast to use a heal (or even another spell)

Eg.
Druid is nuking and mid cast when squishy tank takes spike damage. As it is at the moment druid will finish the cast before using a heal potentially causing a wipe.

With this they'd stop the cast to use a heal based on the heal section. Maybe add two global hp % triggers (group % single %) to determine if you should stop the cast.</sub>

I like this idea, maybe a an option that allows you to prioritise healing over DPS or vice versa, something to that effect

- - - Updated - - -

Also adding in the ability to do /<command> in say DPS, as was shown in another post, just without having to edit my kissassist.mac to do it

https://www.redguides.com/forums/threads/55331-Issuing-slash-(-COMMAND-)-in-KissAssist?p=327262&viewfull=1#post327262

 

[DarkDevil]

I would like to see:

Instead of

DPS32=Force of Ice|99|Weave
DPSCond32=TRUE

A section dedicated to Weave
That works during GlobalCoolDown ONLY when set to 1

[WEAVE]
GlobalCoolDown = 0/1
Burn = 0 (Weave the following spells, list)
DPS32=Force of Ice|99
DPS33=Force of Will |99

Burn = 1 (Weave the above and add the below)
DPS34=Force of Flame |99
Add clickies as well to the WEAVE section
-------------------------------------------------------------

Line commands while KA is running.

/Burnon
/Burnoff
-----------------------------------------------------------------
-------------------------------------------------------------------
I have noticed that the first time you start KA, if will do a full check of the INI file.
BUT
If you make changes to that file, and restart KA, it does not, so..

/Kissassist checkall

To clear and recheck as if it was the first time KA was loaded.

-----------------------------------------------------------------------

Thanks.

 

[nicesandwiches]

Unless I haven't read it, i want to be able to click on some hotbuttons that allow my to:

Toggle Melee (stop and start again)
Toggle songs (on Bard (stop and start again)

At the moment, when assisting (non-af) fading memories does not stop everything even after setting up a macro. Also, I will still keep twatting on the mob. I'm sure i just haven't read the instructions properly but /backoff and meleeoff does not seem to do what I want it to do...

*****
There were some changes to the backoff routine this last update to Kiss. Not sure if you have tried the /backoff since the latest changes. Check out this post for more information:

https://www.redguides.com/community/threads/55091-Anyway-to-clear-a-target-once-combat-starts?highlight=%2Fbackoff
*****

 

[vivviv]

forwarding of tells to gmail

 

[eqtrader74]

Directional Pulling - Have a line in the character ini pulling area that does "PullDirection=East" or such. Then the puller will only target mobs to the east of camp. Would make moving camp or trying new spots faster.

Priority Pulling - Option to use the KA.ini zones MobsToPull section in list order. So you can list named, then placeholders, then trash or such. If it already does this, my apologies, I hadn't tried it yet.

 

[shadowfall]

Better mez routine for bard mez would be great

 

[Tone]

My two patches that I've been thinking through:
1 -- Puller stop fucking pulling when people have rez sickness yo!
2 -- XTarget allow the section to have XTargetSize= and be able to list it out to 10-15


Raid Setup that gets weird:
Have a paladin outside the maintank group and set them to assist the maintank ... because of the healing section it's like they never want to do anything but keep their assist targeted.
I typically end up making paladins heal bots, or just set them up as their own tank, and hope for the best on trash pulls lol.

 

[toots]

Also, build breather into the Mac. It works well with holies and shits, but I can think of very few classes who don't need this ability on lockdown.

 

[TreeHuginDruid]

Also, build breather into the Mac. It works well with holies and shits, but I can think of very few classes who don't need this ability on lockdown.

Try this instead:

BuffsCOn=1
Buffs1=Breather|End|20
BuffsCond1=${Me.CombatAbilityReady[Breather].ID} && ${Me.PctEndurance} < 20

 

[Skyjet2000]

Raid Setup that gets weird:
Have a paladin outside the maintank group and set them to assist the maintank ... because of the healing section it's like they never want to do anything but keep their assist targeted.
I typically end up making paladins heal bots, or just set them up as their own tank, and hope for the best on trash pulls lol.

Add the main assist to your Xtarget window, will fix this.

 

[aspire2008]

I think the biggest thing on my list would be support for multiple Advpaths (you can look at Devestator's code here to see how he does it). Where it runs the path, if it doesn't find any mobs you can run the next path , then next etc.

As there are quite a few zones mq2nav doesn't work well in, usually maze like zones seem to be the ones that give a lot of issues with mq2nav pulling.


Just a minor thing, commented on it in another forum thread, but adding "|stopdisc" value to the DPS section.

https://www.redguides.com/forums/th...-in-KissAssist?p=327493&viewfull=1#post327493

******
The multiple advpath pulling has already been done, but was never adopted by the previous developer(s). The way it worked was the pull routine searched all paths in the ini for a generic name. Lets say you set PullPath=APath and in the advpath file you had paths named, APath1, APath2, APath3, APath4, and APath5. The macro would check the first waypoint in each of the paths and if the first waypoint was within 15 units of your camp location. The path was added to the list. The only limitation is that the total number of waypoints of all combined paths can not exceed 999.
******

 

[Tone]

Add the main assist to your Xtarget window, will fix this.

I tried that...but I'll double check and test again.

 

[Chanticleer]

Only thing I'd like to see is ability to change from kiss healing to raid healing aka main tank group


Xtargethealsonly=0/1 make this where it only heals. Target 1-whatever for raid healing

 

[LurkMcGurk]

A way to turn out of group rezzing on/off and for it to ignore corpses that they rez X amount of times as to not have it spam a nearby corpse endlessly.


When I raid I used to have 1 cleric who rezzed the whole raid, it was kinda his job - but more recent versions of Kiss he doesn't rez out of group anymore. Not really sure why but it would be nice to get a definitive option for this for those of us who box 2 or more groups

 

[EQbackagain]

I'd love for a way to use mq2nav to be able to walk a path and record it outside of the game so I don't have to worry about mobs.
A toggle to turn on invis when moving along a path would be great.

I know these aren't actually specific to kissassist though

 

[ihc385]

the ability to call short custom scripts like modbot.

 

[sabby]

/burn on and /burn off toggles as mentioned above would be absolutely amazing.

 

[Warmonger]

Fixing Mages and Enchanters breaking invis to cast auras and pet buffs.

Improving Enchanter mez routines to cast AEMez immediately when 3+ mobs are on ext target and in range.

 

[stinapina]

Better mez routine for bard mez would be great

+1

 

[eqholic]

buffs, dps, burn

and other sections that take a me/ma/melee/mob

have a common system

me, pet, ma, mt, puller, melee, caster, merc, name.

all with ! infront to not target that option.

so i would like to cast buffs on all members except mercs buff1=bufftocast|!merc
...

I shamelessly point to my thread https://www.redguides.com/community...onditions-over-buf-dps-heal-and-cure-sections. I can't stress enough how important consistency is for a pleasant user experience. For a further and partially entertaining look at it I point into a talk by Scott Meyers https://youtu.be/RT46MpK39rQ?t=2053.

This might even be a chance to simplify the code by moving the interpretation into a common sub.

 

[LurkMcGurk]

I would like to see a feature of kissassist where the Tank (or puller) forces the mob he pulls to the camp location.

A lot of the time the tank will fight a mob on the other side of a little lump or a pillar that blocks the entire groups LoS all because the mob is a few feet outside the center of the camp radius. I would like to see a feature added into kiss so that the tank won't engage the mob until he's pulled to a specific coordinate location (or relatively close to that location) - this would help prevent the tank from fighting around corners and on the other side of pillars.

Maybe even have a section in Aggro for abilities to aid this, such as, Hate's Attraction (Paladins get Divine Call), Warriors get an ability that "pulls" the target to them as well.


______________________________________________________


Another feature that would be nice is a prioritize feature as many others have pointed out here. For example, setting a few debuffs as "Get these on the mob before you do ANYTHING else" would be nice for Slow, Malo and things like that.

It would also be nice to set Hybrid healers like Dru/Sham to ignore DPS and focus primarily on healing when there's X amount of targets on the Xtarget window. Such as, oh shit we pulled 4 - druid doesn't even try dpsing now, he just focuses entirely on healing until we get down to just 2 mobs then he goes back to heal/dps

 

[eqholic]

This is not directly about a new KA feature. I think the KA code is in need of a makeover to make it easier to understand. Think about code like this: Code isn't written for the computer but for other people. This other can also be myself a few weeks later. Nobody understands if clauses that are much longer than half a line for instance. There are some that make me scroll left/right/up/down... I understand that this is partially due to the fact that mq2 doesn't allow the definition of real functions in macros. So there you have it: extend the mq2 macro language with user defined functions which leads to cleaner macro code which leads to easier extensibility of macros.

An other thing I noticed: There is a lot of code that repeats the same spawn[something] many times in a code segment. I think, and I might be wrong, that there are 2 problems with that. a) performance: spawn executes a search in the eq environment everytime I assume. b) correctness: if my previous assumption is true 2 invocations of spawn[something] are not guranteed to return the same result as mobs may spawn or die.

 

[Sum1]

This is probably easy and something I could do myself, but I'd like a way to force kiss to use heals just inside max range, if the target is not flagged as puller. Trying to raid with kiss running the clerics is proving troublesome because I need to pull the mobs closer to him in order for the cleric to heal, even though the toons are within max spell range.

 

[thx07781]

This might not be possible, but it would be great if a tank could be set to keep threat on multiple targets.

For example, have the tank attack a couple times on any mobs that aren't attacking him and aren't mez'd. This problem goes away late game when classes start to get AoE threat spells/abilities, but earlier expansions, and earlier levels it would be really nice. Maybe have the tank use the same unmezzable INI file to get a list of mobs they would need to bounce between.

That's my wishlist item!

 

[Wolfborn]

When pulling, stop trying to re-cast a resisted spell. Check agro after first cast and return to camp with mob in tow. (never seen a mob NOT agro from resisted spell)
A few wipes from this behavior just this week.
When puller brings back multiple mobs, prioritize them and put tank on the highest priority (eg.. Named, highest level, mez immune etc..)
Tank aware of mobs beating on another toon and at least target for taunt or even move to it and do the "attention getting dance".

Something to consider.
Break out some functionality into plugins.
1. Pulling
2. Mezzing
3. Buffing
4. Tanking

 

[rhb]

It may be available but I haven't seen it yet.

In the INI, if spells are written, have a /memspell function to memorize those spells written in the INI file.

Also would like a feature to only accept a certain number of rezzes in a certain amount of time. I say that because I don''t know if KISS can keep track of time, but the kill counter does so maybe it can. I've caught a few toons in a rez hole where a mob kills them repeatedly.

Set a function to pull a certain mob, similar to /addignore, /pull mob_xxx would be awesome. I suppose you would also need a radius function in there to prevent someone running across the zone as well.

Just a few thoughts

 

[TreeHuginDruid]

It may be available but I haven't seen it yet.

In the INI, if spells are written, have a /memspell function to memorize those spells written in the INI file.

Also would like a feature to only accept a certain number of rezzes in a certain amount of time. I say that because I don''t know if KISS can keep track of time, but the kill counter does so maybe it can. I've caught a few toons in a rez hole where a mob kills them repeatedly.

Set a function to pull a certain mob, similar to /addignore, /pull mob_xxx would be awesome. I suppose you would also need a radius function in there to prevent someone running across the zone as well.

Just a few thoughts

From the manual:

[SpellSet] Settings
LoadSpellSet - 0/1/2 - Option to load spellset by defined spellset name or load individual spells via [MySpells].
SpellSetName - The name of the pre-saved spell set you want to use for kiss.

Code:

LoadSpellSet=2
SpellSetName=KissAssist

If you have a spellset saved and enter in the name after SpellSetName Kissassist will load it if LoadSpellSet=1

0 bypasses all spell loading routines.
1 loads your defined SpellSetName from your INI file as usual.
2 will load specific spells in each gem slot based upon the [MySpells] section of your INI file.
If you have no [MySpells] section defined and are using option 2 for LoadSpellSet, a default [MySpells] section is created.

 

[shadowfall]

Current state of bard mez, when i pull 5+ mobs bard will not always cast ae mez he will try and single target each one then after they are mezed he will hit ae mez then remez with single target.

what it should do is when you pull 2+ mobs should ae mez then check to see if mobs are mezed if not then cast single target.

waste so much dps with him constantly mezing mobs that are already mezed with ae mez some fights the bard never even puts his melody up just keeps single target mezing large groups of mobs even when ae mez is up.

 

[aspire2008]

1) I'm not sure if this functionality exists, but if someone requests a buff, the ability to slash command the request to the buffingtoon to buff the whatever toon needs it.



Example:

/bct buffingtoonname buff "talisman of celerity" buffingthisguyname



2) Support for spell gem switching , if 2 or more spells are assigned to a spell gem, usually only applies to classes that need to load spells in and out constantly. This probably only applies to necros and shamans for most part, but loading multiple dots in and out in different gem slots.


Over both of those, I would still prefer multiple Advpaths support implementation if its possible.

 

[TreeHuginDruid]

FYI ..... If you see me give THANKS to any of the suggestions here... that pretty much means I like/love the suggestion.. and it stands a better than average shot of making into the current project management plan I'm finalizing for the next few minor .. and eventually the next major update release.

So smile if you see my "THANKS of Approval".. lol

 

[TreeHuginDruid]

Fixing Mages and Enchanters breaking invis to cast auras and pet buffs.

Improving Enchanter mez routines to cast AEMez immediately when 3+ mobs are on ext target and in range.

Will confer with Ctaylor22 .. but I thought we fixed the breaking invis crud .... i'll double check the code.. but that is an easy ass fix.... the mez crud is Chris's domain... i won't touch it lol

But you do have control over at what number and what distance you use your aemez spell in the settings... you have to tweek the settings a but depending on mobs /camp / scenario of pulls.. but I have not had issue with chanter aemezzing crowds since the 2nd to last mez overhaul chris did...

 

[EQbackagain]

Maybe this is a feature that is already implemented, maybe it isn't.

Is there the ability to issue a command via bccmd to initiate a sequence of actions ie

/bc aeburn (initiates all AE abilities on command)
/bc burn1 (initiates your main burn)
/bc burn2 (initiates a smaller burn)

When raiding these could be really useful to me.

 

[eqholic]

Maybe this is a feature that is already implemented, maybe it isn't.

Is there the ability to issue a command via bccmd to initiate a sequence of actions ie

/bc aeburn (initiates all AE abilities on command)
/bc burn1 (initiates your main burn)
/bc burn2 (initiates a smaller burn)

When raiding these could be really useful to me.

From https://www.redguides.com/community/threads/26002-KissAssist-Instructions-amp-Settings-Info

BurnText=Decepticons Attack - The text to invoke the burn event. KissAssist should read this event text from any window BUT it is highly recommend to keep this command in the MQ2 or EQBC window. Default text "Decepticons Attack"

Usage: create a hot key /echo Decepticons Attack or /bc Decepticons Attack for the EQBC users out there.
​

So it is sort of implemented, but I agree a clean /burn command would be nice.

 

[EQbackagain]

I understand that there is the single burn command. I'm looking for multiple burn options

 

[gse7en]

Using stick to autofollow is just about as bad as in game /follow with modern day CPU's. It would be awesome if there were a flag for using either of /stick or /afollow. I suppose it's even possible to use /nav, but that seems horribly spammy. I had previously thought of the benefit versus cost of implementing this. /stick absolutely is SIMPLE, which is the name of the game, but is /afollow SIMPLE? I was on the fence about it, but then KISS with conditionals was released which I say is not at all SIMPLE (but certainly a welcome feature for we advanced users).

My argument is that with using just /stick instead of autofollow, if I'm doing an LDoN with /chaseon and the pullertank isn't returning to camp, there's a pretty good chance I will fail the LDoN because characters get stuck (and not the MoveUtils kind of stuck). If I manually tell them to /afollow, I get better results, but not organic if the macro handled it. Of course, if I'm not using autonomous pulling, my hotkey of /bcga //nav id ${Target.ID} (aliased to /move) and /bcg //nav id ${Me.ID} (aliased to /mup) do quite nicely. This, however, isn't feasible if I'm over on one of my other groups who isn't doing AFK stuff.

Of course, if there's one thing I hate, it's a bloated and convoluted INI file and this would add one more line to it. Writing the changes in the script itself is easy enough, but I'm not sure how'd you implement it with the setting.