Friday, November 1, 2019

A Change To The Ansiblex Jump Gate Change

At EVE Vegas, we learned that in the Beat Around the Boosh content drop, Ansiblex Jump Gates would receive a anchoring restriction of 500 kilometers from other structures. However, any existing gate could remain in place and still function. Today CCP changed their minds.


When I first heard of the plan to grandfather in any jump gates that fell within 500 km of any other structure, I thought that couldn't last. From a technical standpoint, the situation would get messy. Imagine having to keep track of exempt structures in a database table somewhere. Then, during downtime, run a script to determine which ones were destroyed or otherwise no longer qualified for the special treatment. On top of everything else, QA would have to test each release for years to make sure no new feature broke the grandfathered placement.

Along a similar vein, imagine CCP trying to run a script that would automatically move existing gates 500 km from other structures. What is worse for an alliance logistics team?

  1. CCP moves the jump gates out of range of a citadel's weapons, then the logistics team has to visit each gate to make sure the gate is properly placed. If not properly placed, the logisticians then have to unanchor the gate and place it in a different location.
  2. The logistics team moves each gate to its proper location. The logisticians unanchor the gates under the cover of the citadel's weapons.
I honestly don't know. I've never done null sec logistics. Either way, the process sounds painful.

From a gameplay perspective, I don't really have an opinion. I do think that making the change announced via Twitter will help on the technical end. From my perspective, the change to Ansiblex Jump Gate anchoring distances will cause enough drama. No need to possibly continue the drama for years to come.

No comments:

Post a Comment