of course a big YES...if we are going to game with perfect performans without any problems yess mi can even wait one month...

Personally... sure I would. But I also suspect it would kill the game with a loss in players. If it picked up again it could be extremely profitable IF they fixed a few of the problems. But there's that risk vs. reward situation which they've backed themselves into on this topic...
Ideally they never should have put themselves in this situation in the first place, but I guess every game has bugs... this one just has a swarm of them and a rookie MMO development company to fix them all with.

For a couple weeks? Yeah, I'd be fine with that. A month or more is pushing it.
Again, assuming hardware is one of the causes.

Doncellius wrote: »

@zyk
Taking down the servers would allow ZOS to solely work on Cyrodill Performance aka netcode (like a 14-day maintenance) and fix it.

No, it would not. My software development team uses a very similar setup so I know how we develop, debug, and deploy our program to a dedicated server. For both computer and personnel reasons it would not help them to fix any issues to take down the server. First consider the computer:
- There is no advantage to working on the actual server over working on a duplicate machine. Finding and fixing the issues is still exactly the same. So down time while they work on it is just wasted time. The only time it makes sense to have the server down is during a patch.
- Large releases of fixes have a very high rate of failure. It's why after a DLC we always get a few followup patches to stabilize things. In part that is because the problems they are trying to solve are complex and hard to find, otherwise they would have been caught before the first release. It's better for fixes to trickle in a few at a time.
Second, consider the personnel issues:
- The team includes a lot of people who are not programmers. Artists, writers, people who keep up with the lore, those who develop the audio and hire voice actors. Those who work motion capture. None of those people would be any help in debugging netcode. And without programmers to work with them in implementing their ideas, those people would sit idle or at least build a backlog of material the programmers would then need to implement.
- Speaking of programmers, most of them probably know little or nothing about that particular part of the code. It's a technical and specialized subject area that requires a deep knowledge of network communications, not just how to code.
- There is a limit to how many people can be useful in solving the problem. It's like having a lot of people try to make a pot of soup, do a load of laundry, or make a cup of tea. Not only are the extra people not helpful, they can actually hinder progress or even ruin the product. Imagine if 12 different people all tired to salt the soup, add soap to the laundry, or sweeten the tea.

What they really need is a small team of experts in this particular subject to work on the communications code on their development server (not, PTS, another server that we never see), then when the get it right, try it on the PTS.

A couple of days; sure no problem.

Couple of weeks? No can do - this is something they have to fix as they go.

*If they pause my ESO+ and give me every monster set - hell yes take it down for as long you want *

There's no need to shut down servers for so long to fix those things.

Nope because I don't think the problem is the hardware, it's the code. The suits need to pay for the employees to rewrite whatever spaghetti is causing this and they apparently aren't willing to cut into their profit margin to do so.

If they took the game off line completely, some people will move on to other less wonderful things. Like housework, yard work, and life in general. But seriously, they can do everything they need to without taking it down for more than a day as they have in the past. That's the purpose of the sandbox and PTS. Get it all worked out, then take a day to transfer to live server. They do work on bugs and fixes and so on at the same time other people are working on new content.

While I do get frustrated from time to time with the long load screens, especially once in a while at start up when it times out and logs me out for inactivity, but I have confidence that it will eventually get fixed.

If said server upgrades would fix the lag in Cyrodiil then yes. 100% yes. I could careless about my sub being useless for two weeks if I could come back and play the game the way it was meant to be played.

Honestly haven't seen lag in Cyrodiil this bad since 1.3-1.4 days. Even in non pop locked campaigns running in the middle of no where there is lag. Not to mention lag in vMA, a solo instance. It's horrible.

A couple of weeks?!

I get antsy if I can't play for a couple of days!

I wouldn't mind the game going down for a few days - prescheduled with lots of notice, so I could arrange to go and visit friends in another city. But a few weeks and I'd have withdrawal symptoms and be missing all my friends online.

Valkas wrote: »

Title.

*Assuming that hardware WOULD help the problem, along with halting DB for however long it takes to fix current issues*

I would be all for it. I love Elder Scrolls, and am super excited they've finally rolled out a multi-player version of it, which we've been screaming for since the days of lugging Xbox's and non-flat-screen TV's to one another's living rooms to play together and emulate a multi-player experience.

Why do they need to do that? If they have to do that they might as well call it quits and shoot for ESO 2.0.