This tells me the game is failing the stress test.The stress test is working as planned.
Is the game failing? Too early to tell. It depends if GW is able to fix the issue or at least reach an acceptable level or if I can't do this in time for EE.
The only reason I see why he'd say it's failing... is because I would expect many more people to come into the game for EE. Obviously, if they continue to add more server-room then yeah. But there shouldn't be any server issues ideally when EE starts. Because if there are, then it will only get worse.
Mind you, that it is almost certain that when EE starts, there will be new server issues, or the same ones. But at this point I would hope that they could get the alpha servers working cuz I bet way more people are gonna be on when EE starts.
Goblinworks Executive Founder
|
| 1 person marked this as a favorite. |
Yep I think way more might be a bit of a stretch but once we have persistent characters people will want to start developing them. Personally I don't THINK I have lost any XP with rollbacks but I can understand the concern when its a persistent character affected.
What that really means is we need a secondary catch. A character who's been Training for X amount of time (should be logged) should have Y amount of XP. This can be checked against the costs of all Feats purchased. If there is a discrepancy server side, recompile the total shown. To simplify storage requirements, store the Start and Stop dates of Training, and its easy enough to back check.
Its a change in methodology, depending on how GW has set up the programming on the back end. Instead of just adding 1 XP to all Training accounts every time unit, you store start and stop times as well to be a backup incase something like, THE ROOF OF THE DATA CENTER COLLAPSES FROM SNOW and shuts everyting down for a while. (It's been known to happend :P.)
Realistically the subscription to PFO is covering a months worth of XP gain. If your character(s) cumaltively have less than that GW would not have fulfill that obligation.
=====
It would reassure the nervice to know that such a real world date/time based backstop was in place, so they know that the XP credit they're paying for is protected.
Goblin Squad Member
|
The more annoying one is when after a teleport your character cannot log in at all and just sits at the character loading prompt at the login screen until the next server reset.
BTW - I am not sure its all to do with immediate server load. The Aussie evenings are just before reset and those times are really bad for teleports and desynch even though it is a quiet time in terms of players online. Seems a lot like a resource or memory leak to me.
|
Goblin Squad Member
|
I agree, it doesn't seem to be just number of players. This morning (german time, so about 3-5am EST), it was extremely bad for me, I could barely walk for half a hex without falling through the ground again. I would expect this to have been a fairly quiet time, there was certainly not much activity in general chat, including login/logouts, nor did I meet anyone in any of the hexes i travelled in (mostly south of Kindleburn).
Still, I experienced an extreme amount of issues. And not just in one hex, but in several. The usual logout-wait-relog fixed it everytime, but still, so many issues in a quiet time indicates to me a different cause (in part, at least).
|
Goblin Squad Member
|
I agree, it doesn't seem to be just number of players. This morning (german time, so about 3-5am EST), it was extremely bad for me, I could barely walk for half a hex without falling through the ground again. I would expect this to have been a fairly quiet time, there was certainly not much activity in general chat, including login/logouts, nor did I meet anyone in any of the hexes i travelled in (mostly south of Kindleburn).
Still, I experienced an extreme amount of issues. And not just in one hex, but in several. The usual logout-wait-relog fixed it everytime, but still, so many issues in a quiet time indicates to me a different cause (in part, at least).
Yeah it really does seem like the problems may be triggered by high server load but then continue until reset even if the server load seemingly drops.
