Problem - Characters using Kiss are not using burn command.

[laslow1908]

I have BurnAllNamed=1 on my mage and he only occasionally burns automatically on named. My other kiss character is set to BurnAllNamed=0 but neither of them burn when driving toon sends the /bcga //burn. All toons using MQ2CWTN plugins work just fine though. This problem began to my knowledge around the time I tried swapping things around to do Crusader mission. I saw some lines on one of Sics post about Alias and used them, not sure if that caused this issue.

 

[an_image]

I have BurnAllNamed=1 on my mage and he only occasionally burns automatically on named. My other kiss character is set to BurnAllNamed=0 but neither of them burn when driving toon sends the /bcga //burn. All toons using MQ2CWTN plugins work just fine though. This problem began to my knowledge around the time I tried swapping things around to do Crusader mission. I saw some lines on one of Sics post about Alias and used them, not sure if that caused this issue.

Ditto, i've seen this two with two mages running the exact same macro as the other on the same team. One fired of the burn instantly, the other either didn't recognize the named trigger...or was delayed.

 

[SomeTester]

I’m having problems with my mage burning also using Kiss.

 

[deathlock]

@ctaylor22 and I have worked out the kinks on this. I am not sure if he has updated latest version. Sorry @ctaylor22 if I am speaking out of turn. If so, a fix is n the works and it works great.

 

[ctaylor22]

The Burn code that @deathlock and I worked on has been pushed to the kissassist forums, but I am not sure it has made it into the compile. Go try and download it from the kissassist forum and read the instructions before using the new burn code. there were a few changes.

 

[deathlock]

In short:

## To turn burn section off BurnAllNamed=0 or /Burn Off (group command: /Bcg //Burn Off)*
# !!! The burn section will never be activated.

## To turn burn section on BurnAllNamed=1 + /Burn On or (group command: /Bcg //Burn On)*
# !!! The burn section will go active on any named mob.

## To activate a burn at any time /Burn or (group command: /Bcg //Burn)*
# !!! The burn section must be on via BurnAllNamed=1 and /Burn On prior for this to work.

*This uses EQBCS

 

[gawker]

In short:

## To turn burn section off BurnAllNamed=0 or /Burn Off (group command: /Bcg //Burn Off)*
# !!! The burn section will never be activated.

## To turn burn section on BurnAllNamed=1 + /Burn On or (group command: /Bcg //Burn On)*
# !!! The burn section will go active on any named mob.

## To activate a burn at any time /Burn or (group command: /Bcg //Burn)*
# !!! The burn section must be on via BurnAllNamed=1 and /Burn On prior for this to work.

*This uses EQBCS

But this is not the functionality that I have used up to now. In zones with mobs having names that look like Named, but are not( Kael for example) I do not want Burns trying to fire off on every mob. Also, most Named mobs I can kill without using Burns so I don't usually want burns to fire.

This new solution does not allow me to ignore the Burn section unless I trigger the burns when I want.

Am I misunderstanding the new functionality? What was the reason for this change?

 

[gawker]

The Burn code that @deathlock and I worked on has been pushed to the kissassist forums, but I am not sure it has made it into the compile. Go try and download it from the kissassist forum and read the instructions before using the new burn code. there were a few changes.

Are the new instructions in the Wiki? Is it the BurnAllNamed=2?

Can I use BurnAll Named=2 with no KissInfo.ini entries and still use /Burn to trigger the Burn section manually?

 

[ctaylor22]

If you turn /burn off it is off regardless of BurnAllNamed, if you want BurnAllNamed to work you need to turn /burn on. The logic in how burn works did NOT change, all that was added was a way to turn it on and off while the macro is running.

BurnAllNamed=2 is dependent on what is in the kissassist_info file. Just set BurnAllNamed=0 and use /burn manually. You can use /burn on any target.

 

[deathlock]

To understand it logically, you need to understand the below comments:. (Not being condescending at all, just getting the message across)

## To turn [Burn Section] OFF, there are 2 methods.
1: BurnAllNamed=0 (Never type /Burn On)
2: Type: /Burn Off (even if BurnAllNamed=1)
# !!! The burn section will never be activated.

