AQ, you are saying that this would be able to have a (lets say) 6 Button master bars, one for your driver and the other 5 with these 'broadcast timers' for far more stay on your driver character window?One random application of this:
Using it to broadcast timers which can then be used within buttonmaster, so that you can have hotkeys with cooldown timers for remote characters abilities:
The button created on some character other than the cleric:
View attachment 59530
The property added to SharedDataClient on the cleric:
Saw someone do this on project lazarus with e3next and thought it'd be neat to be able to do this without e3next.You could do similar with pre-configured DanNet observers as well.
Commits
local function MyBuffsFunction()
local MyBuffs = {}
local BuffStatus = false
local BuffName = "abc"
for i = 1 , 20 do
if mq.TLO.Me.Buff(i)() ~= nil then
BuffStatus = true
BuffName = mq.TLO.Me.Buff(i)()
MyBuffs[BuffName] = {BuffStatus}
end
end
return {MyBuffs}
end
