Daniel J. Petersen’s Devblog

Documenting my struggle to make a videogame.

Still Working on the GUI

Work continues on the GUI system for It Always Ends In Nuclear War. In my last post I talked about how I was working on an automatic layout system so that I don’t have to worry about manually positioning GUI items on the screen. This was surprisingly hard to do, but I did come up with something that I’m happy with. It’s not the greatest thing in the world as I only have so much free time to do this, but it should definitely help me out in the future.

At the most basic level, I’m thinking of each GUI component as a rectangle that takes up space on the screen. The layout system just manipulates rectangles for me by positioning and sizing them based on properties that I define for the rectangles. So if for whatever reason I want a GUI component to span half of its container in width, and all of its container in height (a container the size of the screen is always the top most container), be anchored to the left edge of its container with an offset of however many pixels, be centered vertically, as well as have constraints on the size (min/max width and height), I can do that really easily. The cool thing is that each GUI component can have other GUI components as children, allowing me to embed and use these position properties inside other GUI components.

I’m going to be working on the GUI system until it’s finished. I very much want to be done with this task and start work on the actual game again, but I think patience always pays off in the end. It should be worth it to have a good base so that I can quickly create / iterate on the GUI screens. In terms of components, at the moment I have a

I think that’s a pretty good list of things, but I still need to build out a tab container, dropdown list, input box for text, a list view, numeric spinner, and a color picker. I also want some way of making certain components scrollable. I have some vague ideas on how to go about making the components scrollable, but I’m not really sure how I’m going to do it yet.

I’m also trying to pick out color schemes for the GUI. I am not an artist, so I’m going to be going with plain colors / shapes instead of using premade images as a lot of games do. I’m thinking something simple like white text on a semi transparent background as shown here looks pretty good.

Three Day Weekend

I went to sleep at 7 PM last night, and woke up this morning at 9.30. I’ve got a three day weekend, I’ve got 14 hours of solid rest, and I’m ready to get shit done on It Always Ends In Nuclear War.

The biggest thing holding me back has been lack of a good GUI library. A lot of the game will come through interacting with the GUI, so it has to be easy and quick for me to iterate by adding / moving components around. It also has to look half-way decent to the end user. I’ve looked into third party GUI libraries in the past, and it’s been rough. I wasn’t sold on anything that I saw, so I opted to see how it would be making my own GUI from scratch.

It’s been okay. I’ve lovingly titled the GUI system I’ve been making SubGUI. I’ve got a button widget, radio button widget, a navbar, a progress bar, dialogue box, message box (dialogue box being a popup window where you click okay to dissmiss, messagebox being an area of the screen where messages appear / fade away after a certain amount of time), and an initial version of a slider. I’ve basically been making widgets as I needed. I’ve run into two main problems, though.

The first was blurry text. I narrowed it down to using antialiasing. Apparently if I had antialiasing turned on, the text also gets smoothed out, which is pretty terrible. I solved that problem by drawing the text on a RenderTexture off screen instead of directly to the window. The text still doesn’t seem as crisp as it does in a web browser, but I feel like it’s crisp enough, and if I spend some more time on it I’m sure it’s a solvable problem.

The other thing of concern has been how to handle the layout, which I had been doing manually. Each widget has an onResize method, and I define how it positions itself / sizes itself there. This works, but it’s a huge pain in the ass, and I don’t want to keep going down this route.

The way I see it, I have two options. I can either look into third party libraries once again, or I can try my hand at seeing if I can come up with something that automatically lays out my components in a reasonable way.

The path of least resistence is to look into third party libraries / frameworks, which I’ve been doing the past week or two. It’s been rough. I don’t want to deal with working in another language, so that means only C++ libraries / frameworks. I’ve considered in one way or another qt, wxFrameworks, gwen, imgui, myGUI, crazy eddies, gtk, using chromium to build the GUI with web tools (html, css, js), guichan, otterUI, SFGUI, and turbo badger. Out of all of them I liked imgui the most, but I wasn’t sold on any of them.

I’ve decided that I’m going to go ahead and do the stupid thing, which is to make a layout engine and continue to create my own GUI widgets. I started to implement it on Thursday, and I think it’s reasonable. I’ve got a design for the layout API, a decent idea on how it should behave, and three days to make it happen. I’m actually hoping to finish the layout manager early, and work on adding more components to the framework, but I’ll be happy enough if I come out of this weekend having something which does automatic layout in a reasonable fashion.

