Rofl, Darkhold is soooo easy. Ogre is rediculously easy. It's nothing but positioning.
Rofl, Darkhold is soooo easy. Ogre is rediculously easy. It's nothing but positioning.
Oh man, not much more frustratingly retarded than an AF-scrounging Darkhold pickup that has zero chance to kill Deepvoid Slave despite telling them exactly what to do.
How do you deal with coincounters hate reset move?
Looking through my old WoW vids and remembered this gem... I really hope the UI/servers in 2.0 are smooth enough to allow me to do shit like this on DRG w/ Elusive Jump. Skip to 4:52 unless you want to watch.
I was such a bawce with Disengage.
I still don't understand why I have to stop and squat for everything. Even minor self-buffs.
Should only really need to stop moving to cast spells or use WS.
I'm still not sure why they took away movement while casting.
It was very convenient and made playing mage jobs a lot smoother.
I've gotten people killed because of lag/interrupt trying to cure them, not a good feeling when the UI is still slow despite being improved from previous crappiness.
Agreed. I'd rather take a movement penalty than this stuff. Noticed the lag gets fairly annoying to for me when I try to sleep on BLM.
I'd like to see a player's poll on that.
He said the reason in that super long post about the issue a while back. Main reason for getting it in as soon as possible is conditioning really since 2.0's combat system was going to balanced around the no cast while moving. He wanted to get the stoppage system in as soon as it was feasible so people started getting used to the idea they would be doing it in 2.0 and the transition to 2.0 would become that much smoother. Personally I do agree he should have waited till 2.0 to implement it but its here now and unless there is enough complaining about it, I doubt they are going to remove it with 2.0 coming in 6-7 months from now.
Unless 2.0 battles are going to take place in the same area continuously I'm pretty sure I'm gonna dislike it just as much then as I am now.
Not being able to move while casting will always be way less convenient, I don't care how they "planned" it for 2.0, it's still more cumbersome and less enjoyable.
It makes sense that you can't cast while running... but I understand people's frustration with the lag. I noticed while playing that I would be standing still and getting the "You cannot do that" message still - probably because the server sees me still in motion.
Yeah, that's why they added that running/walking indicator. I'm pretty sure it shows you what the server actually still sees you as. If it's off, you should be good to cast*.
(*at least this method has worked consistently for me when I'm lagging a bit.)
I know its gonna sound like i'm nitpicking but I hope to hell SE doesn't go "hard/heroic mode" route, that two/three difficulty shit is so fucking fail in WoW and other games. If you suck at the game to the point where content needs to be faceroll on "easy mode" then get better at the game. The thing is it takes such a long time to balance out multiple difficulties, I rather 1 difficulty so the rest of the content doesn't suffer because they have to disable mechanic's or add mechanics depending on the difficulty level.
I am hoping that raiding or endgame means challenge(rewarding) and not faceroll(lowdrop rate content). I miss the days where endgame was for elite players who wanted to be the best of the best(Burning Crusade) type of endgame. They can add content for everyone but I sure hope to hell they don't go the route WoW did.
The main reason for the "no casts while running" is PvP. In 2.0 they're adding some of that content and Yoshida said that mages being able to cast any spell while running would simply be too much. He also said that they will add some exceptions to this rule in 2.0 and honestly there are some spells you can cast while running away already.
That's a really terrible reason then. The majority of people don't certainly play a FF MMORPG with pvp online, so they're essentially throwing a major nerf for something that was never asked if not by a very small number of players.
Was there a poll that asked "What do you like more? Movement while casting and no pvp or No movement while casting and pvp"? I think the players' answer should have been obvious.
Anyway I think the new job system is awful. It's like an half-assed class system put on top of another half-assed class system.
The original one was great on paper, it just needed some tweakening.
Not being able to move while casting would be fine if they would just incorporate face target into the actual casting mechanic. Several times I've stopped, hit my macro and the shit still doesn't cast. I don't understand why they couldn't have made casting a spell automatically use /facetarget.
Just because they say something, doesn't mean it true. Most times I'm willing to look the other way, but I can't in this instance. SE has never shown that they're able to get over the movement hump, and they haven't come any closer to proving anyone wrong over the last decade. They've went from not telling us anything, to telling us it was a design policy, to telling us that they'd like to change it, but it would create imbalances.
While i don't agree on the term you used, i still feel the whole structure feels like a redundant, terrible mess for anyone less than a true RPG fan.Anyway I think the new job system is awful.
Personally, I kinda like it but that's not my point.
"Naive" players will have a really hard time understanding why they have to roll a Lancer to be the Dragoon they want, for example.
Even the whole "bad in solo/good in party" concept, while great from a more hardcore point of view, feels like an unfamiliar concept for players that are not so much into MMORPGs. Most will probably stick to either the class, or the job, fulltime.