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

[nyghteyes]

An improved Cure routine, it gets stuck a lot.


*****
Can you give a more detailed example of what you mean by stuck?
*****

 

[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.

I think you are using an older version of kiss. Looks like you on 10.0.3

Upgrade please to posted 10.0.4
This should solve both the in his breaking and messing issues

 

[Fennil]

not sure if it was mentioned but i just want KA to not cast if invised, and if its in there then silent presence from shaman needs to be added cus i get killed sometimes cus my shaman or cleric(Autocleric) decide to cast when invised and break it

 

[nyghteyes]

An improved Cure routine, it gets stuck a lot.


*****
Can you give a more detailed example of what you mean by stuck?
*****

Quite often it doesnt seem to detect when it has actually cured the ailment on a group member. It will chain cast RGC after its been cured or doesnt detect it at all.

 

[DarkDevil]

Me too.
What would really be cool, is

/full burn on (Turns on every thing available)
/burn on (Turns on whatever you have listed (baby burn)
/burn off (Of course burn AA's are timed, but when the timer expires, it is often beneficial to change a few spells out, hence /burn off

 

[E9er]

Re: Future "must have" features for KissAssist ?????

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!

use /mac autowarrior he will attack all mobs in camp 1 by 1.

- - - Updated - - -

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.

In mez section you should be able to set ae mez and single target mez by numbers. Example
MezOn=1
MezRadius=125
MezMinLevel=45
MezMaxLevel=61
MezStopHPs=85
MezSpell=Apathy|2
MezAESpell=Fascination|4

This should tell it to cast ae if detects the certain number of mobs in camp.

 

[gse7en]

Most of these, please:

https://www.redguides.com/community...EqMule-Edition?p=327611&viewfull=1#post327611

 

[Skyjet2000]

DPS/Heal/Buff Priority - I'd really like to be able to set some kind of priority when KA is choosing between dps/buff/heal sections. I'd like to be able to make something like a druid stop nuking and prioritize healing first as needed. I've had wipes thanks to a druid finishing his nuke as someone was dying. I've had simliar situations with my shaman casting cannibalize when there are still targets unslowed etc, and I'd rather him focus on that first.

Back up/Secondary Main Assist! - Simply a secondary Main assist incase the first one dies. Doesn't have to have the full functionality that you would have by fully loading KA on a toon, but just a toon who can keep the party going should the MA die during a pull. I'd say one of the primary reasons for wipes for me, is my MA going down and the rest of my toons standing around getting the shit kicked out of them until heaerls run out of mana and everyone dies.

|Class tags in Buff section - Would absolutely love to be able to use buffs only on certain classes by adding something like "Buffname=Buff|Monk|Rogue" etc

Buff Stacking vs Higher level versions - Not sure if this is possible, but It'd be great if my toons would stop trying to cast a buff forever on top of a higher level version of a buff.

Resist threshold on DPS spells - Maybe a way to say if a spell is fully resisted a certain amount of times, to skip that? I know there is an immune section, but it'd fine this useful for general purpose, or short visits etc.

Full Xtarget Healing/Handling - I know this is requested a lot, so I'm assuming there is a good reason we only recently just had a second slot enabled =p. Would be great to be able to watch more people with my healers though.

Invis Command - An invis command and a choice of what to use to cast invis. "//invis" or some such and have all chars invis and hold buffs etc.

 

[Gator]

It would be nice to be able to swap to a previous versions of Kiss. I don't back up well and for some reason I am good at finding bugs.

 

[TreeHuginDruid]

OK Folks.. just a heads up...

We've been seeing some awesome suggestions that almost certainly will be put into the project plan for new minor/major revision releases.... If you see my Thanks on a suggestion... you know I'm loving it and agree it should be something I / Chris get cracking on.

We'll be accepting more suggestions for the the next few days... and closing this thread for additions but keeping it posted as a public reminder .. by this weekend.

This kind of direct feedback about what you want... and need... is what helps us developers provide a product to you that makes everyone happy.

Now go kill some dragons and stop trolling the web.. lol

 

[TreeHuginDruid]

Most of these, please:

https://www.redguides.com/community...EqMule-Edition?p=327611&viewfull=1#post327611

Uhhhhmmmmm we will look into it.

 

[toots]

That 'no' was just an autocorrect issues right?

 

[Scrublike]

For those asking for a 'rolling burn' feature, it's actually very simple. I've added it to KA myself. It just takes 2 lines:

around line 248:

/squelch /alias /rollburn /togglevariable RollBurn

This means u can toggle burn with /rollburn

around line 479:

/call LoadIni Burn RollBurn int 0

This means u can use the variable called RollBurn in the DPS section of your ini.

You can now access this RollBurn value in conditions. Here's a section of my mage ini
DPS2=Heart of Flames|100
DPSCond2=(${RollBurn} && (${Me.Buff[Elemental Union].ID} == NULL))
DPS3=Improved Twincast|100
DPSCond3=(${RollBurn} && (${Me.Buff[Twincast].ID} == NULL))
DPS4=Fundament: First Spire of the Elements|100
DPSCond4=(${RollBurn} && (${Me.Buff[Auspice of the Hunter].ID} == NULL) && (${Me.Buff[Illusions of Grandeur].ID} == NULL))
DPS5=Focus of Arcanum|100
DPSCond5=${RollBurn}
DPS6=Servant of Ro|100
DPSCond6=${RollBurn}
DPS7=Frenzied Burnout|100
DPSCond7=${RollBurn}
DPS8=Host in the Shell|100
DPSCond8=${RollBurn}
DPS9=Virulent Talon|100
DPSCond9=TRUE
DPS10=Host of the Elements|100
DPSCond10=${RollBurn}
DPS11=Deathseeker's Flameweaver Robe|100
DPSCond11=${RollBurn}
DPS12=Silent Casting|100
DPSCond12=${RollBurn}
DPS13=Elemental Union|100
DPSCond13=(${RollBurn} && (${Me.Buff[Heart of Flames].ID} == NULL))

Now I can just call /rollburn and my mage will fire discs as they pop.

NOTE: I don't really understand the alias thing, so I just set my kiss version to 0 so it re-created aliases

 

[TreeHuginDruid]

For those asking for a 'rolling burn' feature, it's actually very simple. I've added it to KA myself. It just takes 2 lines:

around line 248:

/squelch /alias /rollburn /togglevariable RollBurn

This means u can toggle burn with /rollburn

around line 479:

/call LoadIni Burn RollBurn int 0

This means u can use the variable called RollBurn in the DPS section of your ini.

You can now access this RollBurn value in conditions. Here's a section of my mage ini

DPS2=Heart of Flames|100
DPSCond2=(${RollBurn} && (${Me.Buff[Elemental Union].ID} == NULL))
DPS3=Improved Twincast|100
DPSCond3=(${RollBurn} && (${Me.Buff[Twincast].ID} == NULL))
DPS4=Fundament: First Spire of the Elements|100
DPSCond4=(${RollBurn} && (${Me.Buff[Auspice of the Hunter].ID} == NULL) && (${Me.Buff[Illusions of Grandeur].ID} == NULL))
DPS5=Focus of Arcanum|100
DPSCond5=${RollBurn}
DPS6=Servant of Ro|100
DPSCond6=${RollBurn}
DPS7=Frenzied Burnout|100
DPSCond7=${RollBurn}
DPS8=Host in the Shell|100
DPSCond8=${RollBurn}
DPS9=Virulent Talon|100
DPSCond9=TRUE
DPS10=Host of the Elements|100
DPSCond10=${RollBurn}
DPS11=Deathseeker's Flameweaver Robe|100
DPSCond11=${RollBurn}
DPS12=Silent Casting|100
DPSCond12=${RollBurn}
DPS13=Elemental Union|100
DPSCond13=(${RollBurn} && (${Me.Buff[Heart of Flames].ID} == NULL))

Now I can just call /rollburn and my mage will fire discs as they pop.

NOTE: I don't really understand the alias thing, so I just set my kiss version to 0 so it re-created aliases

Gotta admit .... loving the simplicity of it all ... however,... for those who are too scared to step their toes into the waters of the big bad scary "CONDITIONALS" lake .... its a moot issue.

Its got the THD "Thanks of Approval".. so its on the radar for addition to the project management itinerary.

Just not sure why you making the toggled variable Rollburn the method to cast / do a dps spell/disc .... and not having them in the actual burn section,..... and making the

#bind Burn /burn

a toggled trigger.

 

[Scrublike]

Yeah it's only exists to set a flag you can use in conditions, nothing else.

I don't use the burn section for 2 main reasons:

1)The burn section only fires once
On a 30 minute raid where you need to be going full out from the start to the end you can't be constantly turning on burn

2) Burn takes so long to process a trash mob is often dead and your toon hasn't cast a single spell, makes it pointless. If you have burn all named going, it will sit there processing burn for maybe 10 seconds on each mob.

Someone was asking for different lvls of burn, you could do that by making rollburn accept different values, e.g. rollburn 1 vs rollburn 2 and then you could check in conditions. I think that's overkill, you should always be using your quick refresh burns anyway.

If I was to do something to enable a rolling burn mode without conditionals I would add yet another flag to the DPS section entries

e.g. (without checking correct syntax!) Heart of Flames|99|IFNOT Elemental Union|BURN

Then completely dump the burn section

 

[aspire2008]

Yeah it's only exists to set a flag you can use in conditions, nothing else.

I don't use the burn section for 2 main reasons:

1)The burn section only fires once
On a 30 minute raid where you need to be going full out from the start to the end you can't be constantly turning on burn