Risk 2.0

Late last Saturday I decided to check out Typescript , which is a programming language which takes Javascript and adds static typing, classes, and a few other much needed features. I’m really liking it, it’s so much more of a joy to work with compared to regular Javascript. Javascript gets a lot of hate, and while I think a lot of that hate is unwarranted, it definitely can be improved upon, and there’s no doubt in my mind that Typescript is an improvement.

So I played around with Typescript and ended up making a clone of the board game Risk.

I’m hosting it here –
The code for it is here –

I have no idea what the proper project structure is for a Typescript project, nor do I know how to properly do version control with it. I suspect you’re not supposed to commit the .SLN file, but I can’t say that this project is important enough, or that I’m motivated enough to find out right now.

But yeah. Feature wise it’s complete, although I made a few sacrifices such as a lackluster UI, and I opted to allow infinite moves per turn. I think in the official version you can attack an unlimited amount of times a turn, but only move an army to a friendly territory once per turn.

This concession was made entirely for the AI, which I still need to finish. I imagine it won’t ever be good, but I think it’ll be all right once I finish up the code for making the AI capture a continent if it determines it has the numbers to do so, and spreading its armies better across continent chokepoints. There’s also one bug that I’ve encountered and need to squash, where occasionally territories won’t change owners after an attack. I’ve looked into it and I have absolutely no idea why that’s happening.

I’m thinking I’ll spend a few hours over the next week on finishing that up. This weekend, though, I’m going to continue to work on my eternal struggle, It Always Ends In Nuclear War. I think I have to occasionally take a break from working on It Always Ends In Nuclear War and do these smaller projects, or I’m going to lose my mind.

It Always Ends in Nuclear War Update 3.21.15

I was supposed to post an update last Sunday on what I accomplished that weekend on It Always Ends In Nuclear War , but I didn’t end up accomplishing much. I spent all Saturday and Sunday debugging various errors with the game that had popped up, which is harder to talk about than shiny new features. I mostly worked on fixing issues / crashes due to incorrect syncing of data between the province view screen (pictured below) and the actual game data.

I don’t expect this screen to look anything like this when the game is done, but it has to look like something for now and I’m not sure where it’ll end up. In any case, I’ve worked out all the issues and the game is once again solid as a rock in terms of bugs / crashes. I have no one but myself to blame for the issues, though. I’m making my own GUI system for this game and it’s a learn as you go process.

I also spent a little bit of time last weekend stress testing units / pathfinding and I’m pretty happy with the results.

That’s a few hundred units auto exploring the map. This is subject to change, but I currently envision the game ticking along at a solid rate similar to the Europa Universalis series, so it’s pretty important that the time between turns is almost non-existent.

Last night I built another GUI widget for the game – We now have progress bars! Try to contain your excitement.

It might be a bit hard to see with the embedded screenshot. At the moment I’m using it to countdown time until the next game tick occurs (aka the next ‘turn’), as well as to show the progress of things being produced by a province.

The remainder of this weekend I’m going to attempt to actually hook up the province growth algorithm that I have planned. I want the number of births per 1000 people to roughly approximate the rate that populations have grown through history. I’m going to have a rudimentary model of disease and a food/starvation system to keep populations from growing indefinitely. In Civilization, population grows on a stairs sort of system, where it’s flat for a long period of time and then it bumps up instantly when you fill up your food bars. I want the population in this to grow in a more linear fashion, until you start developing technologies to eliminate starvation / disease.

Ruby Is a Mess on Windows

If you’re wondering why I haven’t updated this website in a while, it’s because this blog is using Octopress , which requires Ruby and quite a few gems in order to work. I reformatted my computer a month or two ago, which means that I needed to reinstall my Ruby enviornment. I suspect it’s because I’m on Windows, but I’ve run into quite a few issues trying to get everything up and running, and I haven’t had the heart to fix them all until now. Seriously, Ruby on Windows is an absolute mess. I hope I never make the mistake of doing another personal project with Ruby again, because this is unacceptable.

For comparison, I checked out the most popular non-ruby static site generator out there which is a Python library called Pelican . I don’t even remotely like Python, but it was an absolute breeze to get up and running compared to Octopress with Ruby. I like the default look/layout a lot better on Octopress, so I decided to stick with the current setup for now, but I’m going to have to switch this blog over to something else eventually.

Who cares about that though. Let’s talk about the game that I’m making, It Always Ends In Nuclear War.

