Problem - Where can we disable spamming of Origin? (1 Viewer)

[ABDon]

Could you give a clear proof that the long-time stuck gem bug has been really really fixed this time please? Since DPG screwed this too many times...

Since proving a negative is impossible, no

 

[Trapt]

Hey all, since a couple patches ago, all of my characters are randomly casting origin, but I've checked all their ini's and there are no origin lines in them...any ideas?

 

[Sic]

Hey all, since a couple patches ago, all of my characters are randomly casting origin, but I've checked all their ini's and there are no origin lines in them...any ideas?

you will need to find the "Sub CheckStuckGems" in kissassist.mac and add a /return afterwards

Sub CheckStuckGems
    /return

 

[Lemons]

As for the fixed portion, they've claimed to fix it multiple times over various patches. If anyone has perfect repro or can show us a case of them being stuck, then we can decide if their fix worked.

EQ Forums may be of some help as well for research.

 

[Hylander]

I use what Sic posted.
If toons don’t turn up on the parse , then I go and unstuck them manually.

Forever hopeful Everquest fixes their QuickTime and clicky ready false positive stuff

 

[ctaylor22]

I added a flag for this, not sure when I added it, so check your ini and look for the CheckStuckGem entry.

 

[Sum1]

Also, the stuck gems thing still can happen, but its much more rare now. Or, I just get a bard in my group much more rarely...... whomp whomp....

 

[strongbus]

don't know what is causing it have tried a few ini.

everytime i use group coth on my mage it atemps to(and sometime gose off) to cast orgin aa as well.

 

[AmericanNero]

I believe you are asking about KissAssist. If KA thinks there is a stuck spell gem, it attempts to correct it by clicking Origin. If you cast a long-duration spell like Call of the Heroes, it thinks there is a stuck spell gem and tries to cancel it. The "fix" is to open up KA in your favorite editor and then within Sub CheckStuckGems, go to line 13746 and insert /return. Now your casts wont get cancelled.

 

[ctaylor22]

Casting coth in itself is not the issue, it is trying to cast it outside of kiss and not pausing the macro that is the problem.

 

[jb321]

Weirdness is also happening with the Zueria Slide, I just ran fight fire and completed it healerless, because the healer ported to skyfire..

 

[Leifer1969]

I'm fairly new to KA, but this is a new problem I haven't had before. When I manually go to press a spell gem on the spell bar, I get "You begin casting Origin". Then a "Your ability failed. Timer has been reset." Is this a known bug and is there a fix?

Thanks in advance for any help.

