The worst lag was when people were jumping in, wouldn't reopening the Brian in the Box idea really have helped in this instance?

What is "Dogma"? I'm sure you've mentioned it before but I can't remember what that system is.

It was not covered in the devblog but is there a significant difference between drones when it comes to the load on the server? There is a suggestion that all drones cause lag because they are self-contained units that need to move and shoot, implying that Warrior IIs are just as much a source of lag as Garde IIs. If that is the case, why all the furore about droneboats when most ships in these fights will be sporting their own flights which will be lagging out the system whether they are assisted to a player or not.

Then if you are against any solution that changes game mechanics

How much does a drone "lost" in space cost in performance?

How about entirely removing the auto attack behavior of drones

Would stripping sentry drones from all movement capabilties (ie. turning them into deployed turrets) help solve some of the lag related to them? After all, it takes all movement calculations out of the equations while nobody is going to miss that 1m/s..

There's been some speculation that loading inventories is server-intensive and that capitals, due to multiple inventory bays, may cause higher lag - is that correct?

Also, what sort of lag does refitting in space put on the node? Does refitting trigger the same sort of intense calculations brain in the box is intended to fix, because you've suddenly got to apply all sorts of new bonuses to new mods?

Prior to the fight CCP had to take down G-0 (our staging) and HED. This was because they were both located on the same node. This has occurred many times and has been escalated before. Why have more nodes not been put in the reinforcement pool?

How far would TiDi have to have gone to keep Dogma Lateness at zero? 5%? 1%? 0.01%?

As far as I know, Brain in a Box was never closed; the hold-up is in unraveling the legacy spaghetti-code, whose voodoo underpins the existing systems.

Perhaps get the people from Team Super Friends to give a hand...they aren't doing anything constructive atm.

Ah, so when the system approach 10% TiDi, all drones recall automatically due to "system interference" which would even be true.

Would also encourage peeps to stop using those idiotic ships.

You mean so they are treated as guns? They still need to be targetable but at least what you say makes sense :)

Prior to the fight CCP had to take down G-0 (our staging) and HED. This was because they were both located on the same node. This has occurred many times and has been escalated before. Why have more nodes not been put in the reinforcement pool?

Unavoidable O(n^2) things don't exist. Certainly not in a game. You can always optimize and compromise to avoid them.

So what can you do to avoid these n^2 problems? How about turning off collision detection (except with POS force field, for example) when TiDi is above some limit? I'm assuming you do not do collision detection with warp bubbles already unless warp attempt is actually initiated.

Everything else in EVE is not O(n^2) complex since there are limits - lock limits, watch list limits, etc. Because those limits exist, interaction complexity should not be O(n^2). Network traffic may still scale at O(n^2), but that can be managed and optimized at other nodes, not grid node (for example, I don't care if ship at 100km updates its position as frequently as a ship at 15km)

The only event that a client needs to be told is when the ship dies. Player X does not care that a drone is orbiting player B, especially when drones are not visible to player B! Sort and compromise so things scale. Send aggregate updates to clients that actually need to know about sum of events, not specific event. Player X does not care that Drone 123 hit for 5 dmg and Drone 154 hit for 20. It only cares that Player X sustained 25 damage in a given tick *iff* Player X is either locked by player B or is in Player B's watchlist. If Player B does not lock player X (and not in watch list), then Player B does not care that player X sustains damage.


There is no need or reason to be able to see (or be notified of) drone fire, laser fire, nos effects, etc. when there is TiDi on a server. Simplify and compromise algorithms so you do not have O(n^2) under TiDi.

Jeez man don't they teach you how to multiquote?