Question - Does setting DPSInterval = 0 interfere with the burn section ?

[eqholic]

In an attempt to improve dps I'm experimenting with lowering the dpsinterval. But now my characters don't burn anymore.

 

[ctaylor22]

Then something else changed. DPSInterval is used as a timer when other tests for a timer fails and it is nowhere in the burn section.

 

[TreeHuginDruid]

Then something else changed. DPSInterval is used as a timer when other tests for a timer fails and it is nowhere in the burn section.

What jub jub said . . . .

 

[eqholic]

Are there aliases that are needed for burn (with burnallnamed=1) ? And if so, does autocleric mess with aliases upon leveling ?

 

[TreeHuginDruid]

Are there aliases that are needed for burn (with burnallnamed=1) ? And if so, does autocleric mess with aliases upon leveling ?

If you are referring to the macro AutoCleric .... I don't have a clue because I don't use it.. and we didn't write it.... ... because that's not my baby....

There are no current aliases attributed to BURN....

burnallnamed parameter is simply that.... 0=off / 1=on .... if on it will kick off your BURN section for any detected named mob you are engaging (based upon either its naming convention.... or the TLO sub ordinal of .named... ) or if its defined in your KissAssist_Info.ini file for the zone you are in specified in the label for "MobsToBurn="


Now stop asking a billion questions.. i spend way too much time answering your posts... when I got better things to do like watch porn... lol

( oooohhhh baby ... show me that venus fly trap nature special again.... hhmmmmmm... )

 

[ctaylor22]

AutoCleric only uses these aliases that are used in kiss:

Sub AliasSetup
	/squelch /alias /camphere       /togglevariable ReturnToCamp
	/noparse /alias /campoff	    /togglevariable ReturnToCamp 0
	/squelch /alias /campradius     /changevarint General CampRadius
	/squelch /alias /chase          /togglevariable ChaseAssist
	/squelch /alias /chaseoff       /changevarint General ChaseAssist 0        
	/squelch /alias /chaseon        /changevarint General ChaseAssist 1 
	/squelch /alias /meleeon        /togglevariable MeleeOn
	/squelch /alias /meleeoff       /togglevariable MeleeOn 0
	/squelch /alias /mezon          /changevarint Mez MezOn
	/squelch /alias /mezoff         /changevarint Mez MezOn 0
	/squelch /alias /slowon         /togglevariable UseSlow 1
	/squelch /alias /slowoff        /togglevariable UseSlow 0
	/squelch /alias /returntocamp   /togglevariable ReturnToCamp
	/noparse /alias /instantrelease /togglevariable InstantRelease
	/noparse /alias /usefellowship 	/togglevariable UseFellowship
/return

And I want to take this opportunity to give merit to noobhaxor for his sensitivity when creating the following #Event definitions

#Event KissShit    		 "[MQ2] Reset #1# #2# #3#"
#Event KissShit      	 "[MQ2] toggle #1#

noobhaxor

 

[eqholic]

Sorry for disturbing your entertainment. But when weird stuff happens I come up with crazy theories. And the whole group suddenly not burning on a mob where they so far reliably did is very weird. I don't even get the message about mob beeing named anymore.

 

[ctaylor22]

Sorry for disturbing your entertainment. But when weird stuff happens I come up with crazy theories. And the whole group suddenly not burning on a mob where they so far reliably did is very weird. I don't even get the message about mob beeing named anymore.

I would just reverse whatever changes I made and see if things go back to normal, and if they don't. then most likely something else change by accident.. I have totally deleted entries from my ini files before and when checking my ini files, I think to myself, Hmmmm I thought that entry was closer to the top of this section not at the bottom... Then after thinking about it, there was only 1 logical explanation.

 

[eqholic]

Sometimes computers drive me mad. lol After a restart everything is back to normal.