Question - Lua event help for griklor raid

[Overtimer]

I need to convert this to Lua. Can anyone smarter than me help?

/if (${Spawn[=${EventArg1}].ID}==${Me.ID})


I am trying to write Lua event for Griklor chase part.

Thanks.




This is the answer:

For this event, Griklor only names and does not target you.
Also, he only names you on one of the emotes.

When he points at you, that is the only time you can get a name from him. This gave me headaches because I thought my code was not working.

This is the code for my question above, for those learning Lua.

----------------------------------------------------------------------
Use name if you want to know what name he picked.

local function event_handler(line, name)
if name == mq.TLO.Me.CleanName() then
-----------------------------------------------------------------------
Use target if you want to know what target he picked.

local function event_handler(line, target)
if target == mq.TLO.Me.CleanTarget() then
----------------------------------------------------------------------

 

[Daxchu]

I'm definitely not an expert but that just seems to be doing a check against an event trigger to see if Griklor has called out your current character's name. Looks like it came from the mq2event based script here; https://www.redguides.com/community/threads/mq2events-for-griklor-raid.84826/post-545698

In raid version of the event the person he calls out matters as that character will need to do something different from the other characters. I think the original script using events is this one; https://www.redguides.com/community/threads/mq2events-for-griklor-raid.84826/post-545698

Someone was working on similar raid version using Lua Events Manager (LEM) here; https://www.redguides.com/community/threads/mighty-lua-event-manager.82347/post-525615

Are you doing group or raid version?

For the group event version, doesn't matter too much who he calls out, you would just want to have an event for his call and then possibly move your group to him and do stuff so the check against ${Me.ID} is probably not needed.

 

[Overtimer]

This is for a raid, we have many boxes in the raid and it's a nightmare for us.

Trying to get that name he called to compare to the toon is not working. That command is different from any Lua I have seen.

${Spawn[=${EventArg1}].ID}

 

[Psy]

For what it's worth when we do Grik in our guild we just have that player pause all toons they control and run to Grik. Might not work for your situation but maybe.

 

[Szazor]

There are a few issues with Chasing Griklor. His aura actually seems to be in-front of him - so if you try and run from behind and use stick..you miss it.
However - you can use that to your advantage.

Stand your raid in his path and when he is coming to you he will emote.
Use this in the MQ2Events.ini

[GriklorChase]
trigger=#*#Griklor the Restless roars and points at#1#.
command=/if (${EventArg1.Find[${Me.CleanName}]}) /multiline ; /rsay Chasing Griklor; /docommand /boxr pause; /nav id ${Spawn[Griklor the Restless].ID}; /timed 100 /docommand /boxr unpause


The toon that is target will run towards Griklor, and then Have a second hot key "COME TO ME" that will tell everyone to run to you. Boom every time your toon will path back through Grik's aura and you will get the success emote.

COME TO ME = /dgza /nav id ${Me.ID}

/dgza = everyone in zone.

 

[Overtimer]

Thank you guys, but I am trying to get everyone in my guild to start using the Lua Event Manager.

The guild leader wants everyone to be using this format moving forward.

I got Lua working, but everyone moves, I am having problems just selecting the player being called out.

 

[Daxchu]

The condition you mention should just be matching the person named by Griklor to the person checking the condition. Only the person matched should then do the rest of the actions.
Szazor was working on a LEM entry for this raid as well here; https://www.redguides.com/community/threads/mighty-lua-event-manager.82347/post-525615
There were some suggestions on syntax error correction a couple posts down from that one.
Seems like that was the right track. Everyone running LEM would have the same event. Each character checks their own name against the person Griklor mentions. If you are called, then stop everything and run to him, etc.

 

[Shadow]

LEM is the way to do it, you just have to be clear with the syntax and commands of what you want to process. You can alter the text triggers/spawn id so you can test using group, raid chats to see if it works. Be creative.

 

[Overtimer]

I don't think you understand what is going on here. Let me show some examples.
See the green text color is the key.

