responding to what you said earlier, if UI changed faster, on the contrary, mana ticks should happen earlier, not later. So how do you fundament what you're saying that all the switches are happening earlier?
or if anything, we should still have enough time to get our mana tick through, cause UI timer would start counting earlier, and at the same time AF would stop it earlier as well, if both spells have the same cast time. Then the phase difference should not affect the time gap to get our mana tick.
Last edited by NeruMew; 12-19-2013 at 12:27 AM.
I am not 100% that Blizzard III changes to UI faster, but I am 100% sure that Fire III changes to AF3 before the cast even finishes.
Easily testable and I even spotted with yoshi's titan video. I paused the youtube and got him midcast with FIRE III and no buff even though his UI3 buff had 8 seconds remaining when he started the cast.
This is the case on live, and you can confirm it yourself. You will lose UI3 during the cast of Fire III and get AF3 afterwards.
This means you can't get the double reduced cast time and you can't get mana back after casting flare, hence no more double flare.
The consequence of this is that our UI3 phase is now shorter. Before our UI3 phase lasted even after the Fire III cast allowing us to be fully topped off.
Now it ends before the Fire III even finishes, which is a significant reduction.
Before, when you were unlucky with ticks, you'd still at least get a tick after Fire III.
Now that's not possible, so if you're unlucky with ticks you will not be at full mana.
However, it's clear they never really meant for us to get anything from UI3 after casting Fire III.
The mana ticks were not synced and that is false information lead by someone who casually watched the live letter and said that.
Then it got spread even though those of us who watched the youtube video and analysed it carefully conclusively disproved it.
Now the patch is live and anyone can test it, but people are still talking about syncing when the ticks are, in fact, as fast as they always were.
Our UI phase is just shorter because the transition is quicker.
I am 100% sure your own test could not have conclusively proven that UI3 ticks are longer.
I am also sure you did not really look at your UI/AF buff when casting fire 3 to transition to AF3.
EDIT:
The fact that you can get ticks almost instantly after switching to UI3 disproves any notion that the mana ticks have changed (where people mostly say it takes 3 seconds for every tick).
Also, the ticks have always been on server time.
Go back to any of the Black Mage threads and this has been said repeatedly. It always ticks every Eorzea minute.
People have been trying to figure out if they could use that to their advantage since launch.
It ticks likes that before 2.1 and it ticks like that after.
This is how it's conclusively proven that mana ticks were unchanged because we already have a timer for them.
Coupled with a change to the AF transition that we haven't fully calculated yet, there's no reason to believe it has anything to do with mana ticks.
Last edited by Allyrion; 12-19-2013 at 01:03 AM.
I think a lot of BLMs don't understand what "syncing with the server timer" means.
I get the impression a lot of people think being on the server time means things happen every three seconds.
Well it does mean that, but it means much more than that.
Every dot in this game, every UI mana and healing regen buff...they all tick at exactly the same time.
In ET(Eorzea Time) 1 minute = 3 seconds. All those things tick according to ET.
This means the SMN who is fate farming in Costa has his dots ticking the exact same time as the one doing Coil.
It's weird, but that's how it is.
BLMs don't deal with dots much, so a good few can ignore this completely.
BLMs were always synced with the server and this does not mean that it takes a full 3 seconds after you change to UI3 to get a tick.
It means every Eorzea minute you get a tick, that's very different.
This can be seen when you would transpose for example, sometimes the mana tick would take split a second, or another times would take up to those 3 full seconds.I think a lot of BLMs don't understand what "syncing with the server timer" means.
I get the impression a lot of people think being on the server time means things happen every three seconds.
Well it does mean that, but it means much more than that.
Every dot in this game, every UI mana and healing regen buff...they all tick at exactly the same time.
In ET(Eorzea Time) 1 minute = 3 seconds. All those things tick according to ET.
This means the SMN who is fate farming in Costa has his dots ticking the exact same time as the one doing Coil.
It's weird, but that's how it is.
BLMs don't deal with dots much, so a good few can ignore this completely.
BLMs were always synced with the server and this does not mean that it takes a full 3 seconds after you change to UI3 to get a tick.
It means every Eorzea minute you get a tick, that's very different.
Either way this system is bad, I can see thunder duration getting derpy, sometimes suppose it says duration left 3.. switches back to two, and almost one secnod later, or well about 3/4 to say a figurative number, it goes back up to 3. (this is the effect of your client desyncig, and syncing back with the server afterwards)
As you said, maybe we always were, difference is that before, we had enough spare time to make sure those ticks ALWAYS happened, now it's more of a roulette, unless you're either super obsessed and able to sync an inner clock with that, or well, you're just that good that yo can do it and time your spells perfectly according to that. usually all this timing and syncing is something that gets build up internally (inside of each player, just biological stuff).
I still don't like it, and wanna complain about it. Cause it was much better the way it was before, and no, not because of the numbers, but because of that 'feel' you get when playing it. I love being able to just cast without split second wait time (unless ofc, dodging mechanics). Feels fluid enough.
It's not what i meant
I know full well that tiks are synched with server. I didn't get why ppl are talking about patch 2.1 change the "synch" of ticks when the real effect is shorter UI
Now i know it come out from an error during live letter
It doesn't change the fact that this is in fact a half assed fix, that ends up breaking other things along the way. And you should see it yourself that the way you describe things just ask for problems.
I haven't done extensive testing, I can just tell you from playing that ticks seem completely unreliable. doing this change to AF3 and not UI3 would just be stupid. (well meaning, diong this for AF stacks and not UI stacks).
What if I cancel the cast? well, in that case I guess we are all relying on the broken fact that I can move out with 60/70% my cast complete and still get the cast off, and watch my cast bar complete even as I am running.
So, adding more broken mechanics into already broken ones. Sounds about the right way to do things, doesn't it?
Added: My question is, now that we are at it, why don't get get our firestarter buff when we actually cast our spell, or wait! about 80%ish of our cast done, that way, we would be able to que it up when we should... or well, keep it broken an add a stacking capability to two, fixing this issue where we keep losing firestarter buffs because they get renewed on the next cast.
On a side note, I am not complaining about our DPS, while others got buffed and we may have gotten a slight nerf, we are still fine. But seriously, broken much?
Last edited by NeruMew; 12-19-2013 at 12:51 AM.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.