Eureka unplayable at times

[Chevronone]

Leaving aside our personal tastes regarding this content, with the amount of players they pack into one instance, how do the devs actually want us to play this mode when a majority of the time we can't see the monster, can't see our party members, cant see AoEs - on top of everyone rubber banding around you, NMs disappearing on the screen but still murdering you even though you can't see anything to dodge, your spells taking upwards to almost 10s to take effect on party members, rez leg and that's not even during NA prime time.

How could you do this to players; you must have known that your server infrastructure could not handle these loads...or was this not even stress tested during the 17 months you sat on this? I cant imagine what ps4 players must be experiencing...

[NovaLevossida]

After 2.0 Northern Thanalan FATEs, specialty FATES like Odin and Ixion spanning 2.0 to 4.0, S rank hunts, and Diadem, they clearly could not have expected players to zerg rush or even anticipate DoT / model display issues with so many years of relevant experience with the problem. Clearly.

[Gun-Cat]

After 2.0 Northern Thanalan FATEs, specialty FATES like Odin and Ixion spanning 2.0 to 4.0, S rank hunts, and Diadem, they clearly could not have expected players to zerg rush or even anticipate DoT / model display issues with so many years of relevant experience with the problem. Clearly.

I am farily certain their Eureka image was: Groups gather in grind parties and slowly level, giving people something to do till the next patch hits.

What they didn't anticipate is the NM train. Henche the game being absolutely not prepared for that.

[Tridus]

I am farily certain their Eureka image was: Groups gather in grind parties and slowly level, giving people something to do till the next patch hits.

What they didn't anticipate is the NM train. Henche the game being absolutely not prepared for that.

Then they're incompetent. It's that simple. NMs give overwhelmingly more return on time invested, and players can directly influence spawning them. If they don't know that players are good optimizers and will always optimize for return on time invested, then they haven't been paying attention to what players have done in the past at all.

Much like how the combat design encourages healer DPS, Eureka's design encourages the NM train. If they didn't intend that, then it's on them.

After 2.0 Northern Thanalan FATEs, specialty FATES like Odin and Ixion spanning 2.0 to 4.0, S rank hunts, and Diadem, they clearly could not have expected players to zerg rush or even anticipate DoT / model display issues with so many years of relevant experience with the problem. Clearly.

Quote of the day, right there. The issue STILL happens with Ixion to this day on my server. There is no possible way they can't know about it, and they designed content that encourages it to happen by making the most valuable thing to do clumping up on a single mob, along with putting more people in the instance than the server can handle when they group up.

I mean, who decided it was okay to release in this state with known problems like this?

[RiceisNice]

Then they're incompetent. It's that simple. NMs give overwhelmingly more return on time invested, and players can directly influence spawning them. If they don't know that players are good optimizers and will always optimize for return on time invested, then they haven't been paying attention to what players have done in the past at all.

Much like how the combat design encourages healer DPS, Eureka's design encourages the NM train. If they didn't intend that, then it's on them.


Quote of the day, right there. The issue STILL happens with Ixion to this day on my server. There is no possible way they can't know about it, and they designed content that encourages it to happen by making the most valuable thing to do clumping up on a single mob, along with putting more people in the instance than the server can handle when they group up.

I mean, who decided it was okay to release in this state with known problems like this?

Funny enough, when hunts were first released on 2.0, we had this exact same issue with culling mobs before unpartied players. They eventually implemented a fix on that, but that just makes it even more astounding that they let this slide again in a instanced content that packs so many players. That and the debuff limit (and enmity list) makes it utter hell for classes like MCH to generate heat or apply wildfire. They've designed content that does not take into mind the limitations they have in place (debuff limit specifically), or outright forgot the problems that similiar content has already caused (model culling)

[Tridus]

Funny enough, when hunts were first released on 2.0, we had this exact same issue with culling mobs before unpartied players. They eventually implemented a fix on that, but that just makes it even more astounding that they let this slide again in a instanced content that packs so many players. That and the debuff limit (and enmity list) makes it utter hell for classes like MCH to generate heat or apply wildfire. They've designed content that does not take into mind the limitations they have in place (debuff limit specifically), or outright forgot the problems that similiar content has already caused (model culling)

Yeah. It sucks as a healer because my party also vanishes and I can't do my job effectively, just resorting to the "cast AoE healing and pray to the server gods" method. It sucks as a class like MCH because it breaks how the class plays.

I mean, they should know what their own server limits are. They can see them in production today. Set the zone limit low enough that this can't happen and you solve a major problem by tweaking a configuration variable. For something that was so delayed, there's no excuse for this problem to exist.

[Alleo]

I am farily certain their Eureka image was: Groups gather in grind parties and slowly level, giving people something to do till the next patch hits.

What they didn't anticipate is the NM train. Henche the game being absolutely not prepared for that.

If they did not want it to be people killing all the NMs then why did they give them so much exp and loot and make it possible to spawn them by just killing a certain amount of monsters? They could have simply made the NM spawn at a certain time or give it way more different ways to spawn. So its kinda their own fault when they put so much behind it and do nothing to prevent such a zerg.

At the same time I kinda wonder if people would still even do it if it was so slow.

About topic: It was really annoying to be in an instance that was constantly lagging and DC symbols on everyone nearly all the time. Killing stuff was horrible and I even got a DC right when a NM died so I got nothing..Its utterly frustating on top of being boring. Not a good combination.

[Claviusnex]

If they did not want it to be people killing all the NMs then why did they give them so much exp and loot and make it possible to spawn them by just killing a certain amount of monsters? They could have simply made the NM spawn at a certain time or give it way more different ways to spawn. So its kinda their own fault when they put so much behind it and do nothing to prevent such a zerg.

Even if they changed the spawning technique players would still mass together to kill the NM as it is the most efficient way to play. Ixion and Odin are examples of this.

[Claviusnex]

I am farily certain their Eureka image was: Groups gather in grind parties and slowly level, giving people something to do till the next patch hits.

What they didn't anticipate is the NM train. Henche the game being absolutely not prepared for that.

There is no excuse for SE not anticipating the NM train as players have exhibited this type of behavior time and again. With limited and timed resources players are always bound to massively group to play.

[Gun-Cat]

There is no excuse for SE not anticipating the NM train as players have exhibited this type of behavior time and again. With limited and timed resources players are always bound to massively group to play.

If they were anticipating this I see no reason for the Eureka instance player limit being that high. The game takes a massive nosedive, no matter how good your hardware is if there are too many things happening on screen. The object culling and inability to read boss tells, something that is apperantly emphasised in Eureka as opposed to floor indicators, make this an absolutely horrid experience.

In other words: I doubt they have enough of an QA team to scale these things the same way they scale in the live environment. If you only have 24 people QA testing in Eureka you get a very different experience.