#*#Aten Ha Ra points at |${Me.Name}|#*#

MQ2 code:
/docommand ${If[${EventArg1.Equal[${Me}]}

Lua code:
local function event_handler(line, target)
if (target == my_name) then

-----------------------------------------------------------------------------------------------------

#*#The ice encrusted Avatar of War shouts that #1# must bend the knee!#*#

MQ2 code:
/if !${Me.Ducking})

Lua code:
local function event_handler(line, name)
if name == mq.TLO.Me.CleanName() and not mq.TLO.Me.Ducking() then

-------------------------------------------------------------------------------------------------------

#*#Griklor the Restless roars and points at#1#.

MQ2 code:
/if (${Spawn[=${EventArg1}].ID}==${Me.ID})

Lua code: Everything I have tried does not work, this is where I am stuck.

 

[aquietone]

LEM does not support the variable replacement in the event string like MQ2Events. You can't put |${Me.Name}| in the event.
Instead, try just #1# and then find if your name is the name in #1# in the event code.

 

[Drognir]

I don't think you understand what is going on here. Let me show some examples.
See the green text color is the key.

#*#Aten Ha Ra points at |${Me.Name}|#*#

MQ2 code:
/docommand ${If[${EventArg1.Equal[${Me}]}

LUA code:
local function event_handler(line, target)
if (target == my_name) then

-----------------------------------------------------------------------------------------------------

#*#The ice encrusted Avatar of War shouts that #1# must bend the knee!#*#

MQ2 code:
/if !${Me.Ducking})

LUA code:
local function event_handler(line, name)
if name == mq.TLO.Me.CleanName() and not mq.TLO.Me.Ducking() then

-------------------------------------------------------------------------------------------------------

#*#Griklor the Restless roars and points at#1#.

MQ2 code:
/if (${Spawn[=${EventArg1}].ID}==${Me.ID})

LUA code: Everything I have tried does not work, this is where I am stuck.

One potential issue that I see in your example is with this #*#Griklor the Restless roars and points at#1#.

There should likely be a space between "at" and "#1#" so that it looks like this #*#Griklor the Restless roars and points at #1#.

 

[Overtimer]

Copy and paste that from this site, lol. My version has the space.
Thank you.

 

[Drognir]

Copy and paste that from this site, lol. My version has the space.
Thank you.

Oh...welp. No problem

 

[Overtimer]

LEM does not support the variable replacement in the event string like MQ2Events. You can't put |${Me.Name}| in the event.
Instead, try just #1# and then find if your name is the name in #1# in the event code.

I would use this? I know you said compare name, correct.

local function event_handler(line, name)
or
local function event_handler(line, target)

 

[Shadow]

I don't think you understand what is going on here. Let me show some examples.
See the green text color is the key.

#*#Aten Ha Ra points at |${Me.Name}|#*#

MQ2 code:
/docommand ${If[${EventArg1.Equal[${Me}]}

LUA code:
local function event_handler(line, target)
if (target == my_name) then

-----------------------------------------------------------------------------------------------------

#*#The ice encrusted Avatar of War shouts that #1# must bend the knee!#*#

MQ2 code:
/if !${Me.Ducking})

LUA code:
local function event_handler(line, name)
if name == mq.TLO.Me.CleanName() and not mq.TLO.Me.Ducking() then

-------------------------------------------------------------------------------------------------------

#*#Griklor the Restless roars and points at#1#.

MQ2 code:
/if (${Spawn[=${EventArg1}].ID}==${Me.ID})

LUA code: Everything I have tried does not work, this is where I am stuck.

Have you tried looking at previous examples in the LEM Library that has basically the same text triggers, and going off that?

 

[Overtimer]

Have you tried looking at previous examples in the LEM Library that has basically the same text triggers, and going off that?

Yes, those are different triggers, they seems to be the same but are not.

 

[Shadow]

Yes, those are different triggers, they seems to be the same but are not.

Define seeming to be the same but not? The trigger. Not what actions were taken, the trigger.

 

[Overtimer]

Define seeming to be the same but not? The trigger. Not what actions were taken, the trigger.

Avatar of War shouts uses the local function event_handler(line, name)

Aten Ha Ra points at uses local function event_handler(line, target)

Both use texts, but are handle differently.

 

[aquietone]

the arguments to the event handler function is dependent on how many #1# capture things your event string has. #*# do not count.

#*#Griklor the Restless roars and points at #1#
this has 1, #1#. so the event handler would take (line, arg1)

#*#Aten Ha Ra points at #1#
this has 1, #1#. so the event handler would take (line, arg1)

#*#The ice encrusted Avatar of War shouts that #1# must bend the knee!#*#
this has 1, #1#. so the event handler would take (line, arg1)

arg1 name doesn't matter. call it whatever is relevant. in some cases people have called it name because they expect it to have a player name. in others they may have called it target because its the person targeted by the event? its just a variable name.

 

[Overtimer]

the arguments to the event handler function is dependent on how many #1# capture things your event string has. #*# do not count.

#*#Griklor the Restless roars and points at #1#
this has 1, #1#. so the event handler would take (line, arg1)

#*#Aten Ha Ra points at #1#
this has 1, #1#. so the event handler would take (line, arg1)

#*#The ice encrusted Avatar of War shouts that #1# must bend the knee!#*#
this has 1, #1#. so the event handler would take (line, arg1)

arg1 name doesn't matter. call it whatever is relevant. in some cases people have called it name because they expect it to have a player name. in others they may have called it target because its the person targeted by the event? its just a variable name.

Correct, and that makes sense to me now.

Good news I think I got this working, I will post full code once tested on raid mode.
Look for it Lua event manager soon.

If I do not post it I failed, lol.

 

[Overtimer]

Small update:

I tested this with my 6 toons with a mixture of plugin and Kiss Assist, using boxr commands.
I did this at the group and raid missions. I am limited with the raid, because of only having 6 toons, lol.

This works great so far, only problem I am having is when he drops, they do not return back to where they was at.
Only happens when he lands, not when he keeps flying, I need to figure out why that is happening.

Servers are down atm, so I cannot test this further.

 

[Shadow]

Small update:

I tested this with my 6 toons with a mixture of plugin and Kiss Assist, using boxr commands.
I did this at the group and raid missions. I am limited with the raid, because of only having 6 toons, lol.

This works great so far, only problem I am having is when he drops, they do not return back to where they was at.
Only happens when he lands, not when he keeps flying, I need to figure out why that is happening.

Servers are down atm, so I cannot test this further.

There are two triggers, so two separate LEM's. One for the initial callout and run to Grik, one for the drop.

 

[Trapper]

they do not return back to where they was at.

we use to do this raid with a macro before Lua. what I had in it was both a 15s timer, and an event for :

#Event GrikSuccess "#*#Griklor the Restless tries to control his mount as shards of deadly ice strike it#*#"

basically when timer ran out or the 2nd event fired then it would nav to raid main assist.

and it always worked perfectly.
good luck.

 

[Overtimer]

There are two triggers, so two separate LEM's. One for the initial callout and run to Grik, one for the drop.

I do have two triggers, hence why its works when he stay up flying. They only stop working when he drops to the ground.

 

[Overtimer]

we use to do this raid with a macro before lua. what I had in it was both a 15s timer, and an event for :

#Event GrikSuccess "#*#Griklor the Restless tries to control his mount as shards of deadly ice strike it#*#"

basically when timer ran out or the 2nd event fired then it would nav to raid main assist.

and it always worked perfectly.
good luck.

Yes I do have that second event up and running, and works well.

Only fails when he drops to the ground.

 

[Trapper]

Only fails when he drops to the ground.

I haven't done it in a long time, but that must have been what the 15s timer was for. so it would still return on the drop.

 

[Shadow]

Well, technically there are 3 emotes, but you only asked about the run to, and drop...so I just made the assumption you were good. Look at all 3, and design your LEM's around them. Similar to AoW. Duck, Stand, Move. Griklor has 3 as well. Run to him, tries to stay on his mount (run back) and drop.

I have LEMs for pretty much everything I have access to, and some for my guild members that have been tested. But because they are raid related - they stay on the down-low and in-house. Which is a pretty common theme in this community.

I always say by the end of my time here, I will probably have more than 500 different LEM's for everything.

 

[Overtimer]

Well, technically there are 3 emotes, but you only asked about the run to, and drop...so I just made the assumption you were good. Look at all 3, and design your LEM's around them. Similar to AoW. Duck, Stand, Move. Griklor has 3 as well. Run to him, tries to stay on his mount (run back) and drop.

I have LEMs for pretty much everything I have access to, and some for my guild members that have been tested. But because they are raid related - they stay on the down-low and in-house. Which is a pretty common theme in this community.

I always say by the end of my time here, I will probably have more than 500 different LEM's for everything.

Thank you, and I understand why some of these things are not being shared.

If someone told me not to shared I would respect that and not share it.

 

[Hylander]

Well, technically there are 3 emotes, but you only asked about the run to, and drop...so I just made the assumption you were good. Look at all 3, and design your LEM's around them. Similar to AoW. Duck, Stand, Move. Griklor has 3 as well. Run to him, tries to stay on his mount (run back) and drop.

I have LEMs for pretty much everything I have access to, and some for my guild members that have been tested. But because they are raid related - they stay on the down-low and in-house. Which is a pretty common theme in this community.

I always say by the end of my time here, I will probably have more than 500 different LEM's for everything.

Dude 500 LEMs ? Really ? How many raids do you have scripted? That’s like the last 10 expacs worth of raids

 

[Szazor]

You dont really need an action for the Second Emotes.

Assuming your toons are in Chase mode at the start

Then you get emoted,
then you /boxr Pause
then run to Griklor and get the trigger
then /boxr unpause

You will run back to your group. The only thing that may stop that is if you have done a /stick Griklor or something like that.


Some folks are reluctant to share strategy and LEM for current events because they are selling stuff for real money or have secret strats for current content - but TOV is not really current anymore - so I dont think anyone has any problems with sharing old stuff like this.

 

[Overtimer]

I can be very stupid at times, or most of the time, lol.

I figured out what I was doing wrong. This event has 5 emotes if you really want to script it all the way.

When he lands it is a different emote and there is no name attached to him, this has to be some creative programming that has to be done.
1 & 2 perfectly work 100% all the time. I am going to redo 2 so 3 can work.

Emote list:

1) Call your name.
2) Throw ice at you.
3) Lands on the ground.
4) Whistle when he leaves the ground.
5) AE is coming.

