Category: game design

I’ve been trying to avoid acting too much like a graphics junkie and getting some work done on the gamey stuff instead. I’ve put in difficulty levels today, and also made some decisions regarding what race of aliens the player controls.

The main part of the game currently has ten missions, basically defined by a certain backdrop, of a certain size (some maps are bigger than others) which some other variables such as nebula effects on shields etc. These levels also define the maximum fleet size (in ship and pilot terms) and which race the player fights against.

So today, each of these missions has three enemy fleets rather than one, the normal, hard and expert AI fleets, which are of differing sizes. Obviously the bigger fleets are harder :D. During combat, the enemy AI is the same as yours, so the difficulty comes purely from the force that is fielded against you. I may get around to the AI evolving its own fleets, but thats a whole can of worms.

There will be some ‘other stuff’ that will give the game longevity beyond those 3 fleets in 10 different missions, but I’m not talking about that stuff yet :D

The other thing decided today was that the player will fight the game as ‘the federation’ which is a ferengi inspired race whose backstory I’m still mulling over. Once you have beaten every mission on Normal, you will unlock the Rebels as a selectable playable race for each mission, beat them all on Hard and you unlock the Alliance, Beat them all of Expert, and you unlock the Empire. That’s the plan anyway. Any thoughts?

I’ve thought about the AI for Gratuitous Space Battles a lot. I have a lot of ideas, some of which I’ll sketch out, and some I’m keeping secret for now.

When I say ‘AI’ I’m being pretty nebulous. I don’t use AI in the trad comp-science limited sense of it. I’m talking about the whole matter of computer-controlled opponents. Who they are, how they are selected etc. Because GSB is a ‘hands-off’ battle game (for now), there is an element of determinism about how the battles work. In other words, if you design a fleet, in theory the AI can design one that it is assured of kicking your ass with.

There are many ways it could do this. The most obvious bruet force method is to randomly design fleets and pick the one that beats yours. Another would be to have some initial ‘seed’ fleets and do a genetic mutation – evolution algorithm to deduce the ultimate fleet against yours.

However, while I want a challenge, I don’t want you to be beaten every time. Plus, the ‘problem-space’ is colossal, way beyond chess, because there are maybe 40 hull designs, maybe 100 ship modules, near infinite combinations of ships and modules, and that’s before ship placement or ship-behavior/instructions. It’s not possible for the AI to beat your fleet using deep-blue style iteration of possibilities.

So there is a good chance the final AI will be some mixture of pre-designed (by me) AI fleets, combiend with an element of letting the AI battle several thousand slightly randomly mutated sample player fleets, and improving on my initial design.

I’m sure everyone has lots of ideas of where else to go with this, such as machine learning, copying player fleets etc. Needless to say, I’m mulling over them all :D

One of the big problems with Kudos and Democracy (my two best selling games so far) is that they are basically fixed resolution games. Democracy 1 supported two resolutions, and you can always hack them by fiddling with config files, but basically those games assumed a certain size screen and didn’t scale up or down.

With Gratuitous Space Battles, I’m aiming to support both people with huge monitors, and hopefully people with small laptops, running 600 pixel high screens.

That will mean some major fiddling with the ship and fleet design screens, and the pre-battle deployment screen too. The big probloem will be those 600 pixels. Of course, I could do some super-dynamic scaling thing, but it’s not nice reading text designed for 1900×1200 on a 600 pixel height laptop.

What I probably need is a number of different windowed layouts for different size monitors. The battle screen will be easy, because it already happily scales without any issues.

So if the fixed resolutions of Democracy 2 and Kudos 2 bugged you, don’t worry, I’m fixing it this time :D

BTW, I released a free add-on mini-patch to Democracy which adds a new dilemma for banking bonuses:

I’ve finally got code written that supports the same ship module having different sprites on different spaceships. What this means is that the same weapon (fast pulse laser) can look different on a rebel ship to a federation ship, so hopefully they don’t ever look too out of place.

This works fine, but right now I’m assuming I’m using the same hi-res 3d image for the weapon on the ship design screen, regardless of which ‘race’ the ship hull is from. I have several ways to fix this, none of which are ideal…

I could have different 3d renders for each turret on the ship design screen, depending on the race of the ship hull. This is a lot of work, and also might be confusing. Shouldn’t the player be able to recognise a pulse laser icon regardless what race he plays?

I could have a generic 3d image for the design screen, but represent it differently on each ship, which is easier, but it means breaking the visual connection between the 3d render and the 2d sprite which might be confusing.

I could scrap the idea of the turrets representing individual variations, and just have 3 or 4 turrets for the battle screen, and tons of different 3d ones for the design screen.

I really like the idea that placing a turret in the design screen reflects exactly what the ship will look like in battle. However, it doesn’t really matter in gameplay terms, and ease of use on the design screen is the most important thing. Maybe I keep all the data the same, but have different sprites and 3d renders depending on the selected ship hull. In any case, there is tons of 3d modelling, rendering and data entry to do…