Reason for repeat lines in User Macros?

[Prythwin]

I appreciate the info! Though that doesnt answer the question I was asking.

while raiding I am clicking a lot of things very quickly. Of course animation lock is a thing. when I use my shirk macro I have to use it directly after an animation of one of my GDCs which locks me from casting. If I cast the macro while the animation is still going it cancels my macro so I end up having to time it perfectly and cannot queue it.

I was asking if my above examples would help queue the action and help to ensure that it casts.

[Canadane]

I was asking if my above examples would help queue the action and help to ensure that it casts.

No, macros cannot use the native skill queuing at all.
They will always be worse than manually executing a move. This was by design.

[MicahZerrshia]

I appreciate the info! Though that doesnt answer the question I was asking...

It does tho, like I said, whether you are rapid firing the macro or other skills, if you hit anything else before that macro executes you are cancelling the macro. So whether you have 1 line or 14, you need to hit and and then hit nothing else until that ability is used. This is why macros are so horribly bad to use in combat. It has no queue, its a use it or lose it thing. The only time macros have ever been useful in combat is to let other players know when you are doing something, but honestly with the changes to combat over the years there is really nothing going on anymore that you need to inform your other players you are doing.

Even raise macros are normally worthless since by the time your macro informs me of who you are raising, much less executes, most likely I will have already hit swiftcast and raise anyway. Like Canadane said, they made macros work this way by design. We are not meant to use them in combat.