It’s been slow going, but I’ve been getting at least a few hours of work in every week, and I have super high hopes for this thing. The subtitle of this blog is “documenting my struggle to make a videogame”, and it really is an absolute fucking struggle. I feel like the code behind it is good, but there’s just so much to do, and if I’m being perfectly honest I have no idea how to design a video game. It feels debilitating knowing that it’s all on me to make this thing a reality. I feel like I’d be a lot better off personally if I had never decided to try to make a game, but I think I’ve reached a point where I not only have to finish it, but where I know that I can in fact finish it, and that it’s going to be good. It’s a very nice and sobering thought to me.

When it’s closer to being complete I’ll get around to posting about how it actually plays, but for now I just wanted to post this little update.


I worked a bit today on the code for getting armies (units) working, and then got bored of that and decided to get the game up and running on Linux. Cross platform libraries are crazy – It basically worked out of the box.

The low FPS is from the screenshot program freezing everything.

It’s the Little Things Which Matter

Happy new year! Let’s get to it.

The Civilization series used to have a flaw in that the minimap would reveal exactly where you were on the map. It wasn’t a huge deal, but it could be abused in some situations. For example, if you spawned near the top of the map, you’d be able to see that and plan accordingly. Scouts would be sent south, settlers would be sent south, and no time would be wasted exploring the north of the map. I’m not sure what version of Civilization fixed this, but it was fixed by having the minimap zoom in to fit the area explored.

I’d like to have that same need for exploration in IAEINW. You should have to explore or look at the terrain type to figure out where you are on the map. Up until today, however, you were able to abuse the sides of the map to figure out where you were in the world. Check out this old screenshot to see what I mean.

A few months back I sort of fixed it by only drawing a side of the map if a player discovered a tile on that edge of the map, but this wasn’t perfect. The entire side was still drawn, so you could gauge exactly how large the map was and where you were in it once you discovered one edge. I’ve been wanting to fix this for a while now, and today I finally got around to it. I’m now only drawing the edges of the map between the furthest explored reaches of the edge. Check it out to see what I mean

There are more important things I could be working on, but it’s the little things that make me happy.

Everybody Loves Pathfinding

I’m still working on It Always Ends In Nuclear War, which I suppose can be described as my attempt at a 4x civilization-building game. Randomly generated map of the world, small group of people founding a city at the dawn of civilization, expanding your territory, meeting other civilizations, making alliances, fighting wars, discovering technology… That type of thing.

I admittedly don’t have much progress to show at the moment, but I am putting in a great deal of time and effort. I think the problem is that I have incredibly high standards, and I’m never quite happy with what I come up with for the game. I want to produce something that is not only fun, but a unique take on the genre. I want to produce something that looks good graphically. It also has to be something that I can create in a reasonable amount of time.

I feel confident that I can program whatever design I come up with, but coming up with a good design is challenging. I’m working on this project by myself, so I’m very much working in a bubble. Creating something that is not a cookie cutter copy of the popular titles in the genre is hard. Doing it without having someone to talk to about the ideas is harder. I’ve settled on a few different designs in the past, prototyped them out, and hated them. I’m keeping at it, and I have confidence I’ll get there eventually, but it’s just frustrating. Frustrating and time consuming.

Graphically I like the direction I’m headed, but there’s definitely something not quite right about it. I’m about as far from an artist as one can possibly get, so I think what I’ve done so far is pretty good, but like I said, it’s still not there yet. As you can see, the current thinking is that the entire game is going to have a textureless look, possibly even going as far as to have no sprites or external images used at all. This serves a dual purpose - It takes some pressure off of me having to somehow get high quality art assets, and I also think it gives off a unique stylistic vibe.

One of the design decisions that I’ve settled on is that the game will not be turn based. It’s going to tick along at a solid rate, similar to how the game Europa Universalis works. Another design decision that I’ve settled on is that there are going to be armies, settlers, and ships roaming around the map. This provides a bit of a challenge in regard to pathfinding. I want the game to be playable on a modest computer, and given how large the maps are (84,000 tiles!), and given how many units could possibly be present on the map at a time, pathfinding needs to be trivial from a performance point of view.

I implemented a pathfinding algorithm known as a* (pronounced a-star) forever ago, and it miraculously still works with It Always Ends In Nuclear War after all the changes I’ve made to the code (check out the above screen; purple tiles would be the path), but I’m going to have to improve the system further if I don’t want it to grind the game to a hault.

