EVE General Discussion

Hey guys,

I've been through this thread and gathered a few questions, which were then forwarded on to everyone involved. What can be answered will be outlined briefly and directly in this post.

Firstly, there were a lot of questions about our reboot and node remapping mechanics in terms of aggression/log off timer persistence. Right now, there is no plan to change how this works. Had everything gone to plan this would have not been a factor, which means the key priority here is to identify the root cause of what happened and either enact change or put new systems in place to prevent a re-occurrence.

On Tuesday, we held a multi-disciplined postmortem of the chain of events that led up to the mass disconnect, and as a direct result we are making changes to our internal policies and our tools to ensure that this does not happen again. However, these changes do not include alterations to game mechanics that would lead to ships remaining in space, or changes that would lead to a solar system resuming the exact state it was after such an event.

In terms of addressing the costs associated with dedicating more computing power to meet the requirements of large fleet fights, we are always looking at avenues to improve server performance. However, in the same respect we recognize that as soon as performance is improved, our players will of course test the new limit and continue to push against it. This is a continuous battle for us, and something we remain heavily committed to.

There were also questions raised regarding how we move systems from one node to another, in terms of why persistence occurs for drones and wrecks, but not for ships. This is a simple matter of players being governed by log off timers that cause their removal from space. Wrecks and drones do not have a logged in player tied to them.

Finally, there were questions regarding Internal Affairs involvement in investigating what happened. Since the issue was immediately spotted, investigated and confirmed as a mistake, this negates the need for any IA investigation at this point.

This is all that can be said right now, so I hope this answers the bulk of the questions.

Hey guys,

I've been through this thread and gathered a few questions, which were then forwarded on to everyone involved. What can be answered will be outlined briefly and directly in this post.

Firstly, there were a lot of questions about our reboot and node remapping mechanics in terms of aggression/log off timer persistence. Right now, there is no plan to change how this works. Had everything gone to plan this would have not been a factor, which means the key priority here is to identify the root cause of what happened and either enact change or put new systems in place to prevent a re-occurrence.

On Tuesday, we held a multi-disciplined postmortem of the chain of events that led up to the mass disconnect, and as a direct result we are making changes to our internal policies and our tools to ensure that this does not happen again. However, these changes do not include alterations to game mechanics that would lead to ships remaining in space, or changes that would lead to a solar system resuming the exact state it was after such an event.

In terms of addressing the costs associated with dedicating more computing power to meet the requirements of large fleet fights, we are always looking at avenues to improve server performance. However, in the same respect we recognize that as soon as performance is improved, our players will of course test the new limit and continue to push against it. This is a continuous battle for us, and something we remain heavily committed to.

There were also questions raised regarding how we move systems from one node to another, in terms of why persistence occurs for drones and wrecks, but not for ships. This is a simple matter of players being governed by log off timers that cause their removal from space. Wrecks and drones do not have a logged in player tied to them.

Finally, there were questions regarding Internal Affairs involvement in investigating what happened. Since the issue was immediately spotted, investigated and confirmed as a mistake, this negates the need for any IA investigation at this point.

This is all that can be said right now, so I hope this answers the bulk of the questions.

Keep it civil and on topic, and cut the bad language.

If you want to rumor monger with absolutely no evidence to back up wild accusations, then feel free to do so elsewhere. If you feel you have evidence of developer bias, contact internalaffairs@ccpgames.com.

It really is that simple.

So the root cause of what happened isn't developer/sysadmin error (with a typo) and your system being flawed in accepting an erroneous entry and moving everything without proper precautions?