## To turn [Burn Section] ON, there are 2 methods.
1: If BurnAllNamed=1 and you have NEVER typed /Burn off
2: If (BurnAllNamed=1 or BurnAllNamed=0) and you have typed /Burn On
# !!! The burn section will go active on any named mob.

## To activate the [Burn Section] at any time /Burn
# !!! The burn section must be on via:
1: If BurnAllNamed=1 and you have NEVER typed /Burn off
2: If (BurnAllNamed=1 or BurnAllNamed=0) and you have typed /Burn On

I hope this clarifies how this works.

The Initial BurnAllNamed=0 or BurnAllNamed=1 is followed unless commands are typed in game to over ride it as stated above. These options give you complete control over how to activate your burns whether it be automatically or manually. No one wants to burn on a white conned named so /Burn Off. Everyone I would like to assume burns a Red con name so /Burn On. I like to initiate a burn when I have 3 yellows and a blue in camp... so /Burn On (if not already set) followed by /Burn. Using it with EQBCS for all your toons is advised.

These options give you fine tuning on Who, What, When and Where to burn. Never waste another burn cycle again.

 

[MrPatate]

/burn

Command Usage syntax: /burn - Checks if Burn is turned on or off and starts burn if turned on. /burn 12345 - Checks if Burn is on or off and starts burn if turned on. 12345 refers too the targets ID you want to burn. /burn on - Turns burn on. Does NOT execute Burn. /burn off - Turns burn off. /burn 12345 on - Turns burn on and Executes Burn using the Mobs ID of 12345. /burn on doburn - Turns burn on and Executes burn. Burns are turned ON by default when starting the macro. So if you do a /burn off on a character and then issue the /burn command. The character will NOT execute the burn routine.

From the updated kiss thread.

 

[SomeTester]

It is in your KA ini file as BurnText. The KA default phrase is below, but you can change it to whatever you want.

BurnText=Decepticons Attack

Note it will look for that text in the MQ2 window, not as a say/group/tell/raid message. So you need to use "/echo"

Hotkey for single character:

/echo Decepticons Attack

Hotkey for all characters on your EQBCS server:

/bcaa //echo Decepticons Attack

You should also check out the KissAssist settings and Ini info page. It is wonderful.

Yeah I see all that. The problem is it doesn’t do anything. It my last 10 missions, the character only did it once. Something is fishy. My BurnText=Burn and I /echo Burn and /baca //echo Burn doesn’t work. I see Burn pop up in the MQ2 window. I’m wondering if I need to up the frame rate for my Mage since he runs in a background window.

 

[Robban]

and if I am not wrong, has noting to do with how to trigger the burn?

burntext is only the text that echos in mq2 window when a burn is started, not the text you type to trigger the burn?

 

[Sic]

and if I am not wrong, has noting to do with how to trigger the burn?

burntext is only the text that echos in mq2 window when a burn is started, not the text you type to trigger the burn?

you used to type the burntext to make it burn - it was changed to the current system which includes /burn

 

[Robban]

you used to type the burntext to make it burn - it was changed to the current system which includes /burn

ahh okidoki

here @SomeTester is a very new thread about the burn

https://www.redguides.com/community/threads/characters-using-kiss-are-not-using-burn-command.76129/

 

[gawker]

Thanks for the clarification. Carry on.

 

[SomeTester]

you just bumped something from 3 years ago.

Holy moly I don’t k LW how that happened. I got a notification that someone replied to me so I replied back. I must have gotten lost along the way lol. Can we just delete all my garbage and then somehow delete my embarrassment?

 

[Sic]

Holy moly I don’t k LW how that happened. I got a notification that someone replied to me so I replied back. I must have gotten lost along the way lol. Can we just delete all my garbage and then somehow delete my embarrassment?

I just moved your posts to a more recent thread asking about burn commands that ctaylor responded with some infos - read up a bit might answer any remaining questions

 

[Sic]

Holy moly I don’t k LW how that happened. I got a notification that someone replied to me so I replied back. I must have gotten lost along the way lol. Can we just delete all my garbage and then somehow delete my embarrassment?

and no need to be embarrassed - no one's judging (and if they are pfft) - internet can be hard to read