I finally found a guild I can play with, unfortunately for them, I am probably the most talented for programming, they are doomed, lol.
These are very cool and nice people, and they are very helpful. I need to help them as much as I can. We are just 8 of us.

 

[Tebus]

I can be very stupid at times, or most of the time, lol.

I figured out what I was doing wrong. This event has 5 emotes if you really want to script it all the way.

When he lands it is a different emote and there is no name attached to him, this has to be some creative programming that has to be done.
1 & 2 perfectly work 100% all the time. I am going to redo 2 so 3 can work.

Emote list:

1) Call your name.
2) Throw ice at you.
3) Lands on the ground.
4) Whistle when he leaves the ground.
5) AE is coming.

I finally found a guild I can play with, unfortunately for them, I am probably the most talented for programming, they are doomed, lol.
These are very cool and nice people, and they are very helpful. I need to help them as much as I can. We are just 8 o

I can be very stupid at times, or most of the time, lol.

I figured out what I was doing wrong. This event has 5 emotes if you really want to script it all the way.

When he lands it is a different emote and there is no name attached to him, this has to be some creative programming that has to be done.
1 & 2 perfectly work 100% all the time. I am going to redo 2 so 3 can work.

Emote list:

1) Call your name.
2) Throw ice at you.
3) Lands on the ground.
4) Whistle when he leaves the ground.
5) AE is coming.