[General]
KissAssistVer=12.001
Role=Assist
CampRadius=30
CampRadiusExceed=400
ReturnToCamp=0
ChaseAssist=0
ChaseDistance=25
MedOn=1
MedStart=10
MedStop=50
MedCombat=0
LootOn=0
RezAcceptOn=1|90
AcceptInvitesOn=1
GroupWatchOn=0
GroupWatchCheck=FALSE
CorpseRecoveryOn=0
EQBCOn=1
DanNetOn=0
DanNetDelay=20
IRCOn=0
CampfireOn=0
CharInfo=Paladin|17|GOLD
DefaultUI=TRUE
DPSMeter=1
ScatterOn=0
XTSlot=1
[SpellS]
MiscGem=8
MiscGemLW=0
MiscGemRemem=1
LoadSpellSet=0
SpellSetName=KissAssist
CastingInterruptOn=1
Gem1=NULL
Gem2=NULL
Gem3=NULL
Gem4=NULL
Gem5=NULL
Gem6=NULL
Gem7=NULL
Gem8=NULL
[Buffs]
BuffsOn=0
BuffsSize=20
Buffs1=NULL
Buffs2=NULL
Buffs3=NULL
Buffs4=NULL
Buffs5=NULL
Buffs6=NULL
Buffs7=NULL
Buffs8=NULL
Buffs9=NULL
Buffs10=NULL
Buffs11=NULL
Buffs12=NULL
Buffs13=NULL
Buffs14=NULL
Buffs15=NULL
Buffs16=NULL
Buffs17=NULL
Buffs18=NULL
Buffs19=NULL
Buffs20=NULL
RebuffOn=1
CheckBuffsTimer=10
PowerSource=NULL
[Melee]
AssistAt=95
MeleeOn=1
FaceMobOn=1
MeleeDistance=45
StickHow=snaproll
AutoFireOn=0
UseMQ2Melee=1
TargetSwitchingOn=0
[GoM]
GoMSHelp=Format - Spell|Target, MA Me or Mob, i.e. Rampaging Servant Rk. II|Mob
GoMSize=3
GoMSpell1=NULL
GoMSpell2=NULL
GoMSpell3=NULL
[GMail]
GMailHelp=Events currently support - Dead,Drag,GM,Level,Named,Leftgroup,Tells
GMailOn=0
GMailSize=5
GMail1=NULL
GMail2=NULL
GMail3=NULL
GMail4=NULL
GMail5=NULL
[AE]
AEOn=0
AESize=10
AERadius=50
AE1=NULL
AE2=NULL
AE3=NULL
AE4=NULL
AE5=NULL
AE6=NULL
AE7=NULL
AE8=NULL
AE9=NULL
AE10=NULL
[DPS]
DPSOn=1
DPSSize=20
DPSSkip=20
DPSInterval=7
DPS1=cease|99
DPS2=ward undead|75
DPS3=NULL
DPS4=NULL
DPS5=NULL
DPS6=NULL
DPS7=NULL
DPS8=NULL
DPS9=NULL
DPS10=NULL
DPS11=NULL
DPS12=NULL
DPS13=NULL
DPS14=NULL
DPS15=NULL
DPS16=NULL
DPS17=NULL
DPS18=NULL
DPS19=NULL
DPS20=NULL
DebuffAllOn=0
[Aggro]
AggroOn=0
AggroSize=10
Aggro1=NULL
Aggro2=NULL
Aggro3=NULL
Aggro4=NULL
Aggro5=NULL
Aggro6=NULL
Aggro7=NULL
Aggro8=NULL
Aggro9=NULL
Aggro10=NULL
Aggro2nd=0
[Heals]
Help=Format Spell|% to heal at i.e. Devout Light Rk. II|50
HealsOn=1
AutoRezOn=0
HealsSize=15
Heals1=Light Healing|25
Heals2=Lay on Hands|3
Heals3=NULL
Heals4=NULL
Heals5=NULL
Heals6=NULL
Heals7=NULL
Heals8=NULL
Heals9=NULL
Heals10=NULL
Heals11=NULL
Heals12=NULL
Heals13=NULL
Heals14=NULL
Heals15=NULL
XTarHeal=0
XTarHealList=Xtar slots here Example: 5|6|7
HealGroupPetsOn=0
RezMeLast=0
[Cures]
CuresOn=0
CuresSize=5
Cures1=cure poison
Cures2=cure disease
Cures3=NULL
Cures4=NULL
Cures5=NULL
[Merc]
Help=To use: Turn off Auto Assist in Manage Mercenary Window
MercOn=0
MercAssistAt=92
[Burn]
BurnAllNamed=0
UseTribute=0
BurnSize=15
Burn1=NULL
Burn2=NULL
Burn3=NULL
Burn4=NULL
Burn5=NULL
Burn6=NULL
Burn7=NULL
Burn8=NULL
Burn9=NULL
Burn10=NULL
Burn11=NULL
Burn12=NULL
Burn13=NULL
Burn14=NULL
Burn15=NULL
[Pull]
PullWith=cease
PullMeleeStick=0
MaxRadius=350
MaxZRange=50
UseWayPointZ=0
PullWait=5
PullRadiusToUse=360
PullRoleToggle=0
ChainPull=0
ChainPullHP=90
PullPause=30|2
PullLevel=14|20
PullArcWidth=0
PullOnReturn=0
[PullAdvanced]
PullLocsOn=0
[AFKTools]
AFKHelp=AFKGMAction=0 Off, 1 Pause Macro, 2 End Macro, 3 Unload MQ2, 4 Quit Game
AFKToolsOn=1
AFKGMAction=1
AFKPCRadius=500
CampOnDeath=0
ClickBacktoCamp=0
[KConditions]
ConOn=0
CondSize=5
Cond1=TRUE
Cond2=TRUE
Cond3=TRUE
Cond4=TRUE
Cond5=TRUE
[KissError]
LastCMD:=/endmacro
ErrorDateTime:=05/16/2021 14:53:41
ErrorMsg:=Couldn't open macro file: C:\Users\Larsen\AppData\Local\VeryVanilla\Live\Release\Macros\stop.mac
DataError:=NULL
SyntaxError:=NULL
RunningTime:=19416724
BuildDate:=20210514
CurrentUI:=Default

 