2) Burn takes so long to process a trash mob is often dead and your toon hasn't cast a single spell, makes it pointless. If you have burn all named going, it will sit there processing burn for maybe 10 seconds on each mob.

Someone was asking for different lvls of burn, you could do that by making rollburn accept different values, e.g. rollburn 1 vs rollburn 2 and then you could check in conditions. I think that's overkill, you should always be using your quick refresh burns anyway.

If I was to do something to enable a rolling burn mode without conditionals I would add yet another flag to the DPS section entries

e.g. (without checking correct syntax!) Heart of Flames|99|IFNOT Elemental Union|BURN

Then completely dump the burn section

I'm the same as you, I like having more control over the things that are being done. Most of the stuff can be added to the dps section with conditions to give finer control. Also, can you explain to me the use of using NULL vs NOT? For example I see you did ${Me.Buff[Elemental Union].ID} == NULL, is there some sorta processing time increase over !${Me.Buff[Elemental Union].ID}


I'm a slow work in progress of trying to learn how to write conditions and hopefully ease my way into writing macros.

 

[TreeHuginDruid]

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

Ahh.. understanding the request now...

That does sound like a good idea.... activation commands for /shortburn /fullburn ,... etc... and the activation parameters for the burns reset to 0 when the target is dead.

I like it ....

