@Forestd16b14_ESO am not sure but isn't from software a Japanese developer.If so I can see why they did it They usually have more proud in their work and if something broken would rather pull it off the server and fix it than leave it live and bring more bugs.

Smasherx74 wrote: »

Fix the anti-cheat feature that apparently lags the game to ***, no other reasons why the games performance would degrade over time when playing (without any external issues).

Fix mementos for characters who cannot use them

Fix the loading issues and lag on consoles

Make PVP playable.

The purely database-examining anti-cheat code does not lag anything and in fact the game still has approximately the same amount of performance issues as it always has, although sometimes in the past it's spiked higher. It's certainly not highest now that it ever has been, nor are the load screen issues the worst they've ever been. Nor did the 666 deer in Cyrodiil make any difference when removed. The fact is that the performance issues are totally unacceptable and have received very little attention and resources is the real issue. Granted, for all we know it may have taken up 90% of the developer's attention these last 2+ years but all that means is that (1) they skimped on their hardware which is clearly a fact and (2) they haven't hired enough people to run an MMO, which is something that's been clear from the very beginning. In fact, there's even a gaming site review of Bethesda praising them for always having too few people on staff so they can enjoy the bizarre and constant bugs. They weren't joking but I think only they agree with that sentiment. It's an Agile programming culture arrogance and all it means is that bean counters outsmarted coders with an idiotic idea. No surprise there.

Forestd16b14_ESO wrote: »

Jaronking wrote: »

@Forestd16b14_ESO am not sure but isn't from software a Japanese developer.If so I can see why they did it They usually have more proud in their work and if something broken would rather pull it off the server and fix it than leave it live and bring more bugs.

Japanese yes but Japanese American or even Canadian a Studio and Dev team should have pride in their work and admit when mistakes happen and own up to them not dis-miss everything and say everything is fine.

I agree with you Dev should take pride in their work but we don't have that here it will seem at times.They will just throw anything out and try to fix it later and than they just forget to fix it.

starkerealm wrote: »

Forestd16b14_ESO wrote: »

Jaronking wrote: »

@Forestd16b14_ESO am not sure but isn't from software a Japanese developer.If so I can see why they did it They usually have more proud in their work and if something broken would rather pull it off the server and fix it than leave it live and bring more bugs.

Japanese yes but Japanese American or even Canadian a Studio and Dev team should have pride in their work and admit when mistakes happen and own up to them not dis-miss everything and say everything is fine.

Someone should let Bioware know that. They're still trying to insist that, "no, really, the Starchild was a good plot point, and you just don't understand our genius."

Also, I've got to say, I honestly love Miyazaki's comment about poise. What does it do in Dark Souls 3? Nobody knows. It's starting to look like even Fromsoft doesn't know. But they're really sorry about it. Not, you know, sorry enough to tell us what it does, or to fix it. Just that they're sorry.

ZOS has made some errors. They've copped to some, and worked on fixing them. Sometimes the answer really is "working as intended." Sometimes the real answer is, "no ETA," not because they're stringing us along, but because it's not a simple problem. I know that's not what you want to hear, but there it is.

Copped with some but some others they needs to address such as supposed perma-banend players returning to the game or the players who are still in the game that are cheating and gap closing into keeps.

Gap closing into keeps is a easy fix like we already have it in the game we get a passive in IC that prevents fire chains from pulling us or the DK to the safe area and end of the day fire chains is a gap closer like any other gap closer. ZoS already has the solution to the problem. Why say "no ETA" for a fix when it's already in the game ?

Jaronking wrote: »

Forestd16b14_ESO wrote: »

starkerealm wrote: »

Forestd16b14_ESO wrote: »

Jaronking wrote: »

@Forestd16b14_ESO am not sure but isn't from software a Japanese developer.If so I can see why they did it They usually have more proud in their work and if something broken would rather pull it off the server and fix it than leave it live and bring more bugs.

Japanese yes but Japanese American or even Canadian a Studio and Dev team should have pride in their work and admit when mistakes happen and own up to them not dis-miss everything and say everything is fine.

Someone should let Bioware know that. They're still trying to insist that, "no, really, the Starchild was a good plot point, and you just don't understand our genius."

Also, I've got to say, I honestly love Miyazaki's comment about poise. What does it do in Dark Souls 3? Nobody knows. It's starting to look like even Fromsoft doesn't know. But they're really sorry about it. Not, you know, sorry enough to tell us what it does, or to fix it. Just that they're sorry.

ZOS has made some errors. They've copped to some, and worked on fixing them. Sometimes the answer really is "working as intended." Sometimes the real answer is, "no ETA," not because they're stringing us along, but because it's not a simple problem. I know that's not what you want to hear, but there it is.

Copped with some but some others they needs to address such as supposed perma-banend players returning to the game or the players who are still in the game that are cheating and gap closing into keeps.

Gap closing into keeps is a easy fix like we already have it in the game we get a passive in IC that prevents fire chains from pulling us or the DK to the safe area and end of the day fire chains is a gap closer like any other gap closer. ZoS already has the solution to the problem. Why say "no ETA" for a fix when it's already in the game ?

I just thought of something people have been saying this but it won't work you know why because if they did this it could case that a player can't gap close while in a keep or with defenders and assaulters on the walls fight gap closer to not work if they add that it could completely break keep assaults and gap closers while fighting in a keep.

Which is why it is tweeked to only applied when you are above a player by 5 meters or how ever tall a keep wall is that way when a player is inside a keep or on a wall they can still gap close. Not saying copy and paste but for ZoS to finally start working on it cause again they already have solution that is already in the game that they can easily modify to hopefully end gap closing into keep and make gap closer work again cause it's ridiculous that you can gap close on a small foot hill yet you can into a keep.