Question - holyflag toggle?

[janktron]

can i make an if statement to toggle a holy in a social? something like "if holyflag1=0 then holyflag1=1 else if holyflag1=1 then holyflag1=0"?

 

[Incognito]

I do not believe so, the holy/down flags and the related shits are not their own TLO but rather under the /melee parent and not accessible.

What I have done is toggle between 2 different shits: If shit 1 fires, turn itself off and turn on 2nd shit. When 2nd shit fires, turn itself off and turn back on 1st shit. Multiline is required of course... I have mixed this method with downs and shits and offers some additional power not otherwise afforded.

 

[drcrimzon]

${meleemvi[holyflag0]} or !${meleemvi[holyflag0]}

it's in the wiki, I haven't tested as I dont have the client open right now. As long as the TLO was not removed from melee, it should work.

EDIT:
it works, two line social:

/if (${meleemvi[holyflag0]} && !${meleemvi[holyflag1]}) /multiline ; /melee holyflag0=0 ; /melee holyflag1=1
/if (!${meleemvi[holyflag0]} && ${meleemvi[holyflag1]}) /multiline ; /melee holyflag0=1 ; /melee holyflag1=0

 

[Meistro]

Yes you can use downs and holys to turn on/ off other holys and downs.
I do it alot to activate something i only want going off once in a combat.
At the end of your if statement you use the multiline statement

Holyshit01=/If (${TLO. statement/check}) /multiline ;  /do this ;  /melee holyflag01=0 ; /melee downflag01=1
Downshit01=/if (${check}) / multiline ; /melee holyflag01=1 ; /melee downflag01=0

 

[drcrimzon]

Yes you can use downs and holys to turn on/ off other holys and downs.
I do it alot to activate something i only want going off once in a combat.
At the end of your if statement you use the multiline statement

Holyshit01=/If (${TLO. statement/check}) /multiline ;  /do this ;  /melee holyflag01=0 ; /melee downflag01=1
Downshit01=/if (${check}) / multiline ; /melee holyflag01=1 ; /melee downflag01=0

He wants to do it in a social though.

 

[Incognito]

${meleemvi[holyflag0]} or !${meleemvi[holyflag0]}

it's in the wiki, I haven't tested as I dont have the client open right now. As long as the TLO was not removed from melee, it should work.

EDIT:
it works, two line social:
/if (${meleemvi[holyflag0]} && !${meleemvi[holyflag1]}) /multiline ; /melee holyflag0=0 ; /melee holyflag1=1
/if (!${meleemvi[holyflag0]} && ${meleemvi[holyflag1]}) /multiline ; /melee holyflag0=1 ; /melee holyflag1=0

Debugging TLOs:

    int ${meleemvb[idskill]}
    1 if the skill is ready and target in range, 0 if not. Most combat and/or character kills that can use an ID are testable here. Examples of idskills are: idleopardclaw, idslam, idforage, idfrenzy, idtigerclaw, idescape.
    int ${meleemvi[variable]}
    1/0 if the variable is set to on/off. This includes all variables that can be set on the command line.
    string ${meleemvs[option]}
    Evaluates option based on the current conditions and target. Options are all the INI options that contain command lines that need to be evaluated. Examples are: bashif, beggingif, tauntif, holyshit0, holyshit1, downshit1, slamif, etc. Echoing one of these options will show you how they evaluate.

Jesus Doc, my mind is reeling with some possibilities here... And I had just glossed over that section in the wiki, good find!

 

[Meistro]

If you looking at a hotkey thing

/Melee holyflag01=0

will turn it off

/melee holyflag01=1

will turn it on
But I'm not sure that and intake hotkey could do an if statement in that regard. But it's a good idea, and I'd really like to know if you get it to work..

 

[Incognito]

One problem I have had with toggling shits and holys on the fly is that KissAssist wont always turn combat off in a constant XTar situation (rightfully so, otherwise there would be lag in aggroing next XTar) so if you never wipe the XTar list you may never (or not very often) fire the down to facilitate a shit toggle.

Now, in a single target situation it works wonderfully but i rarely do those camps anymore lol.

- - - Updated - - -

That was supposed to be an 'Update' haha, posting at same time...

 

[drcrimzon]

But I'm not sure that and intake hotkey could do an if statement in that regard. But it's a good idea, and I'd really like to know if you get it to work..

Edited my earlier post with an example, it works on my SK.

 

[janktron]

Ty doc. Just what I was looking for.
I know I could do 2 separate socials, but I wanted a toggle. Less hotkey's the better