"He likes it, hey Mikey!" --- Random 1970's LIFE cereal quote.

 

[TreeHuginDruid]

I'm the same as you, I like having more control over the things that are being done. Most of the stuff can be added to the dps section with conditions to give finer control. Also, can you explain to me the use of using NULL vs NOT? For example I see you did ${Me.Buff[Elemental Union].ID} == NULL, is there some sorta processing time increase over !${Me.Buff[Elemental Union].ID}


I'm a slow work in progress of trying to learn how to write conditions and hopefully ease my way into writing macros.

You always evaluate the existence of non existence of a buff ID (which is an integer) by testing if the integer exists.... or does not exist... if you are trying to "compare" it to a NULL value ... you are just doing it wrong.... Your basicly saying then... does this buff id integer equal NULL .... well... it would never.... it would either exist ( 1/TRUE ) or not exist ( 0/FALSE )

Sorry... that's just how it goes. And the proper method in conditionals is testing it is ${Me.Buff[Elemental Union].ID} or !${Me.Buff[Elemental Union].ID}




FYI: Get your "MUST HAVE" suggestions in soon... thread closes saturday and all suggestions after that will not be considered for project plan.

 

[VorpalChicken]

I'd like to see the ability to do /stopdisc in my ini's so I don't have to keep fidderling with things I'll break to make it work