I finally found a guild I can play with, unfortunately for them, I am probably the most talented for programming, they are doomed, lol.
These are very cool and nice people, and they are very helpful. I need to help them as much as I can. We are just 8 of us.

Awesome work! Thanks for furthering us along!

 

[Shadow]

I can be very stupid at times, or most of the time, lol.

I figured out what I was doing wrong. This event has 5 emotes if you really want to script it all the way.

When he lands it is a different emote and there is no name attached to him, this has to be some creative programming that has to be done.
1 & 2 perfectly work 100% all the time. I am going to redo 2 so 3 can work.

Emote list:

1) Call your name.
2) Throw ice at you.
3) Lands on the ground.
4) Whistle when he leaves the ground.
5) AE is coming.

I finally found a guild I can play with, unfortunately for them, I am probably the most talented for programming, they are doomed, lol.
These are very cool and nice people, and they are very helpful. I need to help them as much as I can. We are just 8 of us.

What are you having difficulties with?

Trigger 1 matters.
Trigger 2 doesn't matter as you can obviously timeout Trigger 1.
Trigger 3 really doesn't matter as you are watching for that specifically, however you could nav automatically.
Trigger 4 matters to keep better automatic control and prevent the wayward toons chasing after Grik in the air. You can spam followme, cleartarget, etc...but KA toons in particular like to keep going...
Trigger 5 matters.

 

