[suggestion] <chain> macro tag

sometimes it happens that while executing a macro the lag makes it skip a line.
would it be possible to add a <chain> tag to the macro system (kinda like the current <wait n>) so that the next command is executed as soon as possible ignoring any possible lag?

I'd be in support of something like this, but most likely the Devs would say something to the effect of "too automated" on its own. I think in a case like that, the entire system should be changed so that you still have to put the proper <wait> value in, but the system would make sure that the macro is fired line for line.

Hmm... Guess I don't know watcha mean unless you mean self skill chains where it skips the damage of the Darkness or whatever. That's only time I've seen lag kill a message. Guess I've been lucky. XD If that IS what you mean I usually put the <wait> 1 ish seconds longer before it switches back to your DoT gear and that worked for me. Sorry if that's not what you meant. Like I said, must just been lucky.

Quote:

---

Originally Posted by Seyomeyo

I'd be in support of something like this, but most likely the Devs would say something to the effect of "too automated" on its own. I think in a case like that, the entire system should be changed so that you still have to put the proper <wait> value in, but the system would make sure that the macro is fired line for line.

---

well, it would be a little contradictory since the theory of a macro is to make automatic something that you would have to repeat manually from time to time.

Quote:

---

Originally Posted by Infidi

Hmm... Guess I don't know watcha mean unless you mean self skill chains where it skips the damage of the Darkness or whatever. That's only time I've seen lag kill a message. Guess I've been lucky. XD If that IS what you mean I usually put the <wait> 1 ish seconds longer before it switches back to your DoT gear and that worked for me. Sorry if that's not what you meant. Like I said, must just been lucky.

---

i currently have:
/ja "assassin's charge" <me> <wait 1>
/ja "bully" <t> <wait 1>
/ja "sneak attack" <me> <wait 1>
/ws "mercy stroke" <t>

sometimes the ws or bully is not executed.

i would like to change it with the following:
/ja "assassin's charge" <me> <chain>
/ja "bully" <t> <chain>
/ja "sneak attack" <me> <chain>
/ws "mercy stroke" <t>

Basically its a problem COR's have had, and I suppose other jobs as well, where in a COR's case they accidentally shoot the bullet from Akvan due to lag during a macro.

Quote:

---

Originally Posted by Infidi

Hmm... Guess I don't know watcha mean unless you mean self skill chains where it skips the damage of the Darkness or whatever. That's only time I've seen lag kill a message. Guess I've been lucky. XD If that IS what you mean I usually put the <wait> 1 ish seconds longer before it switches back to your DoT gear and that worked for me. Sorry if that's not what you meant. Like I said, must just been lucky.

---

Skipping skillchain damage is not due to lag, but a bug in the client where if the WS animation is interrupted by blinking, all associated followup animations are also skipped. At the same time, there is a bug in the way the client displays log data, so it also skips log entries for animations that were completely skipped, in this case, the skillchain.

As for the actual topic, I think a <chain> or <queue> command would be a very good addition to the macro system. I do however think that a change like this would require additional server-side changes, not just client-side changes, like adding <wait #> (most likely) was.

I bet the bug is 'working as intended' too D:

Quote:

---

Originally Posted by Zohno

I currently have:
/ja "assassin's charge" <me>
/ja "bully" <t> <wait 1>
/ja "sneak attack" <me> <wait 1>
/ws "mercy stroke" <t>

sometimes the ws or bully is not executed.

---

You could just try making and using seperate macros for the JAs and ws, would eliminate chance of them not going off :P

Quote:

---

Originally Posted by Mayoyama

You could just try making and using seperate macros for the JAs and ws, would eliminate chance of them not going off :P

---

and increase the chance to waste any buff before the ws :p

To be fair though, you can do bully manually without any issues, as it usually always lasts over 20 seconds.

Quote:

---

Originally Posted by Mirage

To be fair though, you can do bully manually without any issues, as it usually always lasts over 20 seconds.

---

yes, but even just sa+ws can get lagged and it's not like only the thf would gain benefits from this. as demon pointed out before also the cor or rng who use a rare/ex bullet can lose it due to lag.

You have to put wait after each job ability.

Quote:

---

Originally Posted by Zohno

well, it would be a little contradictory since the theory of a macro is to make automatic something that you would have to repeat manually from time to time.



i currently have:
/ja "assassin's charge" <me>
/ja "bully" <t> <wait 1>
/ja "sneak attack" <me> <wait 1>
/ws "mercy stroke" <t>

sometimes the ws or bully is not executed.

i would like to change it with the following:
/ja "assassin's charge" <me>
/ja "bully" <t> <chain>
/ja "sneak attack" <me> <chain>
/ws "mercy stroke" <t>

---

Quote:

---

Originally Posted by Zohno

yes, but even just sa+ws can get lagged and it's not like only the thf would gain benefits from this. as demon pointed out before also the cor or rng who use a rare/ex bullet can lose it due to lag.

---

Yes, it wasn't meant as an argument against the idea. It is naturally still relevant for the other commands, just saying that he could lessen the chance of having the other commands fail if he did Bully separately :p.

Quote:

---

Originally Posted by Zohno

i currently have:
/ja "assassin's charge" <me> <wait 1>
/ja "bully" <t> <wait 1>
/ja "sneak attack" <me> <wait 1>
/ws "mercy stroke" <t>

sometimes the ws or bully is not executed.

---

Bold should make sure they're both done.

Quote:

---

Originally Posted by Nawesemo

Bold should make sure they're both done.

---

actually i've it in the macro. i forgot to add it here.

I noticed when I macro my JA's for zergs, it works better for me to have wait2s rather than wait1s.