Utility QKI "Quicky Kiss It" - A Clunky KissAssist UI. 2.51

Hey everyone,

We have a couple of updates for QKI.

First is a big thanks to @ctaylor22 fixing up the is macro running sections of QKI so that we check if KissAssist is running on initial start of QKI. This fixes a few situations, like one that caused QKI to fail to see a macro running that you may have encountered. For example if you loaded an ini and then set a role and randomly QKI ui would dim and show as if KissAssist was not running when KissAssist is actually was running.

Second is an update to show part of the name of the ini loaded, If you have a couple different KissAssist ini made for certain situations for a character you can easily see what one is loaded/running, and this helps if using viewports and have a couple QKI windows on one screen identify what characters QKI window your are looking at.

Hey! Hope everyone had a great 2024, a Merry Christmas, and wish everyone a Happy New Year! I apologize for not having any updates sooner, We moved in the summer this year and it was a bit of an ordeal since spring. I had to take a break from EQ for a bit and had not had a chance to work on QKI until now. The good news is I have some updates today, and more planned for 2025.

QKI 2.5 Updates:

1. Added Group Watch settings to the pulling tab. Two things we can do here:

A. Set your low mana threshold. The default is 20. Changes are committed to the INI right away. *appends the change for example at 40% mana "|40" to the GroupWatchOn=1|40 line in your ini. If no value set the kiss default is 20% and the ini will only have a =1 or =2

B. Set your group Watch On for either the entire group, or just your healers. *Changes between GroupWatchOn=1 Watching the whole group, or GroupWatchOn=2 watching just healers in the group,

C. GroupWatchOn=0 both unchecked, I don't care about no mana... we killing things if we die we die..

2. Added functionality for Group watch conditions. GroupWatchCheck=FALSE (Unchecked in QKI) means we do not have any special conditions in our Kconditions section of the kiss ini to check, this is default for most. GroupWatchCheck=TRUE (Checked in QKI) means we have other conditions to be met, and they are in our Kconditions section of the kiss ini. If you have specific conditions for group watch identified in your Kconditions section they need to be in the first Kcondition for example cond1=

To use this option, you must have turned on conditions(ConOn=1) in your ini file and created a condition for this option.

Example:
GroupWatchCheck=cond1 (Checked in QKI) and you set in your ini something like:
[KConditions]
ConOn=1
CondSize=26
Cond1=${Me.Snared}

This *SHOULD* hold pulls until your are not snared any more.. let me know what you guys see.

With this feature you can do things like create conditions that wait for someone that just got a rez or any other condition you can think of.
*In the future we might work something up so you can choose what condition number you want to set as your GroupWatchCheck condition but for now while we test it out just move your existing other conditions down a row if you want to use this feature.

3. Added a resume pulls after fade feature. Testing this seems to work just ok but you guys let me know what you experience. I know this is going to need some fine tuning but its a start. The way this works is when Auto Resume Pulls After Fade is checked we will issue a /MQP ON command when the hater threshold is met and fade is triggered. We then use a timer that can be changed in the pull settings tab (default 90sec) That then issues /MQP Off command when timer has elapsed. Not exactly ideal for fade abilities that cause you to fall to the ground like FD but for bard or warrior it might work.

4. Ran into a problem with the fade ability reuse timer causing the new pause/resume pull settings to go into a loop every 90 seconds pausing and unpausing because we had no checks in place that make sure your fade ability is available to use and not on cool down, so I added checks to make sure that we can even use our fade aa, and if we can use then we can attempt to pause and resume after the elapsed time set in QKI in the pulling tab. This is also an overall improvement to the fade over pulls section so that we don't keep trying to use fade when the hater threshold is met.

5. Changed some formatting and layout, changed a lot of ImGui.NewLine() to ImGui.Spacing() to help condense the content to better fit the window. Added a couple lines. Fixed some spelling and tool tip stuff that sort of thing.

Hopefully the Group Watch stuff helps, and the Fade over pull improvements help create a better foundation for improving the feature. As always please let me know in the discussion if you have any subjections, or run into any bugs.

Thanks!

Sorry all, Just realized that some how we still had 2.42 attached here didn't notice until I updated luas with rg updater that 2.43 was not being downloaded. Please give this update a spin it really helps the lag.

Did lots of testing last night, and decided we needed another quick update.

I noticed a lot of lag that was associated with the way some timer code to check if kissassist is running or not.

Updated some logic for most timers that qki uses. This should clear up that lag after you set a role that looked almost like a 1-2 second freeze around every 10-15 seconds while kiss is running.

Fixed an error with stickhow handling causing a few of the other input field commitments to lead to a crash.
Fixed a spelling error that prevented the tank role from working correctly.
Fixed some errors in the tool tips that caused the code to display unwanted numerical values in in the tool tip text.

Noticed that in some lag when selecting an ini and setting a role to start kiss for the first time after opening qki that some times the ui would stay greyed out and look as if kiss was not running when it was and would revert to no ini loaded.

Added a small delay before QKI performs its initial checks with in the checkMacroStatus function. This should prevent this issue.

