Macro curiosity

Did i miss something?

Due to lag i was forced to use /wait 2.5 in my macros as 2.0 would cause the macro to fail. The next spell in the sequence would fire mid cast of the previous. 3.0 would cause a small pause in between spell casts, wasting precious time. This meant i had to use 2.5 to ensure the least possible time between casts without having any spells in the queue fail.

Now with this new addition/alteration to the way wait commands are used 2.5 can no longer be used. As expected 2.0 causes the macro to fail and 3.0 is the lowest one that now works without causing any spells to fail.

Not sure what happened.

It appears we can only use full numbers for the new method. Rather annoying, but at least my crafting macros have been cut down to 1-2 macros now. Not good for battle macros, though.

Are you saying 2.5 doesn't work with the old syntax anymore? Or just that you can't use decimals with the new syntax?

For the new syntax, it's right there in the patch notes:

Quote:

---

* "number" can be any digit between 1 and 60.

---

Though they should probably say "integer" instead of "digit."

Also, even for the old syntax, they've stated in the past that it's supposed to round to the nearest second anyway, and that's an intentional design choice to keep macros from being as efficient as manual abilities. If 2.5 actually works and isn't just rounding to 3.0, I wouldn't be surprised if that got bug-fixed at some point.

While you could type 2.5 in the old system it rounded to 3 anyway. As Bixby said it was intentional to slightly gimp macros compared to a player.
And yes the new system only allows integers.

You seem to have missed something since the beta, since they were rounding the numbers all this time.

Also note that the Patch notes did not display properly. The Syntax change was to add <wait.1> at the end of a command

Quote:

---

Originally Posted by cotti

You seem to have missed something since the beta, since they were rounding the numbers all this time.

---

This. More people need to realize this.

You could use a decimal to your hearts content, but the system always rounded.

There was a post floating around somewhere (perhaps reddit?) that someone said rounding seemed to be broken. Instead of rounding up or down correctly, macros are just truncating. If accurate, this would explain why your 2.5 now acts like a 2 instead of a 3.

http://www.reddit.com/r/ffxiv/commen...mbers_work_in/

Quote:

---

Originally Posted by cotti

You seem to have missed something since the beta, since they were rounding the numbers all this time.

---

Then how come a value of 2 causes the next action to fail and 3 causes a casting delay but 2.5 works perfectly?

Quote:

---

Originally Posted by necrosis

Then how come a value of 2 causes the next action to fail and 3 causes a casting delay but 2.5 works perfectly?

---

This. /10chars

Regardless. It is all rendered moot now anyway. This is the way it is now so we just have to live with it.