Question - Commenting Out

[gogeceo]

Instead of having to rewrite all my numbers when i want to take a spell out is it possible for me to comment out the spell i might want to have there under the right circumstances i.e. tougher mobs?

Case in point
I have scent of thule as dps1= but right now the area I am in is pretty easy so I'd just like to skip it and go to the next one but leave it there so i dont have to rework all the numbers.

I was thining if i put like dps1=null and then whatever the comment out would be if possible like /** Scent of Thule **/

Would something like this work and how do we comment in ini files?

Thanks

 

[Sic]

to comment out in an ini you can use ;

I do this a bunch to add myself notes

;Divine rez - 100% rez 7hour+ re-use
Heals1=Divine Resurrection|0|rez

 

[gogeceo]

to comment out in an ini you can use ;

I do this a bunch to add myself notes

;Divine rez - 100% rez 7hour+ re-use
Heals1=Divine Resurrection|0|rez

That's great to know.

In the example you gave if you wanted to comment out the actual heals1=divine resurrection....

could i just put the ; in front of heals1
;heals1=Divine Resurrection|0|rez

or do heals1=null ;Heals1=Divine Resurrection|0|rez
so that for the time being it will skip over it. In my case I am wanting to comment out what will sometimes be my dps1 scent of thule because I dont always need to cast it.

my rotation starts:
DPS1=Scent of Thule|95|Once
DPS2=Call Skeleton Horde|94
DPS3=Exigeny for Blood|93|Once
DPS4=Blistering Shadow|93
.......

So I want the macro to ignore scent of thule sometimes which is why I figured commenting would be a good idea so I dont have to always change all the numbers everytime I take it out and put it back in. So would I do
;DPS1=Scent of Thule|95|Once
or
or do heals1=null ;DPS1=Scent of Thule|95|Once

My guess is it would be the second one but I am not sure how the program will reach to a null in one.

Sorry in advance for the long windedness of this whole thing.

 

[Sic]

you would just comment out the line

;DPS1=Blah
DPS1=Blah2

 

[gogeceo]

you would just comment out the line

;DPS1=Blah
DPS1=Blah2

So if I have DPS1 to DPS25 and I comment out like you suggest when I put that spell back in rotation would I have to update all the numbers from 1 to 26 now? or would it be okay for there to be 2 dps1's?

;DPS1=Scent of Thule|95|Once
DPS1=Call Skeleton Horde|94

to when I want to use it

DPS1=Scent of Thule|95|Once
DPS1=Call Skeleton Horde|94

Ultimately you answered my question about how to comment out now I am curious if I can save myself the work of having the change the 2s to 3s, 3s to 4s, 4s to 5s etc etc and vice versa

 

[Sic]

Unless I'm misunderstanding you - you are overthinking it a little bit.

if the line is started with a ; it is just entirely considered a comment, so in this:
the first line is a comment, and only dps1=blah2 is "real" - the ";dps1=blah" isn't something that the kissassist is going to load because its treated as a comment, or "a note"

;this line and any with a semi-colon starting it is a comment, I can put all sorts of stuff in here with no ill effect
;dps1=blah
dps1=blah2

if you wanted to swap them to use blah2 instead of blah you would simply

dps1=blah
;dps1=blah2
;RG Rulez

It really sounds like you perhaps want to just keep multiple .ini files for your specific situation, that way yo ucan just load it and not have to go and edit it every time you want a different setup

Alternate ini files: You can also tell KissAssist to load an alternate ini file. If your wizard has a separate ini to use ice nukes instead of fire nukes or your tank wants to run a DPS setup on easier content, you can just save another ini file and load that instead of your defaults.
Code:
/mac kissassist ini kissassist_Name_IceNukes.ini

 

[Sic]

while we're talking about your dps section (and at the risk of adding more confusion for you), I would personally recommend using dpson=2 and then just having everything set to |99 --- this will then just allow the macro to run those dps entries from top to bottom irrespective of waiting for mob health

