So first thing’s first. Since my last update, I’ve put a tonne of work into Samurai Showdown, and you can now find the latest version on Itch.IO. It’s the first version of the game that doesn’t require two players thanks to a very simple AI, so now anyone can play the game!
As always, I’d love to hear what you think of the game, so let me know via Facebook or Twitter.
I know I’ve already written a post for today, but I decided to write about the work I’ve done on Small Gods in the six days since my last post. I’ve also decided to try and enforce a slightly more rigid outline of what’s been done in order to make these kinds of posts easy to read in the future.
I will, however, be keeping this update short due to a lack of images (when I get my first models and/or my logo back I promise I’ll spam pictures of them everywhere :D)
…. Alright, I’ll admit that it’s been awhile since my last post here, but I have access to an Oculus Rift again and can get back to work!
In the two weeks since university life has started again, I’ve done a fair amount of work on Small Gods and another project that I’ll be talking about Soon(TM).
For starters, I’ve recently set up a Trello board dedicated to helping me —and the people who’ve foolishly agreed to help me 😀 — follow the basic SCRUM methodology. This was pretty badly needed as previously I’d been doing everything without a real plan and I need to get the game in as good a state as possible within the few months I have left as uni.
As you can see it’s nothing much at the moment, but I’m hoping to properly fill it out as the weeks go on so that everything is in order and everyone knows what they’re doing.
Since my last update, I’ve been working on both the game and the project proposal in order to get them into a state fit for showing off. While there’s still a fair bit of work left to do it’s steadily getting there and I’m rapidly approaching the point where I no longer need to add AI Behaviours.In any case, since my last update I have:
The “”””fun”””” part of game development.
As part of my game dev work tonight I fixed four bugs/issues that were present in the game and discovered a new one that I’ve never seen before. The bugs fixed during this dev session were:
- The inability to change a worker’s job.
- The worksite of a builder being set to null for five seconds after completing a building. This resulted in workers completely freaking out as their behaviours would get confused.
- The camera movement only working properly when the player was facing forwards.
- Workers having their workplace being set to null when dropped. This prevented me from moving workers to and from the storehouse after they had filled their inventory with goods.
This is just a little update designed to show you what I’ve added since my last post so it’s nothing too exciting. In any case, the player is now able to assign workplaces to AIs simply by picking them up and dropping them on a building. Building-sites (the precursors to actual buildings) will create builders out of the AI dropped on them, farms will create farmers, and mines will create miners.
Another short update but this time, despite being about AI, I’m not declaring a blood feud.
Seriously, though, I’ve just added the basics of a builder AI to my game and aside from some seemingly small things they work okay! They’re currently very dumb (they don’t use resources when building, they sometimes get stuck inside completed buildings, like the other AI they generate exceptions that slow the game to a crawl if they don’t have something to do, etc etc) but for the most part, they work. I also seem to have broken the resource production code in the process of setting up my builders —I think the work distance check is messing things up— but I should hopefully have that fixed by next week.
This wasn’t as hard to implement as I was expecting it to be, to tell the truth.
Basically, all I’ve done is set it up so that the AI produce goods while working and if they fill their inventory with said goods they’ll go to the nearest storage depot with space and dump their goods there. The actual implementation of it is sort spaghettified and I’m sure that there’s a better way of doing it, but it works!
I’m not sure how I’ll end up implementing the whole resource system in the final version of the game, however. Right now it’s taking a similar form to that of the resource and storage system in Black and White where storehouses have a cap on the number of each type of resource they can store and so when a storehouse is full you need to build a new one. however, I may change it to be more akin to a traditional RTS resource system where collected resources are transported to a location that teleports it into a magical place where it’s accessible to all-comers.
This is just a short update to brag that I worked on the AI some more this morning and didn’t end up hating myself. 😛
As of right now, the AI in Small Gods will move to the nearest workplace that matches their skills and hasn’t filled up its worker count. If they leave their workplace for food, rest, or because they’re bored they’ll return to it after resolving those issues, however if the workplace has been destroyed since they left they’ll search for a new workplace altogether (starting the search at the nearest workplace to them that matches their skills).
I’ve also implemented the beginnings of the ‘work’ system itself and workers will be producing actual goods soon. (And then I’ll get to deal with storing items :v).
I hate them. I really, really do.
Seriously, I spent something like three hours today fixing something that I thought I had fixed yesterday but which turned out to have been broken all along in a way that made me think it was working. In any case, I have made it so that AI will now check to see if a worksite is fully occupied before determining whether they should go to it.
If a building is not fully occupied the building will be evaluated based on its distance to the AI and if it’s the closest one the AI will select it as the target and increase its current worker could. Meanwhile, a building that is fully occupied will be skipped over in favour of another workplace altogether. I don’t yet have a behaviour for what the worshippers should do if all workplaces are occupied (right now they’ll go to the first workplace on the array generated when they ask for the closet workplace), but I’ll handle that sometime tomorrow or Friday.
I’ll also need to add a similar behaviour for when the AI are looking for houses, and I’ll need to set up the AI to lower the current occupancy count of their workplace when they stop work. They don’t do that yet as I was tired of writing AI code and decided that 50% was a good place to stop (although realistically it’s about 25% done at best).