Added Tab colors, now better identifying of what tab we are on currently at a quick glance.

Fixed Bard Fade issue.

Added stop commands to all fade commands.

Added support for MQ2Melee options from KissAssist.

Added Set Melee Distance.

Added StickHow and for now, some basic/limited options more to come after some testing.

Added backend stuff for fontsize, opacity and things that may be adjustable in something like a ui settings tab later down the road.

Added tool tips to help explain what stuff does. Added check box to toggle tool tips on and off.

Add more logic for a better set role experience and how we check for for kiss to be running, how we handle the macro ending and it resetting our roles and buttons. Pause also will now better reflect its state should kiss end.

Added lock out based on ini loaded true or false that forces an ini to be loaded before selecting a role and starting kiss. If kiss ends you will now have to reload your ini as well. While this can be annoying this will reset your values in QKI to better reflect what is in the ini every time you restart kiss.

Moved load ini button, added color to set role button when role not set.

There are a few other small changes, and more to come soon.

Let me know if you see bugs.

Thanks.

Quick update to fix a crash happening when using the fade over pulls function - 11/23/23 @7:33PM PST

Happy Thanksgiving!

I know this time of year has always been a sweet spot for EQ play time for me. I think I received EQ with Kunark as an early christmas gift some time around thanksgiving 2000, and created my own account and first Barbarian Shaman, prior to that my friend would let me play his druid from time to time. I spent most of that winter getting chased around everfrost by polar bears..

Anyway in the spirit of Thanksgiving, and the Holidays I wanted to make a meaningful update to QKI for people to use.

QKI 2.3 "Now less clunky here, but also more clunk over there...":

Updated key functions like Role selection, ini loading, Pause and Stop to exist Statically outside and above tabs. This allows for this primary functionality to be easily accessed and viewed at all times.

Updated Roll selection function to fall back to not set if kissassist is ended for some reason.

Updated Text with colors to identify if kiss is running, and if you have an ini loaded or not.

Updated the pause button with more logic to more accurately check if kissassist is really paused or not and reflect that rather than the more crude way from prior versions.

Updated main window Opacity, and Added in a "Grey out" or "Dimming" feature to dim our tabs when kiss is not running. This helps identify that the macro is not running and therefore these functions in the tabs while still editable will probably not do anything until kiss is running. **The edit and force ini live in the main tab and are dimmed because at the moment these rely on kissassist to be running for them to work. Added rounding to make it look nicer.

Updated so that a couple of plugins that we are using are autoloaded when QKI starts. MQ2Notepad, and MQ2Xassist.

Updated load ini logic to disregard some of the variations "Lazy ini" in different kissassist ini's like having all your keys in the ini in lowercase.. These lazy ini's should now load fields more better.

Updated some Checkbox and Input Field sort order, added and removed (some duplicate) functions from the tabs.

Added what I call "Fade Over Pulls" function to the Pulling tab. This is more aimed at fading aggro while pulling than just fading aggro overall as we can easily do that in our aggro section of the ini and toggle that on and off.

Fade Over Pulls Details: This while still very clunky when checked will try and use the selected "fade" ability *limited to specific level aas mostly at this time by class* and then compare the hater count you input **defaulting to 3 at the moment** and use plugin MQ2Xassist to compare your value to your Xtar Hater list and then try and use the selected "Fade Ability" for your class to drop the aggro. **This also Checks your Roll and will only fire if you are in Puller, Puller Tank, or Hunter Roles.**

This will most certainly need some refinement but does basically work, play with it give some feedback. I think we are going to need a /stopcast /attack off /stop song ....... trigger when the "fade" is triggered but we will test it this way first.

There are probably a few other things that changed I am forgetting about.

As always: BACK UP YOUR INI, PLEASE PROVIDE FEEBACK IN DISCUSSION, LET ME KNOW IF YOU FIND A BUG SO I CAN FIX IT PLEASE, CLICK FOLLOW SO YOU GET UPDATES!

** Following should allow you to easily get updated from the RG Launcher as well see here:

Thank you for those who have given some feedback, and those who have gave QKI a try. More good stuff to come soon, I will update instructions, FAQ and things as well when I get a chance. Happy Thanksgiving!

2.2 Mostly Fixes for Imgui/overlay crashes when minimizing the qki window or docking with other luas.

As always back up your Kiss INI files before using this.

• Found a problem that was causing overlay and imgui crashes and fixed it.
• Fixed the roll selection so that it retains the selected role you no longer have to repick it from the drop down before hitting the set roll button again.
• Spent a bunch of time breaking things up into smaller more manageable modules. The package now contains init.lua, checkbox_handlers.lua, config.lua, utils.lua and tabs.lua this is mostly to help organize the growing bunch of stuff that has been added and will be added down the road it.

Please if you are using this click watch so you see updates. Happy to hear feedback on user experiences, and please report problems in the discussion.

Download and extract to you next\MacroQuest\lua\ adding a QKI folder that contains: init.lua, checkbox_handlers.lua, config.lua, utils.lua, and tabs.lua
To run in game type /lua run qki