I'm at work and can't test atm, but looks like you have it set to turn 1 holyshit on and a different holyshit off. I want 1 social to toggle the same holyshit.
So maybe something like

/if (${meleemvi[holyflag0]}) /multiline ; /melee holyflag0=0 ; /if (!${meleemvi[holyflag0]}) /melee holyflag0=1

I'm not sure I'd that's the correct way to do an elseif statement or not.

- - - Updated - - -

One problem I have had with toggling shits and holys on the fly is that KissAssist wont always turn combat off in a constant XTar situation (rightfully so, otherwise there would be lag in aggroing next XTar) so if you never wipe the XTar list you may never (or not very often) fire the down to facilitate a shit toggle.

Now, in a single target situation it works wonderfully but i rarely do those camps anymore lol.

- - - Updated - - -

That was supposed to be an 'Update' haha, posting at same time...

This is specifically for in combat, so having constant xtars shouldnt matter for me....I hope, lol

 

[drcrimzon]

I want 1 social to toggle the same holyshit.

Ooops, I thought it was turn one on and the other off. I've run into issues with nested ifs in multiline before, but that might work. I don't remember what issue I ran into.
The issue with your statement, is you are turning it off, and then evaluating if it is off, which will always be true. Same if you reverse. It's not an else in that instance, it's 2 ifs.
maybe,

/if (${meleemvi[holyflag0]}) { /melee holyflag0=0 } else { /melee holyflag0=1}

I've never tried to use an else in a single line, but that might work. (May need to play with spacing).

 

[janktron]

Ooops, I thought it was turn one on and the other off. I've run into issues with nested ifs in multiline before, but that might work. I don't remember what issue I ran into.
The issue with your statement, is you are turning it off, and then evaluating if it is off, which will always be true. Same if you reverse. It's not an else in that instance, it's 2 ifs.
maybe,

/if (${meleemvi[holyflag0]}) { /melee holyflag0=0 } else { /melee holyflag0=1}

I've never tried to use an else in a single line, but that might work. (May need to play with spacing).

Yea I'm not sure how the syntax works in this...I remember (I think lol) that elseif came after then so was just going with that. Maybe CT or maskoi could clear this up for me

 

[Incognito]

CT posted a shit snippet not too long ago on the thread about nested IFs. Iirc, it mighta included a HUD like if/then/else... lemme see if I can find it.

- - - Updated - - -

Found it here. The HUD style if/then/else is very powerful and I had always wanted to be able to use it outside of HUD code. I musta been retarded but a long time ago I had tried to use it in a SHIT, and maybe even mac code to no avail. Alas, his post shows it so next time I need to 'branch' I will use it.

 

[janktron]

CT posted a shit snippet not too long ago on the thread about nested IFs. Iirc, it mighta included a HUD like if/then/else... lemme see if I can find it.

- - - Updated - - -

Found it here. The HUD style if/then/else is very powerful and I had always wanted to be able to use it outside of HUD code. I musta been retarded but a long time ago I had tried to use it in a SHIT, and maybe even mac code to no avail. Alas, his post shows it so next time I need to 'branch' I will use it.

/if (${If[${This.Equal[true]},True ,${If[${This.Equal[true]},True,False]}]})

this lost me, lol...im assuming this isnt verbatim how you would code it? lol

 

[Incognito]

Its actually correct syntax, its what we use in HUD code. What he did in his example is, on the first test, in the true branch, there is another complete if/then/else so if outer condition is true, you can have another condition test and branch from there. Its an example of nested IFs. I can break it down if that would help.

 

[janktron]

got it to work...sec ill post

holyshit toggle for anyone interested....I wanted it so i could consolidate some hotkeys into 1.

/if (${Me.Combat}) /multiline ; /if (${meleemvi[holyflag0]}) /melee holyflag0=0 ; /if (!${meleemvi[holyflag0]}) /melee holyflag0=1

should work with downshits too if you just change ${Me.Combat} to !${Me.Combat}

Hope this helps some people

*edit. had an extra space in the code...fixed now

 

[hoosierbilly]

could make an event in your macro or an include file for your macro that the social hotkey causes to fire...
this would be similar to how kissassist handles the /commands...

social would be /echo toggle holyshit

inc file would be sorta like

#event name "#*#toggle holyshit#*#"

sub event_name
/if holyshit is on turn it off
else /if holyshit is off turn it on
/return

I'll try to remember to post the exact syntax later when I'm not working or moving.