Skip to main content

Vinland 1936 refactoring.

As usual after finishing a game jam there's loads of stuff that I learned that can help me to make better games. Going back to a work in progress now feels really difficult because so much of the existing code looks ugly and inefficient.

I think I'm going to strip back a lot of the work I've done on V1936 so far and rework it.

Here's the new structure I want to implement:

Before, fog of war, level generation and agent management were all direct elements of the main loop. What this meant was that if I wanted to restart the game or load a new level it was best to reboot the main loop (restart the game), but this has quite high overheads all of its own.

During the making of "The Hole" I implemented a level manager, a container for the level and all agents etc... contained within it. I could pause the level, or reload it or do anything with it, without affecting the main loop. This made it great for adding cutscenes, or menus such as the inventory. It also mad transitioning from one area (level) to another almost instant. It also made transitions very clean. The player was destroyed and remade along with the level so no hangovers fro previous areas.

Another area I want to improve is agent states. In the past I've been putting a lot of the agent's behavior code in the states, but I've found it better just to put calls to agent behavior which is then stored in the agent. Then different states can be used with different agents, a single move state which calls move() on the agent, rather than a different move state being written for every agent type.

Comments

Popular posts from this blog

Vinland 1936

What have I been up to this month?

Well you can see it in a couple of development blog videos, here, here and here.

Vinland 1936 is a game I've been working on (on and off) for about 3 years. It is somewhat based on the old Nirval interactive game, Blitzkrieg;





I hope you've played it since it is one of the best games ever!!! (IMHO)
Blitzkrieg was a real time tactics game. You didn't build a base, or spawn units. It wasn't about rushing the enemy. You got a small number of troops and vehicles that could be replenished or repaired if you had access to a supply base and the right supply trucks, but couldn't be replaced if lost. Once your vehicles were destroyed and your infantry killed you were finished. You couldn't just churn out some more from your factory and have another go at rushing the enemy guns. This made you invest a lot in each of your units. They really mattered.

It was also procedurally generated. Each mission (except for the historical missions) was…

Reboot / Remake / Restart

Although the roguelike project was going well I had a few issues with some parts of the code, and the sheer size of the project was something I could see stretching away in front of me for years with no guarantee that people would actually want to play it when it's finished.

It's time to try something a little less ambitious.
I'm going full rogueLITE!

Using a lot of the code from the roguelike project, I started making a more limited game.
There will be a single character, combat will be more arcade like, there will still be a chance to upgrade and develop your character's stats, but they represent only a single class and have fixed equipment.

I've got a fun character, an interesting setting and an exciting story lined up. It still utilizes my low poly style, but things are going to be a little more cartoony.

Game play involves mostly chucking bombs at the enemy.

But there's also a lot of platforming, jumping from multiple levels is part of the game. And you ca…

Materials.

I'm currently working on the inventory and items system.
I've got a good idea of how it's going to work, and I've made a few test demos in blender so I know how it should fit together, but one area I had some trouble with is how to make the items more interesting.

I don't want to have just sword +1, necklace of AC +5 etc... I want items to feel like they are unique. So I'll be designing a few base item types and then having them generate some qualities.



The first quality is status. An old broadsword, or a rusty helm. Or spoiled meat. These will be limited by item type, so you don't end up with rusty meat or rancid chain-mail. They add a modifier to elements of the item's stats, either a positive or a negative modifier.

The second quality is wear and tear. This is more dynamic since it can change, as you take or deal damage. This might not be seen in the item's name, but rather in a status bar or something. However, it could cause the item to lose so…