Problem - Random button calls in kissassist

[Damon]

I have recently noticed that in the MQ window, I get random calls for events to trigger which are immediately canceled and I don't know what's causing it.
When playing my characters I have noticed things like "casting Origin" Origin canceled" (or something to that effect) I will look and my origin hotkey is on hotbar 6 slot 10 and none of my code called that. I have also seen attempting to camp, camp interrupted and my guy sits down and stands up; I don't have any hotkeys for camp other than the default camp button on the basic UI window that has the melee and social tabs etc.

They have never succeeded in doing anything tragic so far but I am worried that at a crucial time when my group is invis in a dangerous place, one of these random calls will trigger my invis to drop, and I'll get swarmed and die.

 

[durango773]

I have recently noticed that in the MQ window, I get random calls for events to trigger which are immediately canceled and I don't know what's causing it.
When playing my characters I have noticed things like "casting Origin" Origin canceled" (or something to that effect) I will look and my origin hotkey is on hotbar 6 slot 10 and none of my code called that. I have also seen attempting to camp, camp interrupted and my guy sits down and stands up; I don't have any hotkeys for camp other than the default camp button on the basic UI window that has the melee and social tabs etc.

They have never succeeded in doing anything tragic so far but I am worried that at a crucial time when my group is invis in a dangerous place, one of these random calls will trigger my invis to drop, and I'll get swarmed and die.

origin cast is to mitigate the cast spell gem bug thats lurked on EQ side for the past 5 years or so. it cast, then cancels it, to *unstick* gems. there is a settibg stuckgems=0 to turn it off iirc.

> here <

 

[Dragonslayer]

I have this active as, for my feeling, it isn't cast very often.

 

[Damon]

origin cast is to mitigate the cast spell gem bug thats lurked on EQ side for the past 5 years or so. it cast, then cancels it, to *unstick* gems. there is a settibg stuckgems=0 to turn it off iirc.

> here <

Thank you for the quick and accurate feedback. It wasn't detrimental to my play but I am an old code debugger and hate not knowing what every line of code is doing. I am that guy with amazing bad luck that would randomly write a line of code that would break the whole game because my innocent code conflicts with that one line of code meant to work around someone else's bug they won't fix.
At university, they called me the bug whisperer because my code always seems to summon bugs out of the woodwork.
I once had a 1-day project that was meant to be about 10 lines of code to complete but I did 6 hours of edge case testing and "what if the customer types {this} into the input window" and it ended up being about 15 pages of code with several includes and imports to handle security, and future compatibility (because our professors were always adding last minute rule changes or the next project forced others to rewrite their last project from the ground up where I only had to add 1 line of code to handle the new changes [granted they probably spent less time writing both projects than I did writing the first project and the 1 line of code to complete the second project but it's not like time has any value right?])