Cliffski's Blog

GSB recently got a shield support beam. This was a groovy empire-frigate-only weapon which remotely boosted the shield power of friendly ships. It was criticised as being too powerful. Not surprisingly, people experimented with minimal cruiser fleets boosted by a huge swathe of support frigates using the beams for mutual reinforcement.

Surprisingly, this turns out to actually be super effective in comparison with filling those frigates with weapons and other useful stuff. I spent a while playing, and analyzing player challenges where it was claimed the SSB is just *too* good.

So I nerfed it badly to see what was needed to get the sweet spot for this new weapon. Serious nerfing of the transfer rate was tried. Then serious reductions in the amount that would be held in capacitors. Still, the SSB seemed awesome, in large numbers.

Then, eventually, I concluded that it was the mechanic, not the numbers that caused an imbalance. The SSB was being used regardless of the state of the target ship. It could be under intense plasma fire, and be ECM jammed, and still shake offf all attacks thanks to 6 or 8 SSBs boosting its shields. I wanted a single SSB to be worth having, but at any reasonable level, the combination of 8 then became a super-defence.

So my currejnt thinking (under testing now) is to nerf the SSB by reducing two key stats (beam rate to 20, recharge rate to 20), and also introducing three restrictions:

1. The SSB can not be used to reinforce ships if the target ship is currently ECM jammed.
2. Only a single SSB can be utilised on a target ship at any one point in time (although they could take turns).
3. The SSB can only be targeted on cruisers.
   

I think this is the solution, but feedback is much sought. After all, I stupidly thought it as balanced already :D Ideas?

I am working on the various chunks of code that determine the strength of AI opponents in the GSB campaign game (currently being developed). The game takes existing challenge fleets, as well as other players campaign-fleets to use as the enemy, in massively-singleplayer style. However, it needs to select an appropriate fleet, in terms of strength, to fight against you, either as a defending fleet when you attack, or an attack on one of your systems.

The simplest method is just to assign a fleet size value to each planet, and let that be the strength there. Simple, but dumb, because nothing prevents the player sitting back and building up a larger fleet. A refinement would be to gradually ramp up a scalar for the enemy fleet sizes over the game, but that would mean it could spiral into insane difficulty, and doesn’t allow for different skill levels.

A system I’m working on is a ‘reactive-arms-race’ style approach. The nearby enemy worlds have their fixed starting values of fleet strength. When battle is joined, the Ai will start to build up larger fleets in nearby systems when it loses, and not bother if it wins. There will be some lag here, to represent building times.

The idea is that once you think you have a slight fleet-size advantage, you need to get all expansionist and start conquering, before the enemy realsies how mighty your fleets are, and builds it’s own countermeasures. If you just sit back and build up, the enemy will be doing the same. I may introduce an additional ‘anti-turtling’ scalar that starts ramping the enemy fleets up even faster if you have gone a long period without expanding your empire.

All this takes ages to code and test, and you never notice it’s effects on the surface. It is important to get this stuff right though (more important than adding more shiny or features) because it’s what drives long term playability.