This post is about how Spring configurations are used in this project.

I had an issue with a builder. I had used it like this:

reportCreator.start(game, raceId).type(PlanetHasBuiltMinesReport.class)
		.addArguments(name, numberOfItems);

In the last post I described an alternative to a POJO with getters and setters for holding data. I used beans for access:

@Autowired private PlanetName planetName;
...
Planet newPlanet = ...
String name = ...
planetName.setValue(newPlanet, name);

I ended with a few pros and cons and

When the data is stored together (in the map), it is jumbled up. Maybe that will prove painful, maybe when migrating data?

Requirements

Like a lot of other software, Stars! contains lots of features that are totally independent from each other. But an implementation of Stars! also needs to allow for interaction between these components, for example:

• The disadvantage of Only Basic Remote Mining gives you an extra 10 % planet capacity as compensation.
• You can put gadgets into your ships. They provide several benefits, that will be handled by different (Java-)components, impacting several features. And also
  • you need to research gadgets to be able to use them
  • each gadget has a weight, which affects fuel usage
  • depedending on the race you are playing, some gadgets may be available to only you

This is a blog about the reimplementation of Stars! on GitHub.