Determining if I am in a raid group.

[Wowguy25]

I need to make a custom trigger for some of my auras in weakauras. What I want it to do is to prevent the trigger from triggering if I am in a raid group (but not if I am in a party or solo). Weakauras accepts lua for custom triggers but seeing as I am a total noob at lua I am in need of some help.

I suspect I could use UnitInRaid("player") but I have no idea how to construct an actual lua function with it.

[Dridzt]

I believe you could accomplish that with the Load conditions without writing a custom trigger.

On the Load tab you'll find "Instance Type".
Checking it allows you to pick one from dropdown, clicking it again presents you with a multiple checkbox section for all instance types.
Just check the ones you want the aura to load in and leave the rest unchecked.

Custom trigger is also relatively easy.
You'd want
Custom Trigger:

function()
  return not IsInRaid() and true
end

Custom Untrigger:

function()
  return true
end

Generally speaking the dedicated WeakAuras forum is a better place for usage tips and self-help from the community.

This set of pages is also a good resource:
http://www.wowace.com/addons/weakauras/pages/

[Haleth]

Originally Posted by Dridzt function() return not IsInRaid() and true end

The and-operator here is redundant. You're comparing either 'false and true' or 'true and true'. Just 'not InInRaid()' should do.

[Dridzt]

Originally Posted by Haleth The and-operator here is redundant. You're comparing either 'false and true' or 'true and true'. Just 'not InInRaid()' should do.

In the general case that's correct but that's not how custom WeakAuras triggers evaluate.
It needs to be like that. (I should know as I've been doing maintenance work on it after MoP hit)

It's good practice to make sure you return a boolean as you won't be left wondering why they don't work when you rely on 1 or 0 being true.

[Phanx]

Maybe I'm missing something, but doesn't the use of "not" already guarantee a boolean result?

[Vlad]

Actually using the word "not" will always return a boolean value. "not nil" will become true and "not 0" will become false - so strictly speaking it should work just like, like Haleth mentioned.

[Dridzt]

You're not missing anything guys, I maybe worded it wrong, it is redundant in this particular case but users trying to write custom triggers in WeakAuras are best served by having a habit of making sure their custom trigger and untrigger functions return boolean true.

For example while if 1|0|table|'text' then will all evaluate to true for the purpose of the control structure they will not produce the desired result as part of a WeakAura trigger.

My reply was pertaining to the specific addon not Lua code in general, sorry for the confusion.

[Wowguy25]

Originally Posted by Dridzt (I should know as I've been doing maintenance work on it after MoP hit)

Thanks for your lua codes they work great! Since you seem like an expert on weakauras maybe you could help me with a new problem that just presented itself. I need to use full scan with spellID to detect spirit shell on my raid members because the shield buff and the buff from activating the ability itself have the same name. However I just noticed that you can not use unit id's for full scan, only player, target, focus or pet. Is there a reason for this? Ie is it just impossible? Or would it be possible for instance to make a custom trigger that could check for a specific spellID on a specific unit id?

Edit: Never mind! I found I was able to get around this by putting in the unit ID before I turned on full scan and it works. Still curious why the options are limited when you put on full scan though.

[Farmbuyer]

Originally Posted by Dridzt You're not missing anything guys, I maybe worded it wrong, it is redundant in this particular case but users trying to write custom triggers in WeakAuras are best served by having a habit of making sure their custom trigger and untrigger functions return boolean true.

That could be made infinitely more robust by having the WeakAuras calling code force the function return value to boolean, rather than relying on all its users to remember to do so. I'm surprised it hasn't already been done.