EN24 discord
sov map

To keep? The Keepstar?

December 19, 2018

This morning when I woke up, I noticed that Lazerhawks was unanchoring their keepstars. For those unfamiliar with recent events, yes this is a big deal. Hard Knocks a wormhole group just like Lazerhawks came under siege by The Initiative and Goonswarm Federation. The objective of this siege was to kill the keepstar in Hard Knocks home wormhole known as Rage.

 

Now things die all the time in EVE, and it is part of the vicious cycle of destruction we all “mostly” seem to enjoy. But what is remarkable about these events is how they unfolded, and what preceded them. Let me start with a few things that preceded them. The past few months a whole host of armed keepstars have been destroyed by the same entities. Goonswarm Federation and its associated alliances have been able to kill a whole host of keepstars with relative ease. Of course, it required planning and manpower. And Goonswarm and its associates should be celebrated for their hard work. But the relative ease does make one wonder.

 

With ease, I, of course, mean a groups inability to defend them. The keepstar is supposed to be a space station of terrible destruction. A force multiplier if the battle takes place over it. But with all things EVE online, things do not always work out as intended. If one can have a mobile weapons platform and keep it out of range from the keepstar, you can attack the keepstar with impunity. Then if you vastly outnumber the defending side, they can never form a fleet big enough to defend it. And the keepstar will end up as a sweet killmail you can be proud of generating. An example of this would be the anchoring of the H-5 keepstar by Northern Coalition. However, is it really an accomplishment? As it stands now, one single group determines who is allowed to own a keepstar. No one else has the numerical support to defend a keepstar. Because of that, many groups will never consider owning a keepstar, or if they own a keepstar abandon it upon an assault. A clear example of this is the Hard Knocks keepstar, and the unanchoring keepstars owned by Lazerhawks. They rather unanchor those then fight for them in a future conflict.

 

Goonswarm Federation and its associated alliances cannot be blamed for this. The game is considerably in favor of numerical forces. Recent balance passes made sure that fighting outnumbered slowly became a thing of the past. The addition of skill injectors made it that everyone can catch up to high SP doctrines in a short amount of time. Making superior SP also less of a deciding factor in how EVE wars are won and fought.

 

As it now stands, one group decides who gets to play with keepstars. Not only because they are numerically superior. But also because of the keepstar own deficiencies. A keepstar should act as a force multiplier for numerically inferior forces. Of course, this will mean it also acts as a force multiplier for larger groups who already own one. But as it stands the keepstar is nothing more than a housing for supercapitals. That one group decides if someone else can use or not.

 

It is up to CCP games to decide if this is desirable. But a large portion of the player base is denied access to a keepstar purely on the basis that they are severely underpowered. And can be attacked with impunity by staying out of its range. With for instance the long-range mobile platform like the notorious boosh raven doctrine. In the past, we said that citadels where to oppressive and we would not fight on its grid. But being able to snipe a structure out of its range is just bad game design in my opinion.

 

If the option to abandon a structure is more enticing then to fight over it. Then something is wrong. It is not fun for the attacking side. It is not enjoyable for the defending side. Citadels and especially something as expensive as a keepstar needs to provide to the battlefield in a more meaningful way.

 

All I can say further is CCP, look at the game, you should have noticed by now that this needs adjusting. Be proactive about balancing not reactive.