It’d be great if there were two search modes – an accurate mode, which found a path on the actual map the player sees, and a simplified mode, which was essentially finding a path on a representation of the map on a smaller grid (because there’s worse performance for larger search areas). In fact, I already have a smaller representation of the grid coded up in memory. The game was initially more akin to a clone of the game Civilization II, and looked like this zoomed out:

I described in this post how I went about taking the old maps, which were about 5,000 tiles in total, and transforming them into the new maps, which are 84,000 tiles in total. It should be pretty trivial to keep the old map in memory, perform our pathfinding on it, and then convert the tiles into tiles on the larger map. This would be useful for if a unit needs to plot a path far from where it’s currently located.

This would even allow me to precompute and/or cache some common paths, which is the approach I took in the game Sins of a Hex Empire. There I stored the path to every possible location you could travel to from any given hex. Generating a map took slightly longer because it had to precompute all the paths, but it allowed me to have a better AI since I could brute force more stuff, and it had no wait time between turns.

You can see this working here. It shows the number of turns it would take from the topleft most tile to reach any other given tile. This was done and saved for each tile. Then to find a path, you’d just start at the goal and travel backwards, with the next tile being the lowest number. Truth be told it was overkill for the game, but I think it might be worthwhile for IAEINW. It wouldn’t be a good idea or perhaps even feasible to do with 84,000 tiles, but it might be reasonable for the simplified map.

That’s all for now. Hopefully I’ll have some actual progress to report soon.

On the Importance of Free Time

The most valuable skill that I know is programming. It’s paying the bills through an awesome job, and it’s filling my spare time through personal projects that I enjoy working on and articles that I enjoy reading. I have no idea where I’d be right now if it wasn’t for programming, but there’s no doubt in my mind that I’d be worse off.

It’s a skill that I never would have picked up had I not had an absurd amount of freetime somewhere around 2012. I was going through school to become a Stenographer (I went on a pretty decent rant about Stenography two posts down), and the school only met for two five hour days a week. They expected you to practice in your spare time, but truth be told, I never felt the need to. Stenography came naturally to me, and 10 hours a week was more than enough for me to graduate half a year earlier than expected. I had a part time job at Staples, but that didn’t eat up too much of my time either. I began looking for things to do with this free time and decided to take up programming, I’m not even quite sure why. I guess I had a vague idea that I wanted to make create things for the computer.

Learning it was hard. I remember buying huge books, reading them slowly, and then rereading chapters which I didn’t quite get on the first pass. I remember working on a lot of small projects where I bit off more than I could chew and churned out some awful code. I don’t consider myself a particularly good programmer, and I guess it’s funny how that works out – I was unnaturally good at Stenography, something that I thought I’d do for a career but it turns out I’m never going to have a valid use for in life, but I very much struggled with programming, the thing my actual career requires I be good at.

I’m very lucky that I had that free time in 2012. I would not be where I am right now without it. I would have been able to put in the time it required for me to reach a certain level of competency. I would not have even known that programming is something that I enjoy, something that is valuable, indeed more valuable than anything else that I had known prior to that.

And there’s the point. I feel like you need free time in order to figure out who you are and what it is you want to do with your life. Hell, you need free time to figure out what it is you even want to do with your free time. I feel like most people don’t have the luxury of free time. They’re working paycheck to paycheck to survive, or they’re putting in too many hours for school on a major that they picked on a whim.

I remember being interested in learning how to program in 2010. I was in college at the time, and thought I’d sign up for an intro to programming course and see what it was like. There wasn’t any at my school. But I did find a course on making basic websites, I think it was an intro to HTML or some other nonsense. I came out of that class knowing less about how to make a website than I had when I came in. The lectures they had didn’t explain much or give any context to anything. What they did teach was how to copy website code from an ancient HTML book, and the code wasn’t even good. The book had websites which were constructed with tables and frames, it probably came straight out of 1996.

And there’s the other point. You are the only person you can rely on to learn what you want to learn. Yes, you’ll need to use guides and resources provided by others, but it’s really up to you to research that what you’re learning is good practice and the proper way to do whatever it is you want to do. And to tie it back into the previous point, you need free time in order to do this. I have no doubt in my mind that I would have came out miles ahead had I put in my own time and research into learning how to make websites instead of essentially taking a gamble and signing up for a course hoping that whoever was the instructor knew what they were talking about.