Question - EQBC /bct someone an if?

[drcrimzon]

Is it possible to send a bct to a toon, with an if in it?

i.e.
/bct toon //if (!${Me.Mercenary.State.Equal[ACTIVE]}) /nomodkey /notify MMGW_ManageWnd MMGW_SuspendButton LeftMouseUp

So basically, if your mercenary is inactive, click the suspend (unsuspend) button. Right now it runs the if statement on whoever is sending the BCT, which doesnt help determine if their merc is up. I haven't figured out how to check from the sender's side if the targets merc is active, I guess that is another way to skin it if anyone knows how I can check that (Hopefully outside just checking for the merc's name in group).

So, right now it works like:
ToonA has Merc up
ToonB's merc died, or is not up
ToonA sends the above BCT
ToonB does nothing because the if variables are populated with ToonA's variables and it thinks his merc is already up.

So is there either, 1. A way to escape and pass the if statement to the bct target to evaluate? or 2. A way to check target.mercenary.active (I can't find it is docs).

 

[etherealmist]

Yes, you can use if statements in bc commands. I don't know the answer you your second question.

 

[ctaylor22]

It is a long shot, but you could try the /noparse command, not sure if it would work.

/bct toon /noparse //if (!${Me.Mercenary.State.Equal[ACTIVE]}) /nomodkey /notify MMGW_ManageWnd MMGW_SuspendButton LeftMouseUp

/noparse /bct toon //if (!${Me.Mercenary.State.Equal[ACTIVE]}) /nomodkey /notify MMGW_ManageWnd MMGW_SuspendButton LeftMouseUp

Not sure what would happen.

 

[drcrimzon]

It is a long shot, but you could try the /noparse command, not sure if it would work.

/bct toon /noparse //if (!${Me.Mercenary.State.Equal[ACTIVE]}) /nomodkey /notify MMGW_ManageWnd MMGW_SuspendButton LeftMouseUp

/noparse /bct toon //if (!${Me.Mercenary.State.Equal[ACTIVE]}) /nomodkey /notify MMGW_ManageWnd MMGW_SuspendButton LeftMouseUp

Not sure what would happen.

/noparse /bct toon //if (!${Me.Mercenary.State.Equal[ACTIVE]}) /nomodkey /notify MMGW_ManageWnd MMGW_SuspendButton LeftMouseUp worked perfect. Now I can add merc handling to some of my macros without assuming remote mercs are up/down.

Thanks ctaylor!

 

[eqmule]

I thought that was what adding a \ after the $ does? like:

/bct toon //if (!$\{Me.Mercenary.State.Equal[ACTIVE]}) /nomodkey /notify MMGW_ManageWnd MMGW_SuspendButton LeftMouseUp

but I don't know, never tested that particular one, but I know

/bcg //bct ${Me} $\{Macro.Paused}

makes everyone in my group tell me if their macros are Paused or Running...

 

[Incognito]

Was thinkin same; \ in the right spot = /noparse. Haven't tested it, specially in EQBC...

 

[ctaylor22]

I thought that was what adding a \ after the $ does? like:

/bct toon //if (!$\{Me.Mercenary.State.Equal[ACTIVE]}) /nomodkey /notify MMGW_ManageWnd MMGW_SuspendButton LeftMouseUp

but I don't know, never tested that particular one, but I know

/bcg //bct ${Me} $\{Macro.Paused}

makes everyone in my group tell me if their macros are Paused or Running...

EQMule, does the $\{ trick only work with EQBC or is that for MQ2 code in general?

 

[eqmule]

I'm pretty sure that's eqbc specific, try it.

 

[ctaylor22]

I'm pretty sure that's eqbc specific, try it.

Thanks, I will later when I get home.

 

[vickvinegar]

Can always /alias the command and /bct //aliasname

 

[Incognito]

This has potential, glad this came up.

In another thread, we had trouble getting grp members to target someone using /bcg //tar ID ${Me.ID} because everyone would target the toon that sent the cmd since it would get parsed. Yes we discovered /tar myself and that solved it. However the noparse ($\) opens up a number of EQBC applications:

/bct toonname //tar ID $\{Me.ID}

I just tested that and it works, so by extension opens up myraid of unparsed cmd possibilities. I will have to think about practical applications...

- - - Updated - - -

and using the merc example above:

 /bct toon //if (!$\{Me.Mercenary.State.Equal[ACTIVE]}) /nomodkey /notify MMGW_ManageWnd MMGW_SuspendButton LeftMouseUp

Does work.

I had added an event to KA so with a single hotkey I could have my toons 'report' various stats; AA's in bank, % of current AA, Lvl, plat, DPSpaused setting (which I had altered), ReturnToCamp setting, ${Role}, Chase setting, and mana/end % etc. I hadn't got around to empty bag space yet.

Modding KA requires maintaining those mods across releases, could introduce aberrant behavior, limits support etc. Once I started using AutoCleric and AFNuke2 I had to consider adding similar events, the epitome of a slippery slope. Granted some of the reported settings are KA specific (and having to do with my mods) but a slimmed down version could be built into a hotkey for all toons regardless of what mac, if any, they are running, from any toon:

/bcg //bct ${Me.Name} Lvl: $\{Me.Level} - PctLvl: $\{Me.PctExp}  - AA: $\{Me.AAPoints} - Plat: $\{Me.Platinum} - Mana: $\{Me.PctMana}  - End: $\{Me.PctEndurance}  - Zone: $\{Zone}

That gives me a starting point so I can add or remove elements included in the report. I am mixing parsed and non-parsed elements; Parsed for the person to send the msg back to, and non-parsed so the various Me.Elements represent the recipient of the msg not the sender. This is powerful. I will endeavor to test various IF statements in an attempt to glean potential.

Just thought you should know.

~ The Incog

 

[Warl0ck45]

You may want to consider making an include file with your "additions" in it. Then you just need to include it and do minimum modifications to the actual macro. Something like how NinjaLoot or QuickBeg works. (off topic I know)

When I was rewriting DH macros I decided that instead of trying to maintain updates to X section on multiple macros, would be less work to make an include and modify just that file with what I was tinkering around with

 

[Tone]

I recommend making your own UI that you can store these actions with // connect with a separate client // that way you aren't saving these commands inside EQgame ... if you are paranoid.
I macro MQ2 commands all the time, but it's just an extra step if you want to be careful.

Jimbob released a UI that can do most of what I described... just limited # of buttons.


When I'm not 100% afk and driving either my bard or tank...

I have my own set of includes that I wrote that I include with kissassist... I have a set of keywords that it watches for in EQBC and reacts accordingly.
A lot of it is legacy / redundant from the old days when I played pre-kissassist... haven't had enough time yet to optimize the setup.