• In the DPS section, you'll want to align your spells in order in which they cast. They don't need to be in order, but it helps to visually see which spells are going to be cast first and which spells will follow.
• If using DPSOn=1, Kissassist will cast each spell starting when the Mob Health is less than the Spell/AA's MobHealth% and pausing for the DPSInterval timer that starts when the fist spell starts to cast and will pause casting until the timer ends. Once the Mob's Health gets below the next Spell/AA's MobHealth% number that Spell/AA is added to the rotation making a snowball of damage that gets bigger and bigger as more Spell/AA's are added to the rotation. Dot's will be reapplied when they drop off the target. If you have an order that you want the Spell/AA's to cast in, you must use a different MobHealth% for each. An example would be first spell at 99 next at 98 then later in the rotation you might have a 76, 75, 74. once the target gets below 74 all the spells will cast in order from highest MobHealth% to the lowest tying to recast a spell if it gets resisted or interrupted as to not break the sequence. --good for debuff stacking using the |Once tag. If you use spells with the %health 98,98,98 70,70 and 30,30 you will not know what order it will pick, the 2nd or 3rd spell with the same %health may cast first. (Further testing needs to be done on how many times a spell gets resisted/interrupted before it moves on to the next.)
• If using DPSOn=2, Kissassist will cast in a sequential order, a chain of Spell/AAs starting with the highest MobHealth% to the lowest, with no casting delay/pause. As soon as the chain of casting starts, the DPSInterval timer starts. If it takes 12 seconds to cast all the spells in the chain and the DPSInterval is set to 10 you will see no delay in recasting the chain. If DPSInterval is set to 20, there will be an 8 second delay/pause before the chain will recast. If the Mob dies in the middle of a chain, the chain starts over for the new target. If the |Once tag is used with a Spell/AA, it will no longer be cast and will be skipped if the chain is cast a second or third time on the same target. If the target is new, the Spell/AA will cast again, but only once for the new target. If Dot's are used in the chain and they are still ticking on the target there will be a delay in the chain as Kiss checks target for the Dot's and if present will skip it, before moving to the next Spell/AA, but if the Dot ends it will be recast as soon as the current Spell/AA finishes casting, causing the order to be out of place when the chain is cast 2 or more times.

 

[gogeceo]

Unless I'm misunderstanding you - you are overthinking it a little bit.

if the line is started with a ; it is just entirely considered a comment, so in this:
the first line is a comment, and only dps1=blah2 is "real" - the ";dps1=blah" isn't something that the kissassist is going to load because its treated as a comment, or "a note"

;this line and any with a semi-colon starting it is a comment, I can put all sorts of stuff in here with no ill effect
;dps1=blah
dps1=blah2

if you wanted to swap them to use blah2 instead of blah you would simply

dps1=blah
;dps1=blah2
;RG Rulez

It really sounds like you perhaps want to just keep multiple .ini files for your specific situation, that way yo ucan just load it and not have to go and edit it every time you want a different setup

Alternate ini files: You can also tell KissAssist to load an alternate ini file. If your wizard has a separate ini to use ice nukes instead of fire nukes or your tank wants to run a DPS setup on easier content, you can just save another ini file and load that instead of your defaults.
Code:
/mac kissassist ini kissassist_Name_IceNukes.ini

Great! That's exactly what I wanted to know, thank you. I need multiple files for the same character which would help in obviously a variety of situations depending on the instance or area. Thanks so much for your swift replies

 

[gogeceo]

while we're talking about your dps section (and at the risk of adding more confusion for you), I would personally recommend using dpson=2 and then just having everything set to |99 --- this will then just allow the macro to run those dps entries from top to bottom irrespective of waiting for mob health

Okay sounds good,

