Rank: Warmaster Transparency Message for March 5th, 2026

An update to the open and honest letter of where are things and where are they going

It has been years since the last update. Someone asked me today if the project is abandoned, and I said no but I realize that no one else knows that. As mentioned previously, a series of other games to feed back into this one was planned. So things have been moving behind the scenes.

Short answer: No, it's not abandoned, but from the outside I completely understand why it looks that way. We are building using a far more round about method by releasing feeder games for financial and engine update reasons, and the first of those is about to be released!

[dynamiclink href="https://store.steampowered.com/app/2284080/Rank_Warmaster_Bunker_Buster/"]

Long Answer: What actually has been happening:

As mentioned in a previous update a few years ago, the idea was to create "smaller" games on the same engine that could feed back into Rank: Warmaster drastically improving it to make it more viable for a modern audience. Unfortunately, that is the key goal, making Rank: Warmaster more viable for a modern audience. There are a lot of things graphically and functionality wise that people expect as a minimum that the Warmaster Engine or its assets doesn’t meet. Spending the time it would take simply improve it and the assets, would be about the same time to just make another game, and back port the improvements.

As people may know, there is a lot of chaos and uncertainty in the gaming industry right now. I don’t have the budget or resources for the more direct approach, so I have to raise capital by making other games first. Rank: Warmaster Bunker Buster (RWMBB) is the first of those. Ok, what did that add?

• 32 bit to 64 bit engine conversion – The Warmaster engine that is used in Rank: Warmaster (RWM) is 32 bit. Bunker Buster provided the time to convert it up (which did take a while as expected). Modern game effects basically require 64 bit memory comprehensively together. RWM runs in 2.5 GB of RAM because of the limits of 32 bits only being able to address 4 GB of RAM with windows itself eating the top 1.5 GB. I hit an impassible wall with pure AMD systems which handles memory differently to the point the game wouldn’t run. That is the main reason I stopped doing direct updates to RWM because there was nothing I could do until the engine was 64 bit. At the time, it didn’t make much sense to spend the many months it would take to convert and just be in the same spot. The original public release demo of RWMBB was still 32 bit, since it still didn’t make sense to spend the time. However, after the game was complete on the coding end, and while the levels were completed out, it made sense to finally do the conversion. In so doing, while scary, the engine became more stable, I could use more modern tools, and I could implement more modern features that were walled out from before. Also, the AMD issue went away. But this only happened at the end of last year.

• Addition of PhysX – Another upgrade was adding a more robust physics system. I had my own home grown one that did the job, but it isn’t on the same level as something as dedicated as PhysX is. RWMBB 32 bit had PhysX 4.X while the 64 bit version was able to go to 5.x. What does