*****
One of the things we have been toying with is adding in the ability to execute commands, but not just any commands, they would have to be specific commands like /stopdisk. We would maintain a list of the commands and test for the allowable commands in the different routines. We are still working on the list...
*****

 

[gse7en]

When I first turn on KA, it might be worthwhile to have my puller waiting a little bit for the group to buff themselves if they need to.

Also, if my cleric is dead, I'd really rather not have my puller troll my group by wiping us, but absolutely +10 redcents for style to my puller because as annoying as it is, it's funny. Damn trolls.

 

[ctaylor22]

When I first turn on KA, it might be worthwhile to have my puller waiting a little bit for the group to buff themselves if they need to.

Also, if my cleric is dead, I'd really rather not have my puller troll my group by wiping us, but absolutely +10 redcents for style to my puller because as annoying as it is, it's funny. Damn trolls.

It might actually help a bit if you started your group except your puller, and start your puller last after buffs have been applied. one of the things I do is I have my MaxRadius set to like 25 on my puller and start up the group... Once all buffs are up on everyone I hit my hot key that sets my pullers MaxRadius to the radius I want to pull from that camp.

HotKey Example:

Name: 290
Entry 1: /varset MaxRadius 290
Entry 2: /varcalc CampRadiusExceed ${MaxRadius}+250

This way I can start up the whole group and the puller won't take off until I hit my hotkey...

 

[Chanticleer]

id like to see a buff change , maybe say instead of sitting to mem and demem every spell he has to cast , make it where it loads the entire spell line up ? make it seem more real ? like it will load all the buffs in the buffs section AKA spells 1-thru into spell gem , cast them then reload dps spells - just seems like it would be more stream line of real that way

 

[EQbackagain]

I'm not sure if this is a feature already, but do we have the ability for other group members to resurrect the party cleric/healer in the event of the healers death by way of a rez token?

 

[DarkDevil]

YES! The raids often call for, Short Burn (activate every thing that has LESS than a 10 minute repop timer,) and FULL BURN (Turn it all on!)

 

[gse7en]

id like to see a buff change , maybe say instead of sitting to mem and demem every spell he has to cast , make it where it loads the entire spell line up ? make it seem more real ? like it will load all the buffs in the buffs section AKA spells 1-thru into spell gem , cast them then reload dps spells - just seems like it would be more stream line of real that way

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.

LoadSpellSet=1
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.

 

[Skyjet2000]

Thought of another one.
Maybe a mana threshold for DPS section.
Something like If over 50% mana, run DPS, if under 50%, stop.

I Like to nuke with spare mana on healers at time, but don't want them running themselves oom doing so.

*****
This can be controlled with conditions.
*****

 

[Uyndaio]

Sorry if this already exists, and i am not aware, or if it cant be done, but i'd guess it can be.
a command that makes a character log out to character select screen, log into a different character, buff the rest of your group, and log back on the other character?

 

[waldonodrog]

HA automation...via pulling,tanking,cc,heals, moving point to point, rez/respawns, hails, rinse repeats...

 

[ctaylor22]

Thanks Everyone

Thanks for everyone's suggestions. Now we get to make a list and start prioritizing things. I am sure, not every suggestion will make it into K.I.S.S., but we will try and squeeze in as many as we can. Some may not make it into the next release, but that doesn't mean the suggestion isn't on the list.

Thanks again everyone for your help, now it is time for us to start the process.