[Sic]

I'm fairly new to KA, but this is a new problem I haven't had before. When I manually go to press a spell gem on the spell bar, I get "You begin casting Origin". Then a "Your ability failed. Timer has been reset." Is this a known bug and is there a fix?

Thanks in advance for any help.

I merged your thread into the existing origin thread.

the tl;dr is that kiss uses origin for "stuck spell gem detection"

per CTaylor:

I added a flag for this, not sure when I added it, so check your ini and look for the CheckStuckGem entry.

so you should have a CheckStuckGem entry in your INI and you can change that to =0

or - if that never got added

you will want to edit out the sub in your kissassist as suggested in a few of the posts

Sub CheckStuckGems
    /return

 

[jrhansen]

I merged your thread into the existing origin thread.

the tl;dr is that kiss uses origin for "stuck spell gem detection"

per CTaylor:


so you should have a CheckStuckGem entry in your INI and you can change that to =0

or - if that never got added

you will want to edit out the sub in your kissassist as suggested in a few of the posts

Sub CheckStuckGems
    /return

Can we just add this to the character ini file ? as its not in the generated ini files. under General ?

Or just replace the existing CheckStuckGem sub with an empty one ?

| ----------------------------------------------------------------------------
| SUB: Check and Fix Stuck Gems
| ----------------------------------------------------------------------------
    Sub CheckStuckGems
        /if (${Window[CastingWindow].Open} || ${Me.Invis}) /return
        /if (${Me.AltAbilityReady[origin]}) {
            /alt act ${Me.AltAbility[origin].ID}
            /delay 50 ${Window[CastingWindow].Open}
            /stopcast
            /delay 10
        } else {
            /echo Origin AA not ready.
            /delay 20
        }
    /return

to

| ----------------------------------------------------------------------------
| SUB: Check and Fix Stuck Gems
| ----------------------------------------------------------------------------
    Sub CheckStuckGems
    /return

Untill now it never have fired, but I get stomach ache each time this happens

Playing on Rizlona, and it does have a fairly large ping of avg 190 (Scandinavia) compared to other servers

 

[kraszus]

Anyone else experiencing random casts of Origin that causes interrupts to toons mid-buff?

 

[Sic]

Anyone else experiencing random casts of Origin that causes interrupts to toons mid-buff?

I merged your post to the existing thread - read up in here a bit for an explain / solution

 

[Sum1]

Why hasn't this just been removed from KA entirely? Or defaulted to off and requires someone to enable it if they want to use it?

 

[Sic]

Why hasn't this just been removed from KA entirely? Or defaulted to off and requires someone to enable it if they want to use it?

yeah

AN has a merge request here that will warn users by default, or can be turned off, or set to "use origin" if they want

https://gitlab.com/redguides/kissassist/-/merge_requests/23

 

[ctaylor22]

Why hasn't this just been removed from KA entirely? Or defaulted to off and requires someone to enable it if they want to use it?

Because back when this use to be a bigger issue, we had to add the code to check for stuck gems and do something to correct the issue. The fix has always been to cast an AA and then cancel casting. Everyone gets the Origin AA early on, so we decided to se that AA. There was a flag added to allow you to turn on and off this functionality. CheckStuckGem=0 should turn this off. I will add this to my list of things to revisit when when making future changes.

 

[AmericanNero]

I've already posted the fix... check gitlab...

 

[insomniac3011]

Recently I have had problems with this, and they do actually manage to get it off a lot of times causing a few wipes! The only cure I have found so far is to re-install MQ2 every day or so, that seems to have fixed it ....for now?

Are you by any chance using the "CastingInterruptOn=0" Because that's suppose to prevent it from interrupting spells it casts, im not sure if that would also stop it from interrupting origin though.