[Overtimer]

What are you having difficulties with?

Trigger 1 matters.
Trigger 2 doesn't matter as you can obviously timeout Trigger 1.
Trigger 3 really doesn't matter as you are watching for that specifically, however you could nav automatically.
Trigger 4 matters to keep better automatic control and prevent the wayward toons chasing after Grik in the air. You can spam followme, cleartarget, etc...but KA toons in particular like to keep going...
Trigger 5 matters.

Trigger 1 Works perfect.

Trigger 2 Works perfect, but I am going to change what I did, so 3 will be the same.
I had anyone that was called to /nav xyz. Going to change that to /chase, if you're not a assist melee. IF a assist melee /nav xyz. I have to write it and test it.

Trigger 3 will put you in /chase, if you're not a assist melee. IF a assist melee /nav xyz. I have to write it and test it.

Trigger 4 Have not started on that yet.

Trigger 5 Have not started on that yet.

 

[Shadow]

Trigger 1 Works perfect.

Trigger 2 Works perfect, but I am going to change what I did, so 3 will be the same.
I had anyone that was called to /nav xyz. Going to change that to /chase, if you're not a assist melee. IF a assist melee /nav xyz. I have to write it and test it.

Trigger 3 will put you in /chase, if you're not a assist melee. IF a assist melee /nav xyz. I have to write it and test it.

Trigger 4 Have not started on that yet.

Trigger 5 Have not started on that yet.

Trigger 3 is the drop message - simple nav spawn to him works if you want it automated unless you are looking at specific tank spots at the log locations to position him to.

Trigger 4 is confusing as there are technically 2 messages related to air, but only one applies to him going up - the whistle. That is a simple, back off, clear target, etc commands.

Trigger 5 should be a nav to Bethun as Bethun chooses the spot where he heals I believe. I am not sure if that is random, triggered by something else, etc atm. I need to do further research. But a nav Bethun should suffice.

 

[Overtimer]

Thank you, sir.

 

[Overtimer]

Ok, this is what I am done so far, please let me know if I can improve on it.

These are not the final version, use them at your own risk, just for testing. Updated: 03/20/2023

Griklor the restless roars and points at<<<<<<Everyone tags this one.

