Patch 2.16 Up! [Discuss]

[FabioThePunisher]

I don't know if a other ppl white this... all new things are quite good but i'm only really interest in one.... new <wait."#">
we really need that also decimal were be included and seen....
for example the first thing that i think

/ac Cure <me> <wait.2.50>
/ac Cure <me> <wait.2.50>

This is not working.... decimal are not seen so it's like

/ac Cure <me> <wait.2>
/ac Cure <me> <wait.2>

also i tried with <wait."2.5"> but not work aswell....

we cannot waste 0.5 second for each cast.... specially at high level... So please noticed that and try to solve... simply if possible... we could use <wait."#.##"> to enable decimal

[UBERHAXED]

That was intentional (waaaaay back in the beta days they explained it). You can't use decimals at all. This was done so it's never more effective to use macros than to do tasks manually. As you can see, even with the changes, you still can't use decimals. Although it appears that what you show is that it truncates the decimal. In the past, it was rounded (so inputting 2.5 would cast to 3 and inputting 2.49 would cast to 2).

[Ronyx]

I don't know if a other ppl white this... all new things are quite good but i'm only really interest in one.... new <wait."#">
we really need that also decimal were be included and seen....
for example the first thing that i think

/ac Cure <me> <wait.2.50>
/ac Cure <me> <wait.2.50>

This is not working.... decimal are not seen so it's like

/ac Cure <me> <wait.2>
/ac Cure <me> <wait.2>

also i tried with <wait."2.5"> but not work aswell....

we cannot waste 0.5 second for each cast.... specially at high level... So please noticed that and try to solve... simply if possible... we could use <wait."#.##"> to enable decimal

Decimals are working for me

Im using this.
/macroicon Infuriate
/ac "Infuriate" <me> <wait.1.5>
/ac "Steel Cyclone" <me>

Try not using the 0 just <wait.2.5>

[Gilraen]

Decimals are working for me

Im using this.
/macroicon Infuriate
/ac "Infuriate" <me> <wait.1.5>
/ac "Steel Cyclone" <me>

Try not using the 0 just <wait.2.5>

I have my attack combos macro'd, used /wait 2.5 and every action triggered in a timely manner. Tried <wait.2.5> and the second action was skipped each and every time. Seems the <wait.#> in my experience does not recognize .5 increments while /wait # does.

[Errors]

I have my attack combos macro'd, used /wait 2.5 and every action triggered in a timely manner. Tried <wait.2.5> and the second action was skipped each and every time. Seems the <wait.#> in my experience does not recognize .5 increments while /wait # does.

/wait accepts decimals but rounds the value. Has been like this since beta.

1.0 = 1 second
1.1 = 1 seconds
1.2 = 1 seconds
1.3 = 1 seconds
1.4 = 1 seconds
1.5 = 2 seconds
1.6 = 2 seconds
1.7 = 2 seconds
1.8 = 2 seconds
1.9 = 2 seconds
2.0 = 2 seconds

[Felis]

I haven't logged in yet, but... I thought that's what this patch was? x.x You're saying it's not the ticky boxes for quest tracking? *weeps*

This come also with 2.2

Greetings,

Below is an update from Hiroshi Minagawa in regards to the feature for selecting which quests are displayed on your Duty List.

As this feature involves not only the UI team, but the programmer in charge of events, I'm unable to give a specific time-frame for when this feature will return. However, it is included in the tasks for patch 2.2 and I will be sure to keep you updated.

[Parodine]

Summoner and Scholar are now counted as separate jobs when determining the speed at which the limit break gauge is filled.

This is hilarious to me. In what world did it make sense for them to count as the same job?! They're filling to two extremely different roles, womp. Well, glad it's fixed regardless.

[Hanemakikaze]

This is hilarious to me. In what world did it make sense for them to count as the same job?! They're filling to two extremely different roles, womp. Well, glad it's fixed regardless.

They are still both technically summoners(or arcanist if you want) though one is offensive the other is support, so it does make sense from a lore standpoint.