| Author |
Thread Statistics | Show CCP posts - 5 post(s) |
Aralis
Imperial Dreams
Curatores Veritatis Alliance
   |
Posted - 2010.02.04 15:50:00 -
[1]
Edited by: Aralis on 04/02/2010 15:51:24
Ah so our disaster there didn't just happen. CCP engineers were busily working to make it happen. That's nice to know.
I know it's against CCPs policy to admit mistakes or misjudgements but isn't it about time to realise that Dominion is ruining the game. It took everything that was wrong with Eve and added more of it.
It would be easy, more fun, and far more sensible to design a system that didn't encourage the biggest fleets possible.
You are not "aware of the problem" - the main problem is lousy game design. The fact that your servers physically can't cope is detail. As others have pointed out with this game design if the servers were better there would just be more people in there to break them.
|
Aralis
Imperial Dreams
Curatores Veritatis Alliance
|
Posted - 2010.02.08 12:13:00 -
[2]
 Originally by: CCP Atlas
Thank you all for your comments. I'll just make a brief comment about the concerns people have about the node being kept alive for the 1600 person fight that is mentioned in the blog.
We are deploying a fix to Tranquility this week (probably tomorrow) which identical to the methods used that fateful night in keeping the node up.
The problem was that under great strain nodes were unable to contact the database to 'heartbeat' which is a way for them to tell the cluster that they are alive and kicking. A bug was introduced in the Dominion expansion where database calls were not scheduled 'fairly' so low level management functionality such as the heartbeat would not have enough precedence over game functionality such as shooting a gun.
This was jury-rigged live on Jan 28th and is making its way to a permanent fix this week. The fix that is being deployed is identical to the live-fix that was made on Jan 28th.
So, despite 'making people faint' comments this change was done in an extremely controlled manner and was not a case of 'keeping the node alive longer than it should have been'. If the node would have been allowed to die the results would have been extremely bad for everyone as the solarsystem would not have been properly persisted, and it would have come up on a different node, where it would immediately die again because of the population count and that would continue to cascade as long as there were more than ~1000 people fighting there leading to horrible gameplay for those involved and a possible destabilization of certain parts of the cluster.
The cluster cannot gracefully handle a 1600 person fleet fight right now but bouncing between dying nodes every 2 minutes with the solar system in an indeterminate state is not really any kind of a solution.
We will be deploying fixes this week and the next and are continuing to closely monitor fights as they occur. Please bear with us a little while longer.
Nice. So you simultaneously did and didn't keep the node alive. Please less quantum physics in yuor answers.
No you are totally mistaken. An utter crash would have been better than one that lets one side play and one side not.
|
Aralis
Imperial Dreams
Curatores Veritatis Alliance
|
Posted - 2010.02.13 15:26:00 -
[3]
Originally by: Future Mutant
Or maybe we can just stop being complete morons about it. Case and point- whose idea was a 1500+ fleet fight again?
CCPs. Pay attention.
|
Aralis
Imperial Dreams
Curatores Veritatis Alliance
|
Posted - 2010.03.05 17:28:00 -
[4]
I look forward to the day you realise you totally screwed up the game with Dominion. In the meantime some traditional CCP denials telling us how much you've improved gameplay and increased the number of people in 0.0 should be good for a laugh.
|
| |
|