cmV0dXJuIHsKIGxvYWQgPSB7CiAgYWx3YXlzID0gZmFsc2UsCiAgY2xhc3MgPSAiIiwKICB6b25lID0gIiIsCiB9LAogY29kZSA9ICJiRzlqWVd3Z2JYRTljbVZ4ZFdseVpTZ25iWEVuS1Fwc2IyTmhiQ0JtZFc1amRHbHZiaUJsZG1WdWRGOW9ZVzVrYkdWeUtHeHBibVVzSUc1aGJXVXBDaUFnSUNCcFppQnVZVzFsSUQwOUlHMXhMbFJNVHk1TlpTNURiR1ZoYms1aGJXVW9LU0IwYUdWdUlBb2dJQ0FnSUcxeExtTnRaQ2duTDI1aGRpQnpjR0YzYmlCSGNtbHJiRzl5SnlrS0lDQWdJQ0J0Y1M1amJXUW9KeTkwWVhJZ1IzSnBhMnh2Y2ljcENpQWdJQ0FnYlhFdVkyMWtLQ2N2WW05NGNpQlFZWFZ6WlNjcENpQWdJQ0FnY21Wd1pXRjBDaUFnSUNBZ2RXNTBhV3dnYlhFdVZFeFBMbFJoY21kbGRDNUVhWE4wWVc1alpTZ3BJRHdnTmdvZ0lDQWdJRzF4TG1OdFpDZ25MM04wYVdOcklHOXVKeWtLSUNBZ0lDQnRjUzVrWld4aGVTZzVNREF3S1FvZ0lDQWdJRzF4TG1OdFpDZ25MM1JoY2lCamJHVmhjaWNwQ2lBZ0lDQWdiWEV1WTIxa0tDY3ZjM1JwWTJzZ2IyWm1KeWtLSUNBZ0lDQnRjUzVqYldRb0p5OWliM2h5SUhWdWNHRjFjMlVuS1FvZ0lDQWdJRzF4TG1OdFpDZ25MMjVoZGlCc2IyTjRlWG9nSURrM0xqZzVJREUzTUM0d01DQXROREV1TmpJd0p5a0tJQ0FnSUdWdVpBb2dJQ0FnSUFvZ0lDQWdDbVZ1WkNBZ0NuSmxkSFZ5YmlCN1pYWmxiblJtZFc1alBXVjJaVzUwWDJoaGJtUnNaWEo5IiwKIGNhdGVnb3J5ID0gIlRPViIsCiB0eXBlID0gImV2ZW50cyIsCiBuYW1lID0gIkdyaWtsb3IgdGhlIFJlc3RsZXNzIHJvYXJzIGFuZCBwb2ludHMgYXQiLAogcGF0dGVybiA9ICIjKiNHcmlrbG9yIHRoZSBSZXN0bGVzcyByb2FycyBhbmQgcG9pbnRzIGF0ICMxIy4jKiMiLAp9

Causing Griklor to fall to the ground<<<<<<< Only the Main Tank.

cmV0dXJuIHsKIGxvYWQgPSB7CiAgYWx3YXlzID0gZmFsc2UsCiAgY2xhc3MgPSAiIiwKICB6b25lID0gIiIsCiB9LAogY29kZSA9ICJiRzlqWVd3Z2JYRTljbVZ4ZFdseVpTZ25iWEVuS1FvS2JHOWpZV3dnWm5WdVkzUnBiMjRnWlhabGJuUmZhR0Z1Wkd4bGNpZ3BDbTF4TG1OdFpDZ25MM1JoY2lCSGNtbHJiRzl5SnlrS2JYRXVZMjFrS0NjdmJtRjJJSE53WVhkdUlFZHlhV3RzYjNJbktRcHlaWEJsWVhRS2RXNTBhV3dnYlhFdVZFeFBMbFJoY21kbGRDNUVhWE4wWVc1alpTZ3BJRHdnTmdwdGNTNWtaV3hoZVNneE1EQXBDbTF4TG1OdFpDZ25MMkYwZEdGamF5QnZiaWNwQ21WdVpDQWdJQXB5WlhSMWNtNGdlMlYyWlc1MFpuVnVZejFsZG1WdWRGOW9ZVzVrYkdWeWZRPT0iLAogY2F0ZWdvcnkgPSAiVE9WIiwKIHR5cGUgPSAiZXZlbnRzIiwKIG5hbWUgPSAiY2F1c2luZyBHcmlrbG9yIHRvIGZhbGwgdG8gdGhlIGdyb3VuZCIsCiBwYXR0ZXJuID0gIiMqI2NhdXNpbmcgR3Jpa2xvciB0byBmYWxsIHRvIHRoZSBncm91bmQjKiMiLAp9

