[Request: Fix Macro Clipping ] Please support my initiative to fix macro clipping.

[Lord_Miakeus]

Ok Rongway refuting your points.

• Basically in my youtube video I didn't want to confuse the viewer by showing them anything other than what macro clipping is in action.
• I've demonstrated my knowledge of how macro clipping comes about in my earlier posts. I don't even know what you're trying to achieve by stating that I have grossly misunderstood something when I haven't.

What if I want to error chain different abilities/spells. What if I want to fire off my defensive cooldowns and change my hotbar page in the same macro while locking all macros?

I can do this currently with the current macro implementation.

The macros that I've created unfortunately clip each other.

Putting a macrolockrecast into the game makes combat macros spammable and is a fundamental element in any MMO's macro implementation. We don't have it in this game which is faulty game design. Plain and simple.

Do they want combat macros or not?

[Lygas]

... Putting a macrolockrecast into the game makes combat macros spammable and is a fundamental element in any MMO's macro implementation. We don't have it in this game which is faulty game design. Plain and simple.

Do they want combat macros or not?

No, making macros spammable is not a fundamental element in any macro implementation, much less MMOs specifically. Not having it isn't faulty game design, it's preferential game design. They do NOT want combat macros in the way you do.

[Rongway]

• Basically in my youtube video I didn't want to confuse the viewer by showing them anything other than what macro clipping is in action.
• I've demonstrated my knowledge of how macro clipping comes about in my earlier posts. I don't even know what you're trying to achieve by stating that I have grossly misunderstood something when I haven't.

You don't seem to undestand what macro clipping is.
If you have a macro that does the following:

/ac (Raise) <mo> <wait.1>
/p (Raise) >> <mo> (Just used it.)
/micon (Raise)

When you press it, it will try to Raise someone, then wait 1 second, then notify the party.
If you spam the button, it will run line 1 repeatedly until you stop spamming the button, because each subsequent button press interrupts the 1s wait. This is useful so that you don't spam the party with your Raise message. Once you stop spamming the button, the final iteration of the macro will run to completion and notify the party of the Raise.


Or a crafter might have a macro that performs a series of crafting actions.

/ac (Comfort Zone) <wait.3>
/ac (Tricks of the Trade) <wait.3>
/ac (Inner Quiet) <wait.3>
/ac (Tricks of the Trade) <wait.3>
/ac (Steady Hand II)

If you activate any other macro during those waits, it will abort the crafting macro and begin executing the new macro instead.


The /macrolock command prevents this from happening. If you insert it before the first line, then you will be unable to use any other macros until the crafting macro reaches the final line. This is definitely a bad idea in the Raise example, and probably not a terrible idea in the crafting example.

The lock releases immediately upon execution of the final line, and does not wait for any animations or cooldowns to expire.

Putting a macrolockrecast into the game makes combat macros spammable and is a fundamental element in any MMO's macro implementation.

/macrolock's purpose is specifically to make macros not spammable, to protect yourself from interrupting important action sequences.

But even then, as I said above, /macrolock doesn't care what animations or cooldowns are happening. It just wants to reach the last line and send it to execution.



What you are actually experiencing is how macros are excluded from the ability queue (see my previous post and this handy visual aid).




In your original post,

/macrolockrc 2.5
/ac "Hard Slash"

This would lock the macro for the recast period of hard slash.

You are proposing a "solution" to a problem that doesn't exist. That is, subsequent macros are already allowed to fire as soon as the macro reaches the Hard Slash line, regardless of whether or not it successfully activates Hard Slash. If you're having problems firing a second macro, it's not because of a /macrolock. It's because whatever abilities are in your second macro don't participate in the ability queue.



What you really need to do is abandon any hope for executing efficient sequences of combat actions, because the system is specifically designed so that it doesn't give you this advantage. If you want to execute combat actions efficiently, you have to do it manually. You can't script the game to play itself for you, unless you're willing to sacrifice a significant portion of your DPS.



And forget this nonsense:

Putting a macrolockrecast into the game makes combat macros spammable and is a fundamental element in any MMO's macro implementation. We don't have it in this game which is faulty game design. Plain and simple.

Do they want combat macros or not?

Efficient macros are not fundamental to anything; they're a convenience, and can come with whatever costs the devs want to levy, and they choose to make it so you can't be good if the game is playing itself for you. Plain and simple.

[Lord_Miakeus]

You don't seem to undestand what macro clipping is.

I don't have time to counterpoint your horrible post. I've defined macro clipping at the beginning of this thread. It is not an official term and I wont let you redefine it on me. Your first examples have nothing to do with macrolock or combat macros which means they are outside of the scope of this thread. Your images demonstrate how queuing and macros work, amazingly, despite how flashy this is it is outside of the scope of this thread and a waste of my time.

As much as I enjoyed being not enlightened on aspects of macros I had already researched and accused of being ignorant yet again I have to point out that this thread is about what people want not what the devs want.

You have demonstrated perfectly how flash impressed the masses rather than logic which I suppose why the human race is ultimately doomed to destroy itself. Please stop posting completely. For humanity.

[Martin_Arcainess]

Macros aint lines of code?!?!
Da hell are they then? Nusery rhymes?!