Wtf does haste do in this?

[Epicmask]

Im surprised no ones mentioned it, but haste doesnt seem to do anything.

In the other versions, haste was an amazing buff, Way more damage. Anytime ive used haste in this version though the damage and number of hits doesn't change at all.

I thought thats okay, the made it like how haste works in the other games and will make the hasted dude go faster in the turn order.

Nope. Doesnt change at all. Then i thought to myself. How the hell is the turn order even decided? Agility doesnt matter obviously, Since usually my viking goes first. So maybe draw attacks just always goes first? Nope, not always. Bard goes first half the time, then after that my dragoon and geomancer randomly switch as well. Agility seems to have nothing to do with turn order.. so...the ♥♥♥♥♥? It seems completely random. No mater whos hasted they still never go faster than they normally do in the turn order. Same with the enemies, sometimes the boss goes first, sometimes last. So... how does it work? Anyone know?

[SC_Nikki]

It might be my imagination, but the effect seems to be delayed. As in, a few turns later, I noticed my number of hits gradually increasing.

[ztdk]

Just tested it on my Dark Knight as a very quick test. Did five attacks unhasted against death needles and got 21hit, 21hit, 24hit, and 22hit and 20hit. Then did another four with haste and got 25hit, 26hit, 24hit, 30hit, and 21hit.

I'd guess I just missed a couple on that last attack but who knows. I'm pretty sure it increases how many times you hit.

[SC_Nikki]

The effect definitely is not as dramatic as in FF1 and 2. It only gives you, like, a few more hits.

[Liam]

Out of curiosity, do buffs stack in this game, or do they only have one level? I'm not far enough to test myself.

[Epicmask]

Even tough i notice them doing a few more hits now and then, the damage still is always around the same. Especially at early levels, In the nes version id always use the item that gives haste to my fighter when fighting Salamander at the fire crystal since it was a huge difference. In this he did like 20 more damage. Barely noticeable at all. Maybe it still does a tiny buff, but i think using the turn to cast it instead of attacking waste more damage then the buff gives over the entire fight.

As for buffs stacking, I dont think so with protect or haste. I dunno bout the bard ones, since they always miss after the first time. Id like to now for sure though. An indication of how long they last would be nice too, but as far as i can tell nothing shows if your effected by a song or not.

[spoonygundam]

Buffs no longer stack, and the effect now wears off after a few turns.

I didn't really notice much of a difference with Haste (Or Protect) either. A lot of the time I would end up doing more damage after it wore off, just because the effect isn't even large enough to be clearly distinguishable from normal damage variance.

Is this how the spells were in the 3D remake?

[eyrie0]

I'm pretty sure Haste actually increases your chance to perform your action prior to the enemy in this game. I used it at the end of the game on my Devout a bunch and it definitely seemed like it made them able to cast Curaja/Arise/whatever before the enemy's turn much more frequently than otherwise.

[Epicmask]

Originally posted by eyrie0:

I'm pretty sure Haste actually increases your chance to perform your action prior to the enemy in this game. I used it at the end of the game on my Devout a bunch and it definitely seemed like it made them able to cast Curaja/Arise/whatever before the enemy's turn much more frequently than otherwise.

It might boost the chance of it a little, but not by much. I tested tons of things but turn order was different every single time. When my viking was taunting and my bard singing, They would switch off going first and second before anyone else even when my other guys had haste.

Im pretty sure sing and draw attack have a priority bonus, which is why the always go first and second when using those, but not when i have them use and item or attack. Healing i think has less priority then buffs, but more than attack actions. But even though thats usually the case it still has some randomness to it.

When using healing spells i usually want them to go early in the order, but tons of times ive needed them to go early so people wont die and the enemy randomly goes before the casting or potion goes off when they werent before, regardless of class or haste.

Its different so often even in the same fight that there is obviously some randomness with turn order. Maybe haste slightly increases the chance of them going early, but it must be such a small notice that i dont notice an difference.

[Oondiv]

Haste yields a number of hits and a boost to attack power based on the caster's Spirit stat. It's weird to think, but any spells that yield buffs in this game actually have a scaling effect based on the caster's own stats.

[Alanthier]

Originally posted by SC_Nikki:

The effect definitely is not as dramatic as in FF1 and 2. It only gives you, like, a few more hits.

Haste in all the other ones(1/2/4/5/6) merely allowed you to take your turn sooner. Because this game is actually FF VI(when the data for 3 and 6 got sent to the west it was sent in the wrong order, hence the reason you can do stuff in 3 that couldn't be done in 4 or 6, but could be done in 5,) the mechanics changed for that spell, allowing for an increase in the # of hits you deal with an attack, as opposed to getting more turns in before the enemy.

[Epicmask]

Uh.. no. Until 4 haste just boosted number of attacks. not turn order. Its very obvious in the nes versions that haste buffed hits and damage. Especially in japanese nes 3, where it was almost double damage when hasted sometime, but in nes 1 it was the only buff for attack damage that even did anything, since the others were bugged.

[spoonygundam]

Originally posted by Epicmask:

Uh.. no. Until 4 haste just boosted number of attacks. not turn order. Its very obvious in the nes versions that haste buffed hits and damage. Especially in japanese nes 3, where it was almost double damage when hasted sometime, but in nes 1 it was the only buff for attack damage that even did anything, since the others were bugged.

You have it backwards for FFI. Haste always worked and was great, Temper/Saber were the ones that were bugged.

The idea that Square sent the data for the games in the wrong order is completely wrong though. There's even an English prototype of NES FFII floating around, Square just chose not to release it or 3 because the SNES was already out in America by that point.

[Shyao]

Originally posted by spoonygundam:

Originally posted by Epicmask:

Uh.. no. Until 4 haste just boosted number of attacks. not turn order. Its very obvious in the nes versions that haste buffed hits and damage. Especially in japanese nes 3, where it was almost double damage when hasted sometime, but in nes 1 it was the only buff for attack damage that even did anything, since the others were bugged.

You have it backwards for FFI. Haste always worked and was great, Temper/Saber were the ones that were bugged.

The idea that Square sent the data for the games in the wrong order is completely wrong though. There's even an English prototype of NES FFII floating around, Square just chose not to release it or 3 because the SNES was already out in America by that point.

Actually, that was Nintendo's doing. According to a bunch of rumors, Nintendo didn't allow Square to put out FF2 or FF3 because they didn't want to release major titles for the NES while it was phasing out, instead opting to ask Square to skip to Final Fantasy 4, since it was in development at the time for the Super Famicom. That's why we never got FF2 or FF3, because of the platform holder.

[Epicmask]

I dont have it backwards. I said that in 1 haste was the only buff that effected attack that worked. You may have read what i said wrong.

[spoonygundam]

Originally posted by Epicmask:

I dont have it backwards. I said that in 1 haste was the only buff that effected attack that worked. You may have read what i said wrong.

I did, my bad.