Griklor lets out a tuneless whistle<<<<<<<<< Everyone tags this one.

cmV0dXJuIHsKIGxvYWQgPSB7CiAgYWx3YXlzID0gZmFsc2UsCiAgY2xhc3MgPSAiIiwKICB6b25lID0gIiIsCiB9LAogY29kZSA9ICJiRzlqWVd3Z2JYRTljbVZ4ZFdseVpTZ25iWEVuS1Fwc2IyTmhiQ0JtZFc1amRHbHZiaUJsZG1WdWRGOW9ZVzVrYkdWeUtDa0tiWEV1WTIxa0tDY3ZkR0Z5SUdOc1pXRnlKeWtLYlhFdVkyMWtLQ2N2Y0dWMElITjNiR1ZoZG1VbktRcHRjUzVrWld4aGVTZ3hNREFwQ20xeExtTnRaQ2duTDNCbGRDQmlZV05ySUc5bVppY3BDbTF4TG1SbGJHRjVLREV3TUNrS2JYRXVZMjFrS0NjdllYUjBZV05ySUc5bVppY3BDbVZ1WkNBZ0lBcHlaWFIxY200Z2UyVjJaVzUwWm5WdVl6MWxkbVZ1ZEY5b1lXNWtiR1Z5ZlE9PSIsCiBjYXRlZ29yeSA9ICJUT1YiLAogdHlwZSA9ICJldmVudHMiLAogbmFtZSA9ICJHcmlrbG9yIGxldHMgb3V0IGEgdHVuZWxlc3Mgd2hpc3RsZSIsCiBwYXR0ZXJuID0gIiMqI0dyaWtsb3IgbGV0cyBvdXQgYSB0dW5lbGVzcyB3aGlzdGxlIyojIiwKfQ==

Gather This fire should protect you from the sleet<<<<<<<<<Everyone tags this one.
[CODE title="LEM"]cmV0dXJuIHsKIGxvYWQgPSB7CiAgYWx3YXlzID0gZmFsc2UsCiAgY2xhc3MgPSAiIiwKICB6b25lID0gIiIsCiB9LAogY29kZSA9ICJiRzlqWVd3Z2JYRTljbVZ4ZFdseVpTZ25iWEVuS1Fwc2IyTmhiQ0JtZFc1amRHbHZiaUJsZG1WdWRGOW9ZVzVrYkdWeUtDa0tiWEV1WkdWc1lYa29NVEF3S1FwdGNTNWtaV3hoZVNneE1EQXBDbTF4TG1OdFpDZ25MMjVoZGlCemNHRjNiaUJDWlhSb2RXNG5LUXBsYm1RZ0lDQUtjbVYwZFhKdUlIdGxkbVZ1ZEdaMWJtTTlaWFpsYm5SZmFHRnVaR3hsY24wPSIsCiBjYXRlZ29yeSA9ICJUT1YiLAogdHlwZSA9ICJldmVudHMiLAogbmFtZSA9ICJHYXRoZXIgVGhpcyBmaXJlIHNob3VsZCBwcm90ZWN0IHlvdSBmcm9tIHRoZSBzbGVldCIsCiBwYXR0ZXJuID0gIiMqI0dhdGhlciEgVGhpcyBmaXJlIHNob3VsZCBwcm90ZWN0IHlvdSBmcm9tIHRoZSBzbGVldCEjKiMiLAp9[/CODE]

 

