Sorry SE, but endgame won't work if you don't fix something.

[Gravehill]

What I mean is that lag in this game is so consistent, it basically functions the same as if the cast time is simply shorter. If WotL is 2.0s to cast, you might as well think of it as if it's just 1.4s. Therefore ultimately skill does determine whether you'll dodge it or not. If WoW needs to duplicate the exact difficulty of FF14, they'd just use a 1.4s casting spell, and if you can't dodge 2.0s in WotL, you still won't dodge 1.4 (without lag) in WoW.

That's great but it doesn't change the fact that the game feels insanely clunky and sluggish. It's the whole game, not just the cast bar. I noticed it 5 minutes in to the beta where I had to pick up items for quests

[xanj]

it would be nice if square would say anything about this instead of telling us to zoom out

[Knosis]

Heya, just a tip on those making videos displaying this issue: disable comments on the videos as I believe the video speaks louder when there are no distraction after they watch it when they read YouTube comments. I think we can all agree that YouTube comments do more harm than good.

[CheshirePuss]

read between the lines, they think we're just bad

Who knows, maybe you are? I mean if you're going to try hard enough to derive only that from any context given by SE on the situation, who am I to argue about your skill?


In all seriousness, SE's not so ignorant to not know there is an issue, given that there are even videos on Youtube and the like, PROVING said issues. Remember how player casted skills activate before it's charged? This same exact issue applies to the enemies, especially on more noticeable enemy casts from monsters like Titan. So there isn't just the lag being an issue, it's the mechanic itself that is making it over difficult to cooperate with.

[carlos777uk]

SE's silence basically says "we're aware of this but cannot solve the problem, either due to the amount of resources it would take or because we simply don't have a clue".

In business launches like this are called a MINIMUM VIABLE PRODUCT. You are aware of the shortcomings of your product but await feedback from your customers as to what they perceive as being most needed as additional features or fixes. Often this feedback is completely different from what the in-house team thought would be important.

Problem being, you have to follow it up with real action - and quickly. Designate the resources to achieving these goals or the product remains MINIMALLY VIABLE. Like now. I've just cancelled my subs and won't re-sub unless this is fixed.

[complexxL9]

bumpity bump

[Goreth]

Problem being, you have to follow it up with real action - and quickly. Designate the resources to achieving these goals or the product remains MINIMALLY VIABLE. Like now. I've just cancelled my subs and won't re-sub unless this is fixed.

They have a few more months to take action, but soon competition will start to get fierce in the MMO market. If they choose to do nothing... well I think the "make the game more like FFXI or 1.0" will suddenly become a lot more relevant.

[Randalthor]

SE's silence basically says "we're aware of this but cannot solve the problem, either due to the amount of resources it would take or because we simply don't have a clue".

In business launches like this are called a MINIMUM VIABLE PRODUCT. You are aware of the shortcomings of your product but await feedback from your customers as to what they perceive as being most needed as additional features or fixes. Often this feedback is completely different from what the in-house team thought would be important.

Problem being, you have to follow it up with real action - and quickly. Designate the resources to achieving these goals or the product remains MINIMALLY VIABLE. Like now. I've just cancelled my subs and won't re-sub unless this is fixed.

MVP, or Minimally Viable Product is when the product and engineering teams KNOW what their customer needs are at a minimum, either through customer studies, feedback, etc., in order to use a product that solves the most critical use cases. It's not a tool to validate whether what you launched is correct or not.

What SE did, or seems to have done, is build a product that THEY thought their customers wanted/needed, and built that functionality to rush a product out of the door. Some things are successful, some are not. That is not how you perform product management.

What I agree with you on is that there are things like this that should have been fixed in a fast follower build (usually 2-3 weeks after the initial launch). It just seems that SE doesn't think that this is a problem, or strongly believes it's "by design".

[Dashuto]

Its actually pretty worrying how they've responded to 15 page threads before fairly quick and this monster is at 150+ and another at 38 and we still don't have response.

Sounds like its something they can never fix. They're basically admitting it to us by not responding.

[Astarica]

What SE did, or seems to have done, is build a product that THEY thought their customers wanted/needed, and built that functionality to rush a product out of the door. Some things are successful, some are not. That is not how you perform product management.

I think there was an article by Ralph Koster just on this subject, where he basically says it doesn't matter what you think the customer wants, if the customer tells you that's not what they want you don't get to argue against them. While it's true a dev probably does know better than an user on a general level, if enough users feel strongly about something to dev they're wrong, then the dev is indeed wrong. If all your users want the wrong stuff, then you better deliver the wrong stuff.