A Billion Suns Introduction

I like A Billion Suns because it does not treat space combat as just two tidy battle lines trading shots until one side runs out of ships. It is a fleet game, but it is also a game about contracts, profit, timing, and deciding how much force you are willing to commit to a job before the job stops being worth doing.

The game is by Mike Hutchinson and published by Osprey Games. You may know Hutchinson from Gaslands, which is a useful point of comparison only in the broad sense that both games are good at turning a simple table setup into a messy decision engine. DriveThruRPG and Wargame Vault have the digital listing for the first edition, which is handy if you prefer PDF rules. Osprey Games also lists a second edition for pre-order, with availability shown as 27 October 2026, so check which edition your group is using before buying or printing aids.

This is a fan introduction, not an official rules summary. The aim here is to explain what makes the game worth looking at and what I would pay attention to before putting ships on the table.

The basic idea

A Billion Suns is miniature-agnostic. You need spaceship models or tokens, dice, a tape measure, cards, markers, and enough table space to make the battles feel like they are happening across more than one bit of space. That last point is important. The game is not just a single furball in the middle of the board. Ships can arrive, move between battlefields, complete contracts, and leave again.

The players are not only admirals. They are more like competing space CEOs, sending forces into danger because there is money to be made. That gives the game a different flavour from the usual heroic fleet action. You can bring in more ships, but ships cost money. You can solve a problem by throwing metal at it, but that may leave you with a poor balance sheet at the end. Winning a fight and winning the game are not always the same thing.

Ships arrive when you need them

One of the clever parts is that you do not begin with a fixed fleet list in the usual way. Ships can be brought in during the game, and the decision to bring them in is itself part of the play. This makes the opening feel less like a pre-planned deployment puzzle and more like an unfolding job. You look at the contract, the enemy, the table state, and your own nerve, then decide what you are willing to pay for.

That can be a small scout or fighter presence, or it can be a heavier ship if the situation is getting serious. The danger is that every answer costs something. I like this because it makes restraint useful. Many games reward you for having the right unit in the right place. A Billion Suns asks whether you can afford to have it there at all.

Contracts matter

The contracts are the heart of the game. They tell you what the fight is about and give the battle a shape beyond simple destruction. You may need to claim something, scan something, destroy something, protect something, or move assets through dangerous space. The card-driven setup helps keep games varied, and it makes the table feel less like a formal tournament lane.

This is also where the game gets its best tension. A ship may be in a poor firing position but close to completing work that actually pays. A large vessel may be impressive, but if it is tied up in the wrong place, it is only an expensive ornament with guns. The game rewards players who keep asking what the job is. That sounds obvious, but it is easy to forget once the shooting starts.

Multiple battlefields

A Billion Suns can use more than one battlefield, and this is worth keeping in from the start if you have the room. You do not need grand terrain. Separate mats, table sections, or clearly marked zones can do the job. What matters is that ships can move between places, and that the player has to think about where attention and resources are being spent.

This gives the game a campaign-map feeling without needing a campaign. You can have one area where a fight is building, another where a contract is nearly complete, and a third where a ship has just arrived and is about to become a problem. It also helps smaller ship groups feel useful. Not every ship needs to be in the main brawl. Sometimes being somewhere else is the whole point.

Miniatures and practical setup

The miniature-agnostic side is a real strength. You can use old spaceship models, 3D prints, counters, tiny toys, card markers, or whatever looks good enough to your group. Scale is not worth getting precious about unless your players enjoy that sort of thing. Consistent basing and readable ship types matter more than perfect proportional modelling.

If I was setting up a first game, I would make simple labels or ship cards before worrying about a beautiful fleet. The game asks players to track what ships are doing and what contracts are being pursued, so clarity helps. A cheap printed token that everyone understands is better than a lovely miniature nobody can identify after turn two.

This is also a good game for using neglected models. If you have spare fighters from one range, cruisers from another, and some old capital ships that never found a home, A Billion Suns gives them a job. That is one of the quiet pleasures of miniature-agnostic space games. The setting at the table belongs to the players.

How it feels in play

The game feels more economic than many fleet games. That does not mean dry. It means that most decisions have a cost attached, and the cost is not only damage. Calling in another ship may solve the immediate problem but reduce your profit. Ignoring a threat may save money, but only if the threat does not ruin the contract. Overcommitting can win the battle and still leave you feeling as if the accounts department will have questions.

The dice system is straightforward enough that the game can keep moving, but the surrounding choices give it depth. It is not a game I would sell as a detailed starship simulator. It is better understood as a playable fleet game about risk, commitment, and opportunism. If your group likes clean fleet lists and symmetrical stand-up fights, it may feel odd at first. If your group likes scenarios with awkward priorities, it should land better.

Starting sensibly

For a first night, I would keep the fleets modest and the table easy to read. Use two or three distinct ship sizes, simple markers, and clear contract notes. Do not make the first game a modelling showcase. Make it a rules-learning game that still looks enough like space combat to be fun.

I would also decide in advance how strict you want to be about model identification. In a casual game, coloured bases, printed tags, or small cards beside the table are fine. Use whatever works. The aim is to get players making contract decisions, not arguing over which grey wedge is meant to be the destroyer.

Why it is worth a look

A Billion Suns is worth a look if you want a space game that makes the mission matter. It gives players big ships and explosions, but it keeps asking whether those ships are earning their keep. That one question changes the feel of the game in a useful way.

It is also friendly to existing collections. You do not need to buy an official fleet range to try it. If you have models, printouts, or tokens, you can start. If the second edition becomes the local standard after release, the same general appeal should still be there, but check the new book before assuming every first edition habit carries over unchanged.

My suggestion is simple: gather a few ships, make readable markers, set up two battlefields if you can, and play for the contracts rather than the kill count. Have fun with it. The game is at its best when somebody realises that the impressive enemy cruiser is not the real problem. The real problem is the small ship quietly finishing the job somewhere else.

All trademarks and copyrights belong to their respective owners. No challenge is intended.