[Overtimer]

See post 1 for the answer to my original question.

Added Gather This fire should protect you from the sleet.

I will post this to the Event manager thread if I feel this is working well.

 

[Shadow]

Checked out your LEM's, and going to offer a couple of questions to think about improvements. Will work backward if that's ok. Please, this is not a slight, or anything, and maybe it is this simple and will work. I do not know personally, as I am waiting for a lockout to clear before my own personal attempt on him. I am only coming at this from a logical standpoint with my experience with other targets, LEMs I have built and tested. I have my own LEM's I built for this event, but built after the lockout was already in place, so testing will be done soon.

1. Assume you have 54 in the raid, you have the sleet trigger issue a /gsay command, which means everyone will spam gsay at the same time, which is bound to induce lag at the time you are initiating a nav spawn command. Do you really need to be informed 54 times that the sleet is incoming?

2. What happens when you nav to Bethun, and the chars are in chase mode? Don't make it because of lag? Got hung up on a log, in a hole, wall, etc based on the previous positioning? What do Berserkers do in case they had already popped Frenzy? What happens when the chars get there? Why would you target Bethun if you are nav spawning to him? What if adds are up?

3. Just pet classes? From hearing others' personal experiences of them doing this raid from my guildmates, KA/MA classes are notorious for following Grik into the air and chasing him around. They have to spam the backoff/cometome hotkeys to get them to return.

4. Griklor comes down, your tank goes to him, and sticks to him. I haven't messed with stick on in a while, does it prevent the effective moving of Grik? From my understanding, Sleet is roughly 90 secs in duration, and can be triggered while Grik is in air, on ground, etc.

Will stop there with the questions...some food for thought.

 

[Overtimer]

Checked out your LEM's, and going to offer a couple of questions to think about improvements. Will work backward if that's ok. Please, this is not a slight, or anything, and maybe it is this simple and will work. I do not know personally, as I am waiting for a lockout to clear before my own personal attempt on him. I am only coming at this from a logical standpoint with my experience with other targets, LEMs I have built and tested. I have my own LEM's I built for this event, but built after the lockout was already in place, so testing will be done soon.

1. Assume you have 54 in the raid, you have the sleet trigger issue a /gsay command, which means everyone will spam gsay at the same time, which is bound to induce lag at the time you are initiating a nav spawn command. Do you really need to be informed 54 times that the sleet is incoming?

2. What happens when you nav to Bethun, and the chars are in chase mode? Don't make it because of lag? Got hung up on a log, in a hole, wall, etc based on the previous positioning? What do Berserkers do in case they had already popped Frenzy? What happens when the chars get there? Why would you target Bethun if you are nav spawning to him? What if adds are up?

3. Just pet classes? From hearing others' personal experiences of them doing this raid from my guildmates, KA/MA classes are notorious for following Grik into the air and chasing him around. They have to spam the backoff/cometome hotkeys to get them to return.

4. Griklor comes down, your tank goes to him, and sticks to him. I haven't messed with stick on in a while, does it prevent the effective moving of Grik? From my understanding, Sleet is roughly 90 secs in duration, and can be triggered while Grik is in air, on ground, etc.

Will stop there with the questions...some food for thought.

1) Good Point was using it for troubleshooting will leave it till everyone in my guild says it's working, but it will be removed before the raid. Need to make sure to remove it, lol.
2) No one can be in chase mode, this LEM is designed for that very point. I haven't thought about the Berserkers, will look into that, thanks. Just in case they get hung up on a different target. I need to see how that works.>>> /tar command.
3) My description is wrong, everyone will get it. I have code for them too.
4) Sticks works great if you're right on top of him. If you too far, you might get stuck. This is why I created a loop on>> /nav I wanted to make sure on top of him.

Thank you, will fix some of these things.