My current set up was
DPSOn=2
DPSSize=15
DPSSkip=20
DPSInterval=0
DPS1=null ;Scent of Thule|95|Once
DPS2=Call Skeleton Horde|94
DPS3=Exigeny for Blood|93|Once
DPS4=Blistering Shadow|93
DPS5=Argandev's Venom|93
DPS6=Scorch Bones|93
DPS7=Pyre of Nos|93
DPS8=Ninavero's Swift Deconstruction|93
DPS9=Ninavero's Swift Lifedraw|93
DPS10=Night Stalker|93
DPS11=Thought Flay|93
DPS12=Rise of Bones|93
DPS13=Swarm of Decay|93
DPS14=Companion's Fortification|93
DPS15=Life Burn|93
DebuffAllOn=1

so I'll just change all the numbers to 99s

 

[Sic]

This is going to make the dps1 entry not functional - but it isn't what you're trying to do

add the semi-colon to the front of it if you want to "comment" it out - keep in mind that if you *do* do that, then kiss will create a DPS1=NULL entry for you since it no longer exists (and it will put it at the bottom of your current dps section
just ;DPS1=Scent of Thule|blah|blah
DPS1=null ;Scent of Thule|95|Once

if I were commenting that out, I would replace

DPS1=null ;Scent of Thule|95|Once

with (keep in mind, I'm just copy/repeating your 95 and once, not suggesting you keep it that way

;DPS1=Scent of Thule|95|Once
DPS1=NULL

to answer your question about the 99 - yes and no.
yes if you want it to cast your abilities in the order of those dps entries
no if you want it to wait for any reason to cast
you can still have different |##s, but they get treated as an order in the dps array rather than health values
(i personally just keep my dps entries in order of what i want to happen using the |99 and conditions to manage anything special like ${Target.Named} etc)

and sorry if I'm rambling a bit - I crawled out of bed to help with some code, then saw you had a post with no responses and didn't want you left hanging, so tryin to crawl back in bed to die now

 

[gogeceo]

This is going to make the dps1 entry not functional - but it isn't what you're trying to do

add the semi-colon to the front of it if you want to "comment" it out - keep in mind that if you *do* do that, then kiss will create a DPS1=NULL entry for you since it no longer exists (and it will put it at the bottom of your current dps section
just ;DPS1=Scent of Thule|blah|blah
DPS1=null ;Scent of Thule|95|Once

if I were commenting that out, I would replace

DPS1=null ;Scent of Thule|95|Once

with (keep in mind, I'm just copy/repeating your 95 and once, not suggesting you keep it that way

;DPS1=Scent of Thule|95|Once
DPS1=NULL

to answer your question about the 99 - yes and no.
yes if you want it to cast your abilities in the order of those dps entries
no if you want it to wait for any reason to cast
you can still have different |##s, but they get treated as an order in the dps array rather than health values
(i personally just keep my dps entries in order of what i want to happen using the |99 and conditions to manage anything special like ${Target.Named} etc)

and sorry if I'm rambling a bit - I crawled out of bed to help with some code, then saw you had a post with no responses and didn't want you left hanging, so tryin to crawl back in bed to die now

Excellent, that'll work just great for the time being. Thanks for your help Sic

 

[kaen01]

If you want to skip a line in a dps section or buffs, or heals set their value to 0, no need for commenting or anything.

Example:
Here Buffs6 and Buffs8 have been turned off by setting |0

[Buffs]
BuffsOn=1
RebuffOn=1
BuffsSize=9
CheckBuffsTimer=10
Buffs1=Nature Veil|Me
Buffs2=Strength of the Tracker
Buffs3=Jolting Swings|Me
Buffs4=Protection of the Paw
Buffs5=Yowl of the Predator
Buffs6=Flaming Arrows|0
Buffs7=Devastating Blades
Buffs8=Eyes of the Nocturnal|0
Buffs9=Consumed by the hunt
PowerSource=NULL

Same we can do in dps section, here we have turned of the first 3 dps lines.

[DPS]
DPSOn=2
DPSSize=19
DPSSkip=5
DPSInterval=0
DPS1=Summer's Mist|0
DPS2=Cataclysm Ash|0
DPS3=Windwhip Bite|0
DPS4=Barrage of Arrows|93
DPS5=Beetle Swarm|93|cond2
DPS6=Scout's Mastery of the Elements|90
DPS7=Outrider's Attack|77
DPS8=Outrider's Accuracy|77
DPS9=Group Guardian of the Forest|80
DPS10=Auspice of the Hunter|80
DPS11=Warder's Wrath|80|cond1
DPS12=Focused Storm of Arrows|93
DPS13=Sureshot Discipline|83|cond1
DPS14=Entrap|83|cond4
DPS15=Heartshear|90|cond5
DPS16=Guardian of the Forest|80
DPS17=${InvSlot[Chest].Item.Name}|70|weave|cond1
DPS18=command:/autofire|0|Once
DPS19=Spire of the Pathfinders|83
DebuffAllOn=0

 

[Sic]

@kaen01 yeah that too - but he wanted different things in place of each other

 

[kaen01]

oh yeah, then a simple a ; infront of the line you dont want to use is the proper way.

 

[gogeceo]

actualy i was just looking for the leanest thing and figured a comment would do the trick. did not realize setting a 0 would work either. they both work good with the 0 i may not have to worry about creating a second ini file i can just turn it on and off with 0 and non-zero unless theres an issue with that perhaps

 

[BrianGragg]

If you just copy your ini file and and name it bob2 you can call the other ini file while launching kiss. Then you don’t have to open your editor and make the changes all the time. This ini for this zone. This other ini for that zone. Could use camp names for your ini files too. Can have as many as you want for different circumstances. Don’t have to recreate them either as you just copy your working one into a new name.

 

[BrianGragg]

Like this:

Alternate ini files: You can also tell KissAssist to load an alternate ini file. If your wizard has a separate ini to use ice nukes instead of fire nukes or your tank wants to run a DPS setup on easier content, you can just save another ini file and load that instead of your defaults.



/mac kissassist ini kissassist_Name_IceNukes.ini

 

[gogeceo]

Like this:

Alternate ini files: You can also tell KissAssist to load an alternate ini file. If your wizard has a separate ini to use ice nukes instead of fire nukes or your tank wants to run a DPS setup on easier content, you can just save another ini file and load that instead of your defaults.



/mac kissassist ini kissassist_Name_IceNukes.ini

Sweet, tahts great. thanks Brian!

 

[Sic]

Sweet, tahts great. thanks Brian!

this is what i recommended this morning in this very thread > here <

 

[gogeceo]

this is what i recommended this morning in this very thread > here <

I know Wasnt trying to discourage the help.

 

[BrianGragg]

this is what i recommended this morning in this very thread > here <

Sorry Sic I was out of it and totally over looked that part of your post.

 

[runcade]

I have always put a | before the line that I didn't want to use. What is the difference between that and using the ;?

 

[ctaylor22]

The ; is syntactically correct when using ini files. The result will be the same regardless of using the ; or the |.

 

[deathlock]

The ; is syntactically correct when using ini files. The result will be the same regardless of using the ; or the |.

I use a # REBEL without a cause!

 

[Knightly]

The difference between:
|something=SomethingElse
and:
;something=SomethingElse

is that in the first, the value of "|something" is "SomethingElse" while the second is a comment. If you were to ask for the value of "|something" you would get "SomethingElse" back, whereas that is not the case with ";something." As CTay said, though, since you're probably asking for the value of "something" either of them are fine. It could also be "Asomething", "Bsomething", "Csomething", "NOTsomething" since all of those are not "something" but syntactically ";" is treated as a comment and the rest are treated as named keys.

 

[Redfrog]

Knightly..you |Something=Scare the ___ out of me
;Knightly scares poop out of me

 

[kaen01]

the problem happens, when people comment out things like this:

DPS1=#Summer's Mist|99 DPS1=!Summer's Mist|99 DPS1=;Summer's Mist|99 DPS1=.......Summer's Mist|99
just a few examples of the ways i seen, now that creates an entry in the dps1 array ofthe macro with an invalid value, and well that needs to be processsed, and that can cause issues in the long run i believe.

 

[ctaylor22]

In kiss 12 I added logic, when loading the Arrays, to check the first character, and if that character = ";" then skip the entry.