Balancing Function With Simplicity

I’m a simulationist. When I make a game, I want it to handle the situations that I throw at it and I want the whole thing to be elegant. The problem I have is, I’m always adding more situations that I want my games to work under.

For example, in the Energy System (the system that is powering Protector and Jump Temp) the function of things like vehicles is pretty simple. The problem I’ve been having is how many passengers a vehicle can carry. On the one hand, I could just say “use common sense.” A motorcycle can carry one or two people and a car can carry four or five and be done with it.

But then I wanted to throw a light airplane in the equipment list. How many people does it carry? One? Four? Twelve? How big is a “light” airplane?

That’s a bit of a minor issue, but not simulating things like passengers properly leads to weird issues. For example, a motorcycle is probably a little faster than a car, but the car can probably travel further. As things are, they kind of balance each other out and motorcycles cost about the same as a car, which is an odd result.

That kind of thing really bugs me. There are structures in place to handle this kind of problem, but the system handles everything in terms of challenges and I’m not sure what kind of challenge “passengers” are and if I want to spend time in game even handling that.

I could write it off and say “Adding one passenger costs one die” and that could work. The problem with that is it’s one more rule to add to the system.

I had to half add a rule for money. In reality, all I did was explain how to handle money in the existing framework, but it had to called out and explained. I’d rather not have to add a special rule for passengers.

I’ll work on it. . .

Leave a Reply