Battlehouse Dev Blog, Issue #10: Chat Improvements, and more

📢 Attention Thunder Run, Days of Valor, Mars Frontier, War Star Empire, Battlefront Mars, and Firestrike Commanders:

Welcome to the 10th installment of the Battlehouse Dev Blog, a place where fans of all Battlehouse games can enjoy regular behind the scenes peaks into the minds of Battlehouse Developers. Without further adieu, here’s bh-nirgal to talk about some in-game chat improvements, and development updates for all games:

Chat Improvements

This past week has mostly been dealing with quality of life improvements and patching UI errors.

The biggest change was enabling mouse wheel scrolling in chat. All games benefited from this change.

We’re going to pause on UI improvements for a short period to get a few content patches out for Firestrike, Mars Frontier, Battlefront Mars, and War Star Empire. These are smaller games that represent a smaller portion of the income that keeps the whole ship afloat, but they deserve new content too! We’ll return to UI improvements for all games shortly afterwards.

When we return to the UI, the next step is to expand the player options menu to allow scrolling. There’s no room left right now to add options, and a lot of upcoming UI improvements need to be something the user can toggle. Sadly, this is not something we can just flip a switch on, but once scrolling is added to a UI element it can be expanded easily in the future. While we’re at it, we’ll make sure mouse wheel scrolling works in this UI element.

Once player options can scroll and we have more room to give you options to choose from, here’s the new options we’ll be adding:

  • Turn off screen shake when explosion effects happen.
  • Reverse chat window vertical orientation. New messages and the input window on the top, or new messages and the input window on the bottom. Your choice.
  • Reverse mouse wheel scroll direction. Scroll down to go down, or scroll up to go down, your choice.

Game Development Status Updates

Firestrike players: You’ve been asking for it, and it’s in the works. Tier 16. You’re getting new levels to all units, new levels to all tech, new levels to all buildings, the addition of barriers, and one new unit. This is a big patch, so it might get broken into stages.

Mars Frontier: You’re getting a new Central Computer level, reduced build times for existing building levels, and a new level for all units. Most of the work on this was already done, so expect it very quickly.

Battlefront Mars: You’re getting a new level for all units, and one elite unit. A lot of the work on this is already done, but it needs some polish. It shouldn’t take too long.

War Star Empire: You’re getting a new level for all units and some additional turret levels. About half of the work on this was done between other patches, so it won’t take too long.

There’s not much else to discuss this week. To our American friends, enjoy gorging yourselves tomorrow. To the rest of you, have a great week.

Stay up to date every day on what’s being developed on the dev-tracker channel here.

Looking for an update on where the Dev Team currently stands regarding various recent community suggestions? Check out our “Voice of the Commander” trackers here:

Like what you see in this Dev Blog, or have suggestions on things you’d like to see addressed in our “Voice of the Commander” trackers? Let us know over on our Thunder Run Discord Server!


Battlehouse Dev Blog, Issue #9: Thunder Run and Days of Valor Updates

📢 Attention Thunder Run and Days of Valor Commanders:

Welcome to the 9th installment of the Battlehouse Dev Blog, a place where fans of all Battlehouse games can enjoy regular behind the scenes peaks into the minds of Battlehouse Developers. Without further adieu, here’s bh-nirgal with some more development updates for TR and DV:

Thunder Run and Days of Valor Developments

Let’s take a moment to recap a recent change. As part of the release of the TOC12 infantry buildings and the new L16 for non-elite infantry, we reworked one of the least-used elite infantry units (Elite Stinger Gunner) and put it on sale.

One of the things we do behind the scenes is examining the stats of deployments of unit types, adjusted for their unit space costs, and trying to encourage a reasonable distribution of deployments. Obviously some units are better for base defense, others are preferable for AI events, and others are probably better suited to attacking bases. We expect player favorites to emerge.

When one unit is the most common by a disproportionate amount, or when a unit barely makes a blip in the stats, we try to adjust things to give players incentive to adopt and deploy more variety. Sometimes, we discover that the popularity was due to a bug. For example, the Elite AH-64 was stunning aircraft a while ago, but was only intended to stun turrets. Other times, it is far more powerful than any other unit of its type, as it was when the Elite TOS-1A outclassed all other long-range ground attacks. We sometimes have to adjust the popular unit, but we normally don’t want to completely remove something the players are enjoying. Because of this preference, we usually buff other units rather than directly nerf a unit.

The Elite Stinger Gunner was chosen for a major refit because it was both very rare in deployments and was also originally designed as a direct counter to helicopters. The Elite AH-64 happened to be a disproportionately popular unit, with well over half of all unit deployments being Elite AH-64s. We balanced the new Elite Stinger Gunner stats to make it so that it could not kill an Elite AH-64 of equal upgrade level in one shot, but could be killed by the Elite AH-64 quite easily. This meant that massed Elite Stingers would win against lone Elite Apaches, but some clever maneuvering with Elite Apaches would keep winning.

New Elite Stinger Gunner Stats

There were two problems with this. First, the Elite Stinger Gunner’s unlock requirements were balanced for a pre-Hardware era. It is much faster to unlock an Elite Stinger Gunner to maximum level than an Elite Apache, so the average encounter was usually between higher level Elite Stingers and lower level Elite Apaches. The second is that there were far more Elite Stinger Gunners on AI single player bases and AI multiplayer map bases than we realized.

We debated making an AI-only “classic” Elite Stinger while giving the players the new Elite Stinger, or swapping all Elite Stingers on AI bases for basic Stingers, which are closer in stats to the old Elite Stinger. We chose the latter option so we could get it to players faster, but the idea of “Mercenary” units with legacy stats going into AI bases is something we’re strongly considering for future adjustments.

Moving forward, we’re going to try to keep players in the loop on planned changes to existing units, especially when they affect event bases.

During the week that the TOC12 patch enables new Maintenance Bay and Motor Pool levels (coming soon!), we’ll be updating the Elite BDRM-3. Our analysis shows that it is the least used elite vehicle, and multiple players have requested an update. We’re hoping to make it more in line with the Elite Stryker, except that it will deal less damage per shot and focus more on spreading damage around with its AoE attack. I’d like to make the fire damage it causes weaken a target against long-ranged attack, so it would make sense to send a BDRM-3 “shock team” in ahead of an artillery barrage. Since there are a total of 453 Elite BRDM-3s spread across all of the event bases, this is probably a good candidate to test the “Mercenary” concept so that AI base difficulty doesn’t change. Ideally, you’d see the AIs with the current version of the Elite BDRM-3, only renamed “Mercenary BDRM-3”, while players would get the updated stats version.

Short version: Expect the unit to be much harder to kill and to debuff enemy defenses, but not be a very long-ranged unit. Full details will be in the eventual patch notes.

During the week that the TOC12 patch enables new Maintenance Hangar and Airfield levels (coming after the Maintenance Bay and Motor Pool updates), we’ll be updating the Elite AH-1. Our analysis shows that it is the least used helicopter. It has been difficult to find a niche for this unit, so I’m thinking that it will play “overwatch” against incoming anti-aircraft fire. Think of the anti-missile stat on some buildings, except it only affects ground to air missiles instead of air to ground missiles. Since only the Stinger, Elite Stinger, and Elite Nimr use ground to air missiles (all other Anti-Air is bullet-based), the Elite AH-1 will also have a defense boost similar to the Elite MQ8B’s offense boost.  Deploying an Elite AH-1 with your group should be an interesting option with these changes. It won’t be the most powerful unit around, but it will increase the survivability of others.

Short version: Expect the unit to become harder to kill and to buff friendly air units against anti-air attacks.

Discord Dev Tracker Recap

It was a busy week in Discord. Here’s the recap of the dev-tracker channel:

  • Nirgal kept us updated on work done on two highly-requested UI features, the ability to view building stats while upgrading, and the ability to have buildings that require zero build time to bypass the building queue. Both patches were completed and sent to the rest of the dev team for review.

Stay up to date every day on what’s being developed on the dev-tracker channel here.

Looking for an update on where the Dev Team currently stands regarding various recent community suggestions? Check out our “Voice of the Commander” trackers here:

Like what you see in this Dev Blog, or have suggestions on things you’d like to see addressed in our “Voice of the Commander” trackers? Let us know over on our Thunder Run Discord Server!


Battlehouse Dev Blog, Issue #8: Thunder Run and Days of Valor Updates

📢 Attention Thunder Run and Days of Valor Commanders:

Welcome to the 8th installment of the Battlehouse Dev Blog, a place where fans of all Battlehouse games can enjoy regular behind the scenes peaks into the minds of Battlehouse Developers. Without further adieu, here’s bh-nirgal:

Thunder Run and Days of Valor Developments

There was a lot of active discussion on Discord over the weekend about our plans to “squash” some of the development time for things in the game. I first mentioned this in the inaugural blog post back in September. Instead of a link, here’s the original text:

  • “The third project, slated for an uncertain future date, is a rebalancing of the TOC tiers. This is one of the less-defined plans, and player feedback is highly encouraged. Ideally, I’d like to see the average player base level increase so that the top-tier players have worthwhile opponents to fight and the average player can hold their own. This would involve reducing research and building times for lower building levels and lower tech levels, and would involve reducing prices for older blueprints (or removing them altogether for some lower turret levels).”

Some veteran players expressed concern about the impact on the game, especially if it means that alt accounts can get powered up too quickly.

These are some fair concerns. It probably would be disruptive to significantly lower the time needed to research offensive technologies by too much.

We’re still a ways out from the rebalancing of lower content tiers, but it is probably best to focus on infrastructure, such as building upgrade times and costs, rather than on force projection, such as unit research and build times.

The one category that this probably shouldn’t apply is what we internally call “core units”. These are the units that you do not need a blueprint to unlock: the Rifleman, Mortarman, Javelin Gunner, Sniper, HMMWV, M1064, Stryker, M109 Paladin, M2 Bradley, M1 Abrams, OH-58 Kiowa, AH-1 Cobra, and AH-64 Apache.

These are weaker units, but in some cases they take a significant amount of time and resources to unlock, to the point that only extreme completionists are bothering to do so for achievements. Given the wealth of premium content, we’ll probably need to spend some time making a few these less-used “core units” more accessible to players.

Discord Dev Tracker Recap

It was a busy week in Discord. Here’s the recap of the dev-tracker channel:

  • Nirgal kept us updated on work done on the L5 Leaders for TR and DV, and also mentioned that h’d started the next FS content tier.
  • Nirgal completed several bugfixes, which included some issues with the new TOC12 weapons, the C-RAM turret, and several AI maps
  • We got a sneak peek at some of the in-progress work on the L5 leaders.
  • Nirgal reported that the L5 leaders patch was done and being reviewed by the rest of the dev team prior to deployment, and announced the order of work on the next several projects.

Stay up to date every day on what’s being developed on the dev-tracker channel here.

Looking for an update on where the Dev Team currently stands regarding various recent community suggestions? Check out our “Voice of the Commander” trackers here:

Like what you see in this Dev Blog, or have suggestions on things you’d like to see addressed in our “Voice of the Commander” trackers? Let us know over on our Thunder Run Discord Server!


Battlehouse Dev Blog, Issue #7: Thunder Run and Days of Valor Updates

📢 Attention Thunder Run and Days of Valor Commanders:

Welcome to the 7th installment of the Battlehouse Dev Blog, a place where fans of all Battlehouse games can enjoy regular behind the scenes peaks into the minds of Battlehouse Developers. Last week, bh-nirgal provided some updates on current projects he’s working on for MF, WSE, TR, and DV and this week he’s diving deeper into some of the juicy details surrounding his TR and DV developments. So without further adieu, here’s bh-nirgal:

Thunder Run and Days of Valor Developments

The ability to move buildings while they are “busy” has been added to the engine. Both Thunder Run and Days of Valor players can move upgrading, crafting, or repairing buildings now. The next engine quality of life change will be to enable accessing building stats while the building is “busy”. This will take slightly longer, since it will affect more portions of the engine.

Many players have requested that Unit Equipment be broken up by unit type. A working prototype of this was developed over the weekend, and is being fine-tuned before release to Days of Valor and then Thunder Run.

Unit Equipment section in the ONP Store

Days of Valor and Thunder Run players may notice that Unit Blueprints and Elite Unit Blueprints are now split into Infantry, Vehicles, and Aircraft sub-sections. This will make it a little easier to get to some of the blueprints.

The Level 5 leaders, along with the alternative leader update system, is well underway. This will mostly affect how players buy leaders and how players upgrade leaders. The new L5 leaders will be stronger versions of the existing L4 leaders and will not introduce any new mechanics other than how you upgrade to get them.

Buying leaders: Right now, the store entries for each leader checks if you have any level of the leader, and whether you can still upgrade the leader. If so, it lets you buy another leader. Since we’re changing the crafting system, the main listing for leaders will let you buy a leader if you don’t have any level of the leader.
Old system: 1x L3 leader, 1x L2 leader = can buy another L1 leader
New system: 1x L3 leader = cannot buy another leader

Upgrading leaders: The upgrade menu in the Leader Barracks now has three “recipes” for upgrading each leader to each level from 2 through 4.

  • There’s a legacy recipe that you’ll never see. This will keep any upgrades in process when we deploy the patch from disappearing.
  • There’s a “merge” recipe, which normally doesn’t show. This works the same way as you’re used to. If you have two leaders of the same level, this recipe will show up so you can upgrade them. If you only have one leader, it won’t show up.
  • There’s a “promote” recipe, which displays if the “merge” recipe doesn’t display. The engine seamlessly switches between the two. A “promotion” recipe requires a leader and “Promotion Orders”, an item you can acquire in the store. There are four levels of Promotion Order. A promotion order is more expensive than a leader, but the Hardware cost and time required to Promote is significantly less than combining multiple leaders.

The upgrade times and costs have been changed. To determine the new costs and times, I added the upgrade time and upgrade cost for each level, divided it by the number of recipes, and rounded it down. This means that individual leaders might take longer and cost more, but taken as a whole L2, L3, and L4 all take less time and cost less.

To try to bring some balance the greater number of upgrades required under the old system, it takes twice as long to do a promotion upgrade as a merge upgrade. Bear in mind, you have to craft L1 to L2 four times and L2 to L3 twice to get to L4, so there is a time savings in the L1 to L2 stage.

Buying Promotion Orders: The Promotion Order items will appear before the Alpha Team in the leaders section of the store. If you don’t like the new system, you’re in luck! The old store listings will be in a sub-section of the Promotion Order.  You can still buy all 8 level 1 leaders required to upgrade a leader to L4, or you can buy the 1 leader and 4 Promotion Orders required to upgrade. It’s your choice.

L5 Leaders only support the new Promotion Order method of upgrading. You will not be combining two L4 Leaders.

Looking for an update on where the Dev Team currently stands regarding various recent community suggestions? Check out our new “Voice of the Commander” tracker here: Thunder Run Voice of the Commander: Declassified.

Like what you see in this Dev Blog, or have suggestions on things you’d like to see addressed in our “Voice of the Commander” trackers? Let us know over on our Thunder Run Discord Server!


Battlehouse Dev Blog, Issue #6: War Star Empire, Mars Frontier, Thunder Run, and Days of Valor Updates

📢 Attention War Star Empire, Mars Frontier, Thunder Run, and Days of Valor Commanders:

Welcome to the 6th installment of the Battlehouse Dev Blog, a place where fans of all Battlehouse games can enjoy regular behind the scenes peaks into the minds of Battlehouse Developers. Last week, bh-nirgal took a deep dive into some of the current projects he’s working on for Battlefront Mars, and this week he’s providing us all some updates on his War Star Empire, Mars Frontier, Thunder Run, and Days of Valor projects. So without further adieu, here’s bh-nirgal:

War Star Empire and Mars Frontier Developments

War Star Empire has received a lot of dev cycles over the past year, thanks mostly to the presence of Promethium in the game. The three currencies allowed a 1 to 1 conversion and reskin of the turret system in Thunder Run, Days of Valor and Firestrike. I have a few minor changes in the pipeline, but I want to give players time to finish off the Central Computer L8 tier of content.  I do have some questions for players:

  • Would you prefer more levels of existing units, elite versions of existing units, both, or neither?
  • Would you like more defenses like mines, or no?
  • Would you like to be able to swap out the security teams on your buildings with ones made up of different units?

Mars Frontier is our quietest group of fans. Other than making an Opportunity Rover building security team add-on in memorial to our little rover friend, I haven’t spent much time working on Mars Frontier, and I’ve never received any requests or feedback from the player base. Is there anything you all would like to see, or are you pretty happy right now?

Thunder Run and Days of Valor Developments

Days of Valor has had the economy portion of the TOC12 patch for two weeks, and will get the Infantry patch tomorrow. Thunder Run is getting the economy portion of the TOC12 patch tomorrow. Portions of this patch will automatically unlock through January.

Now that this project has shipped, I’ll be tackling a major redesign of the introduction tutorial and rebalance of lower levels of content. There are two versions of the new player tutorial being tested in Days of Valor. We try to test and fine-tune things like these to see if we can figure out what will acquire and retain more new players. Based on the numbers in Days of Valor, we’ll either incorporate the new tutorial into Thunder Run as-is, or make tweaks to both the Days of Valor and Thunder Run versions. Once this is ready, we’ll be launching some new ad campaigns. I hope this will answer some of the good player questions we had on what we’re doing to grow the game.

While this is going on, I am working on some small UI changes and improvements. I’m testing the ability to move buildings that are being constructed, repaired, or are crafting in Days of Valor. Its release to the other games is pending.

I added in the ability to toggle the advisor and opponent AI portraits. It was deployed to Days of Valor for testing on October 26, and will be added to Thunder Run on October 31.

Looking for an update on where the Dev Team currently stands regarding various recent community suggestions? Check out our new “Voice of the Commander” trackers below:

Like what you see in this Dev Blog, or have suggestions on things you’d like to see addressed in our “Voice of the Commander” trackers? Let us know over on our Thunder Run Discord Server!


Battlehouse Dev Blog, Issue #5: Battlefront Mars Developments

📢 Attention Battlefront Mars Commanders:

Welcome to the 5th installment of the Battlehouse Dev Blog, a place where fans of all Battlehouse games can enjoy regular behind the scenes peaks into the minds of Battlehouse Developers. Last week, bh-nirgal took a deep dive into some of the current projects he’s working on for Firestrike, and this week he’s giving Battlefront Mars some love. So without further adieu, here’s bh-nirgal:

Battlefront Mars Developments

Battlefront Mars has been a “problem child” behind the scenes here at Battlehouse, but those problems led to improvements in all of the games.

We had a dedicated hacker who kept making alt accounts in order to destroy rivals of his clan using a weapons range hack. Our hacking detection system detected each of these, but required an admin to pull the trigger on a ban. On the plus side, this helped us refine and improve our alt detection systems and the hacker eventually exposed his main accounts and received a ban on those accounts as well. Eventually, we implemented criteria the hacking detection system is allowed to use to ban an account without admin intervention. Admins still review any automatic bans, but this allowed our systems to stop the damage caused by an unleashed hacker destroying other players when an admin wasn’t available to monitor the servers live.

The next round of troubles came from speed hackers. The CS team and I were both under the impression that our hacking systems could detect and defeat speed hacks. Upon further review, we found that previous members of the dev team had deployed our speed hack countermeasures only to Thunder Run. After a round of tests in Battlefront Mars, this got deployed to all of our games.

That covers the recent history for Battlefront Mars. What’s next for this game?

Currently, whenever I have a spare dev cycle, I work on porting the turret mounting system currently in all of the modern military games and in War Star Empire. This is taking longer in Battlefront Mars because unlike the other games, it only has two resources instead of three. With no Prometheum in the game, I can’t simply port over the turrets from War Star Empire.

When a turret converts, it also has to change a lot of the player’s game file under the hood. In the modern military games and in War Star Empire this only needs to account for ten levels of three turrets, but in Battlefront Mars there are twenty-eight levels. This means a lot more values to manually account for.

It isn’t an unsurmountable project, it just needs more time. I’m hoping to deliver a converted turret system by the end of the first quarter of 2020, at which point I’ll start enabling new levels for content already in the game.

Like what you see in this Dev Blog, or have suggestions on things you’d like to see Nirgal talk about in the future? Let us know over on our Thunder Run Discord Server (for Thunder Run players), or on Clan HQ (for all other games). See you all next week!


Battlehouse Dev Blog, Issue #4: Firestrike Developments

📢 Attention Firestrike Commanders:

Welcome to the 4th installment of the Battlehouse Dev Blog, a place where fans of all Battlehouse games can enjoy regular behind the scenes peaks into the minds of Battlehouse Developers. Last week, bh-nirgal took a deep dive into some of the current projects he’s working on for Thunder Run and Days of Valor, and this week he’s giving Firestrike some love. So without further adieu, here’s bh-nirgal:

Firestrike Developments

Firestrike is the first Battlehouse game I played, and the last one to be moved into my area of responsibility. Weird, huh?

Firestrike is one of the more difficult titles to develop. The other games are all set by hand. A Rifleman in TR and DV has 15 levels manually set by the developer. Hit points, damage, movement speed, and so on are chosen by whichever developer worked on the unit. Individual levels can be adjusted. This can lead to poorly balanced units. Firestrike was developed on an automatically balancing algorithm. The downside to this algorithm is that concepts that weren’t in the original design are hard to add in without breaking everything else. Firestrike’s revenue is also a lot lower than other games. Firestrike makes about as much in a month as Thunder Run makes on a Saturday.

To justify the development resources to upper management, I proposed that Firestrike get to test new concepts before they go to other games. This meant that I had to get some new tech working in Firestrike. Landmines had to go in first so that I could (later on) add new types of landmines. The armed TOC was the first example of a new gameplay mechanism that Firestrike got first.

The next steps for Firestrike will be to add a new tier and to aid lower level players in levelling up.

The Vault, a building present in Thunder Run and Days of Valor, will be added in to help new players avoid a total disaster when attacked by higher level players. Ideally, a player should be able to retain enough resources to fully repair their base and army and to complete at least one new building level or new technology research, regardless of how many times they were attacked while logged off. Player input is welcome and requested for several topics:

  • Which would you prefer, many upgrade levels per tier, or one upgrade per tier? Assume the resources and costs would be the same regardless.

Tier 16 will add more levels to all of the defensive technologies, more building levels, and four new units. What are those units, though? Player input is key here! As veteran players know, each tier gets an Infantry unit, an Armor unit, and an Aircraft unit. These are balanced by the algorithm, so the only real choice at play is the art assets to use. Anything that is currently in TR and DV is available. What would you, the players, like to see as the Tier 16 units?

Tiers can also receive a “special” unit of any type. Tier 16 is going to receive the UH-60 Blackhawk as a “special” unit. It will most likely not be deployed in the initial Tier 16 patch, because it will require an engine change. More details will be disclosed in a future blog post, but I will disclose Firestrike will get to try out a new mechanic with their implementation of the UH-60 before any of the other games.

Like what you see in this Dev Blog, or have suggestions on things you’d like to see Nirgal talk about in the future? Let us know over on our Thunder Run Discord Server (for Thunder Run players), or on Clan HQ (for all other games). See you all next week!


Battlehouse Dev Blog, Issue #3: Thunder Run/Days of Valor Developments

📢 Attention Thunder Run and Days of Valor Commanders:

Welcome to the 3rd installment of the Battlehouse Dev Blog, a place where fans of all Battlehouse games can enjoy regular behind the scenes peaks into the minds of Battlehouse Developers. This week bh-nirgal will be diving deep into three active projects he’s currently working for Thunder Run and Days of Valor. So without further adieu, here’s bh-nirgal:

Thunder Run/Days of Valor Developments

There are three major projects underway for our flagship game and its sister game.

The first project, slated for release in Q4 2019, is the TOC12 tier. The Tactical Operations Center will be one of the new armed buildings. Starting at level 12, players can mount special turrets on the roof of the TOC. The turret designs currently in testing are built on the concept of the Long Range Acoustic Device (LRAD), meant to disorient and debuff incoming troops while doing little damage. It will have a much greater range than other turrets. For players who prefer a damage-dealer, the TOC will also have its own version of the High Energy Laser (HEL). Unlike turret HELs, the TOC HEL can target ground and air targets, at the cost of somewhat decreased damage. As part of this update, all mobile units will have their level caps raised to 16.

The second project, which should follow quickly on the heels of TOC12, is an overhaul of the Vault building. Every TOC level will get 2 vault levels. At the second level per tier, the vault will store enough hardware to be able to repair the base itself and the most expensive possible combination of Base Defenders units. The first level will be halfway between the old cap and the new cap. So let’s throw out some wildly inaccurate numbers and say it costs 300k Hardware to fully repair a TOC8 base and the best (or at least most hardware-expensive) army units in the game. If you have a level 16 Vault, you have that much saved from attackers. You can immediately start repairing. You can’t necessarily repair your field batts or protect what you have saved for research, but you can get your base back in business. 

The third project, slated for an uncertain future date, is a rebalancing of the TOC tiers. This is one of the less-defined plans, and player feedback is highly encouraged. Ideally, I’d like to see the average player base level increase so that the top-tier players have worthwhile opponents to fight and the average player can hold their own. This would involve reducing research and building times for lower building levels and lower tech levels, and would involve reducing prices for older blueprints (or removing them altogether for some lower turret levels).

There’s some delicate terrain to navigate here. The game lives or dies based on players who pay to play. We cannot change that. So long as internet infrastructure costs money and so long as we have to pay our rent and pay to eat, we can’t make an entirely free game. Many of the players who pay to play are touchy about other players getting for free what they paid for.

I’d like to come up with a compromise. My plan is to divide the player base into a rookie tier, a regular tier, a veteran tier, and an elite tier, based on unlocked content.

The Elite Tier would always be the newest level of content, in this case all the stuff requiring TOC level 12. It doesn’t change until the theoretical release of TOC13, and is intended to give non-paying players at least six months of construction and research projects to complete. There are many players who won’t play if there’s nothing new to acquire, so the top tier needs to cater to this type of motivation.

The Veteran Tier is the last two levels of content, the stuff requiring TOC levels 10 and 11. It gets a slight nerf in ONP/hardware prices, research times, and build times, but no more than a 5% cut. I’d like to see players go from Veteran to Elite in half a year or less.

The Regular Tier is everything from TOC level 6 through TOC level 9. This gets a decent nerf in prices, research times, and build times, but never more than a 20% cut. I’d like to see players go from Regular to Veteran in a quarter of a year or less.

The Rookie Tier is everything at or below TOC level 5. This gets a generous nerf in prices, research times, and build times, up to a 50% cut. I’d like to see new players go from Rookie to Regular in less than a month. Sprinkled into the nerfs would be some removals of blueprint requirements.

How would it make you, the veteran players, feel if newcomers got for free some of the things you worked long and hard to acquire? Does the thought of new faces to fight and befriend make it worth it, or does it bother you to see cheaper availability?  Please send me your thoughts.

Like what you see in this Dev Blog, or have suggestions on things you’d like to see Nirgal talk about in the future? Let us know over on our Thunder Run Discord Server (for Thunder Run players), or on Clan HQ (for all other games). See you all next week!


Battlehouse Dev Blog, Issue #2: Discord AMA Recap

📢 Attention Thunder Run Commanders:

Welcome back to the 2nd installment of the Battlehouse Dev Blog, a place where fans of all Battlehouse games can enjoy regular behind the scenes peaks into the minds of Battlehouse Developers. This week bh-nirgal will be recapping our recent 2nd ever Thunder Run Discord Dev AMA, as well as expanding deeper into a few of the great questions that were brought up. So without further adieu, here’s bh-nirgal:

Discord AMA Recap

Our Dev Talk/AMA session from October 4 was a ton of fun. I (Nirgal) greatly appreciated your comments and questions. We’ll be sure to do this again soon.

#1 – Mystic Puzzle asked: Are we going to get Poacher and Virus single player campaigns back anytime soon?

  • Our response: This has been on the dev wishlist for months now. It dropped behind some engine changes and major content patches in multiple games, but I do believe we’ll be able to devote some time to bringing back these events. They most likely won’t be in the regular ONP schedule, but it wouldn’t be out of the question to see them in the Hardware week line-up.
  • More thoughts: I know a lot of players want to obtain the achievements related to these events, so when we get to the point where we can launch these, we’ll be sure to keep the achievements enabled. This is now officially a work in progress. Kim will make the first return, but I won’t have an ETA until I finish dusting off the old maps and deciding where to insert them into the schedule.

#2 – MamaSandy asked: Nirgal did I read your blog right that to have interactive batt fight need a different platform?

  • Our response: @MamaSandy, the engine doesn’t currently support truly head-to-head combat with two human controllers in game. The closest we have is a click-race to be the human in charge of a battalion vs battalion fight. That’s led to a lot of frustration and complaints from various groups of players who want the game to work in different ways. My blog entry on it was brainstorming/idle chat about possible changes to the system. Nothing is happening right now. If you liked any of the ideas (or really hated them), we’d love to hear.

#3 – mehedi kaisar asked: whats your plan about bringing new players i tr ? all i see is if there anynew member of tr its a alt and its really make me sad

  • Our response: Different members of the team focus on different parts of this.  Bh-nirgal and bh-cameron are focusing on making the tutorial process easier, we’re tailoring ad campaigns, and streamlining the upgrade process to make it easier for new players to survive and feel like there’s a reason to come back and play. There’s a lot about this in the next dev blog post, but the bottom line is that we’re working on making low level content easier and with a gentler learning curve to bring them into the war! Best thing you can do to help is let your friends know about Thunder Run! 🙂

#4 – Steelrain asked: Do you think we’ll ever see Level 5 leaders?

  • Our response: Absolutely, beyond a doubt.  You can also expect to NOT have to build another level 4 leader to get your level 5 leader. You will just need your current level 4 leader and one other thing that you’ll be able to get pretty easily.  Expect it in the upcoming content patches.
  • More details: You’ll still be combining your L4 leader with something to promote the leader to L5. It will most likely be a Promotion Papers, an item that you buy from the Leaders section of the store for slightly more than the cost of an L1 leader.

#5 – mehedi kaisar asked: the recent changes of advanced air units making all other units look poor …. so i feel there is an imbalance between unit right now … do you guys have any idea to make the balance between ground air and infantry?

  • Our response: Good question.  We did just release a major boost to the Elite Machine Gunner, though it is a secondary air defense unit. We also released three new levels for the Elite Rifleman.  That being said, the Stingers might need some love, as well as some of the anti-air turrets. We’ll have to run through a few battles and try some different mixes. We don’t want the E-Apache turning into the E-TOS of the skies…
  • More thoughts: Expect some love for the Elite Gaz Tigr and Elite Nimr soon.

#6 – Steelrain asked: When will we see an elite blackhawk that can carry elite riflemen?

  • Our response: We could do it within the month if you’d be happy with it suiciding the way the UH-60 does, but I’m planning to devote some dev cycles to a non-suicidal Elite Blackhawk and a non-suicidal revision to the UH-60.  The engine currently only supports releasing units if the “mother” unit dies. I think the tech investment is worthwhile, so I’m planning to get that done first.

#7 – mehedi kaisar asked: a boost for c ram ?

  • Our response: Probably.
  • More thoughts: Definitely.

#8 – Mystic Puzzle asked: Regarding the Vault, the amount protected seems way too low and the costs are way too high. I think it should be like a certain percentage protected everytime the Vault gets upgraded. Say, for max level should be 30% of fuel and supply resources protected and 50% hardware protected. As hardware is just extremely hard to loot so much and even 1 attack can just deplete all that hard-earned hardware to go poof, as why 50% seems reasonable, while the others a lower percentage.

  • Our response: Here’s what I posted on ClanHQ regarding the vault.  Bear in mind, these are general concepts, not concrete figures:
    • Every TOC level will get 2 vault levels (24 total after the upcoming TOC12 patch). At the second level per tier, the vault will store enough hardware to be able to repair the base itself and the most expensive Base Defenders units. The first level will be halfway between the old cap and the new cap. So let’s throw out some wildly inaccurate numbers and it costs 300k Hardware to fully repair a TOC8 base and the best (or at least most hardware-expensive) army units in the game. If you have a level 16 Vault, you have that much saved from attackers. You can immediately start repairing. You can’t necessarily repair your field batts or protect what you have saved for research, but you can get your base back in business. Ignore the current costs of the vault, I plan on slashing them.

#9 – WarlordKirk asked: Have you guys thought about making a map for level 39 and below only? To keep new players from getting discouraged by the big bases being bullies?

  • Our response: Thought about it, yes.  Come to an accord as a team, no.  There are competing schools of thought on how to give newcomers the genuine Thunder Run experience or to keep them on a guided and safe path to learn the ropes.  We’ll be discussing this further during our new player experience overhaul, which we’ll be working on as soon as the next major content patch is out the door.
  • More details: Cameron and Nirgal have in-depth discussion of this as an agenda item for the newbie experience overhaul. If it gets implemented, you all will know. If it doesn’t, we’ll at least acknowledge it and go over our reasons why not when the newbie overhaul is complete.

#10 – MamaSandy asked: is there any more consideration being given to be able to gift warehouse items to other clan players?

  • Our response: Sure, which items in particular are you interested in gifting?
  • More thoughts: (we’d be happy to receive some suggestions here. If there was a follow-up question during the dev talk, I missed it. Sorry!)

#11 – Mehedi kaisar asked: as per now vault is auto but is there any possibility it can be manual like we can save a certain amount of resource when our depots are full and when we used the res of depots we collect from vault ?

  • Our response: The vault doesn’t really work like that. It’s just another storage slot that happens to be invulnerable. The engine doesn’t support anything like what you’re describing. How often do you think a feature like this would be useful? It would be a pretty major investment of time to add a feature like this.

#12 – Mystic Puzzle asked: For the Vault, how about if we have the ability to choose resources of our choice. To be honest, rather have all hardware protected than the other 2. If possible, can we have the ability to do that?

  • Our response: Hmm, that’s an interesting idea. The engine could conceivably support this, but only in a very clunky way. We’d have to make a Supply Vault, Fuel Vault, and Hardware Vault building, each of which must be deconstructed before building one of the others. Or we could make an equip slot that changes which one it stores, but that would eat warehouse space. Making it not require a bunch of clicks would mean engine changes. 🙁 I’ll definitely think about it, but I think you all will like the planned Vault changes. I’m afraid we can’t make Hardware risk-free, but we will be making a lot of defenses easier to acquire.

#13 – Yooshijin asked: any update on an elite humvee?

  • Our response: Eventually. We’re working our way down the list. Any thoughts on what sort of loadout you’d like to see? Any special abilities?
  • More thoughts: This might be an ideal platform for the engine changes that will allow for two automatic weapons. Right now, the engine supports one automatic weapon controlled by the AI and one special weapon controlled by the ‘e’ key. What would you all think of an Elite Humvee supporting a machine gun for ground troops and a Stinger launcher for helicopters? This would mean it wouldn’t be out soon, as the code changes would be significant.

#14 – Bastian asked: How about a bounty system where players can take out contracts on others?

  • Our response: No engine support… but I love the idea. We’ve discussed internally a “black ops” mission type where you can hide your identity when taking a bounty, but the person who posted the bounty is disclosed… unless you fail the attack! Then you’re exposed! No timeline for such a feature, but I definitely want to tackle it.

#15 – mehedi kaisar asked: how can we edit our base setup more easily ?

  • Our response: A base editor program has been on my features wishlist since I started working here. I can’t offer a timeline for it, but I promise that I haven’t forgotten about it. My blueprint includes stored layouts so you’d be able to swap them around.

#16 – MamaSandy: anything in the works to maybe “beautify” the base ei roads and or trees? be nice to try and hide things a little.

  • Our response: Nothing in the works, no. I should add this to the requirements list for the eventual base editor.

#17 – Steelrain asked: Are players still getting all unit range boosts or have those gone away?  I haven’t seen one in a long time.

  • Our response: The drop rates for the strong all-unit range boosts were nerfed a while back because, based on a survey of battle replays we looked at, they were un-balancing combat quite badly (making whole swathes of units/turrets obsolete due to range limitations).

#18 – Shininson asked: are there any new plans for actual new turret heads aka tesla coils or something.. or long range rocket artilary like v2 rocket in original c&c or since we have air that stuns air … maybe vehicles that stun vehicles lol

  • Our response: The Long Range Acoustic Device is our first new weapon type. A nasty sonic weapon (which is based on real tech) disorients, slows, and debuffs enemy units. Vehicles that stun vehicles… maybe that can be the Elite HMMWV’s speciality.

#19 – Raider150 asked: when toc12 coming?

  • Our response: Very, very soon. I am working on two art assets, then we should be ready to launch.
  • More details: Days of Valor should see the first part of the release on October 17. This is a multi-stage release, so expect new content to activate every two weeks from release through January.

#20 – Achmed asked: When bats are traveling on ma why can’t we call to a new location before bat arrives at first waypoint?

  • Our response: You can cancel bat movement and re-direct after the cancel. But the bat still has to “snap” to the next hex on its path first. This is because the server tracks bat movement hex-by-hex, so it isn’t possible to change anything when a bat is between hexes. It’s sort of in a “ghost” state at that point.

#21 – Upendra asked: Why there is limit of 5 on unit boosts in each slot in Warehouse? and the shields only one? can we make it as equal to the Missiles?

  • Our response: Some of it is, admittedly, arbitrary. I’ve seen in many games that players can succumb to “hoard it for the final boss” syndrome, and limiting space can often serve a good purpose in game design. Scarcity keeps a player focused on making choices. If you can have everything, you’re not really strategizing. One solution I’ve thought of is to increase the stack, but make items expire, perhaps after a month of sitting in storage. Even military hardware has a shelf life.
  • More details: If we implemented such a solution, existing items would be grandfathered to keep their existing stack limits and lack of expiration date.

#22 – Mystic Puzzle asked: PvP suggestion: If a player fails to do at least 50% base damage why can’t they lose PvP and the defending base gets the points instead? (600 maps and this also includes all other BH games)

  • Our response: This would make it too easy to farm up PvP points by setting up fake battles against allies/alts. Maybe if we limited PvP point gain/loss only to specific, server-chosen enemies. But I suspect that would be an unpopular option.

#23 – GrandadN asked: will there be more control over players using alts on non alt maps

  • Our response: We’re continuing to improve alt detection systems. Quite a few alts get moved or banned automatically on a daily basis. If you notice alts on maps where they don’t belong, please send us a report using the in-game Contact Support button so we can investigate.

#24 – Jhun asked: Sirs. any chance of an anti-missiles troops?

  • Our response: I’m considering some art assets for our future units, and the Patriot missile system is among what I’d like to add.  It’d definitely have anti-missile.

#25 – Cyberton asked: Can we get 10gold for watching an ad?

  • Our response: It’s worth us discussing internally. Thanks for the suggestion.

Two general threads that did not get addressed during the chat were “ghost battalions” (a term players use for battalions with troops at a low percentage of their total HP) and “hardware stealing” (regional map AI bases with their Hardware Depots destroyed while leaving the rest of the base intact). I’ll be giving each of these a blog entry later down the road.

Like what you see in this Dev Blog, or have suggestions on things you’d like to see Nirgal talk about in the future? Let us know over on our Thunder Run Discord Server (for Thunder Run players), or on Clan HQ (for all other games). See you all next week!


Battlehouse Dev Blog, Issue #1: About Your Developer, Engine Developments

Welcome to our first installment of the Battlehouse Dev Blog, a place where fans of all Battlehouse games (Thunder Run / Days of Valor / Mars Frontier / War Star Empire / Battlefront Mars / Firestrike) can enjoy regular behind the scenes peaks into the mind of at least one Battlehouse Developer. This week we’ll be getting to know our Developer a little bit better, after which point he’ll dive deep into some detailed Engine Development updates. So without further adieu, everyone meet bh-nirgal:

About Your Developer

Hello, all!  Your blogging developer this month will be Nirgal. My professional background is in cybercrime investigations and computer forensics. I served as a police detective for fourteen years prior to joining Battlehouse. Aside from my developer role, I also work as a computer forensic scientist and forensic software developer.

I joined Battlehouse in May of 2018 as a junior developer. My first project was the anti heavy armor mine. In September of 2018 I became the lead game developer. At that point, I mostly worked within the confines of existing engine features. I had prior experience as a Python developer, but no experience in JavaScript or HTML5, meaning I had little knowledge necessary to work on the browser engine. Thanks to constant immersion in the code and a passion for education, I’ve learned enough JavaScript to make adding features to the engine a regular part of my work. My responsibilities gradually morphed to the point where I’m now responsible for a lot of the game engine and server.

My goals for all of the games have been to improve the chances of defenders by increasing the variety and strength of base defenses, and to make new content for attackers more mechanically interesting to play.

In this blog, I’ll be discussing contents that are currently being developed and the reasoning behind the developments. I will also be discussing planned next steps that have a timeline, and discussing possible future development that has no set timeline. Reader feedback is strongly encouraged.

Engine Developments

Our HTML5-based browser client has been the focus of several recent developments that have affected most of the games. Most of the changes currently in development have been focused on how crafting and upgrading works “under the hood.”

Landmines, which are currently featured in Thunder Run, Days of Valor, Battlefront Mars, War Star Empire, and were most recently added to Firestrike, were a significant problem area for us. Many of the data objects in the game are able to define an item or unit at every level the item or unit has. For example, a level 1 Rifleman in TR or DV is the same data object as a Level 14 Rifleman. Landmines were unique because they required three separate data objects for each level of the landmine: one for the mine itself, one for the mine’s explosive, and one for the engine instructions on crafting and delivering the mines. In TR and DV, this meant that anti-infantry mines had 54 separate data objects. In Firestrike, three landmine types with 215 levels each meant that there were 1935 data objects in landmines. Each data object duplicated data needlessly, and was resulting in larger downloads.

This project was completed first for War Star Empire, and has since been deployed to all other games.

This migration process uncovered problems with how our battle log and battle replay system were designed, which will have to be addressed in a future engine update cycle. Our current plan is to leave the legacy data online until March of 2020, then deprecate battle replays that predate October 2019. If you have an iconic battle you’d like to save, be sure to record it with video software before it’s gone forever.

The second update involves armed buildings. For the longest time the only armed buildings have been landmines and turrets. Each of these use a special crafting interface that other portions of the game don’t need to use. I altered the turret crafting interface to support three other types of armed buildings. During this process, I came across a similar problem faced by landmines. Any turret that consumed power while crafting required a separate data object for each level of its crafting instructions and the turret itself. In Firestrike, the three turret types only required three data objects each, but in Thunder Run each turret required two objects per level, resulting in 56 separate objects per turret type.

Engine Future Plans:

There’s a laundry list of UI tweaks and bugfixes that need to be addressed, but the next major feature change is the grid crafting system. Currently, only landmines use the crafting grid. I’d like to make it so players can craft ambush point equips on a grid, and building security nodes on a grid. We added the inventory tab system as a bandage to the warehouse size issues, but I’m hoping being able to craft what goes into a slot will help players who currently use these features. Currently, interface limitations mean the grid sizes are hard capped at 28 slots. I intend to add support for scroll buttons, allowing us to raise the cap. To be clear, mines, ambushes, and security nodes would all have their own grids. Mines need to be rebuilt, so a “rebuild all” button will be added both to the mine crafting interface and to the base repair interface. Once this is done, I hope to add these features to games other than Thunder Run and Days of Valor.

That Laundry List of Bugs:

Mine crafting queue freezing: This looks like something related to how the building repair code interacts with the crafting queue. It will take some research.

Lack of Hardware listing in the repair UI: This is now fixed!

Battle Replays: A lot of data doesn’t get snapshotted properly and becomes buggy when the state of the game changes. The whole system needs an overhaul to take better data snapshots and not rely on the current gamedata. We will probably have to automatically sunset replays older than one month to keep the replay data storage from becoming unmanageable.

That Laundry List of UI Changes:

Allow access to building leaders and stats while the building is building/crafting/repairing: This should be doable. There’s some logic that decides which buttons to show for a building. There will need to be some additions to hide certain menu buttons once you’re viewing the building if it’s busy building/crafting/repairing.

Allow buildings to be moved while under construction: This shouldn’t be too hard, but there may be some surprises under the hood.

Allow buildings with an instant build to bypass the construction timer. This will require some significant logic restructuring to implement and will be a low priority.

Toggle enemy AI picture: I want to make it so you can show/hide the enemy AI at your leisure. It will still have to appear at the start of an event.

Toggle base advisor picture: I want to make it so you can show/hide your base advisor, though it will reappear during important announcements.

Show ONP as a resource: I plan to show it next to Hardware. Mirroring the count in the warehouse will be fairly simple. I will not be able to remove it from the warehouse inventory without a much more significant engine overhaul that would require changes to both the server and browser client.

Damage indicators: I intend to update the hovertext over UI damage indicators to show the modified DPS against a class of unit.

There are many other excellent suggestions on UI overhaul, but I’m not adding them right now. For one, I’m not a UI designer, so I’d probably botch it. For two, I don’t even have an inkling of the time investment necessary, so putting them up here as in the works would be disingenuous.

Vague Future Plans:

I want to overhaul the multiplayer map interactions. Accusations of cheating on the multiplayer make up a significant amount of our fan interactions and customer support tickets. Since actual player vs player is currently beyond our engine’s abilities (and may always be), I have come up with some theoretical changes that are in line with our player vs AI-owned-by-player model. None of these are in the pipeline or definitely happening, but player feedback is encouraged:

  • Make it so battalions can’t be attacked while a player is online, but also that the battalion can’t block a path while a player is online. In other words, no jailing, and no PvP between players online at the same time. This would probably be the simplest to implement, but also the worst idea.
  • Make it so battalions can be attacked and block while a player is online, but only if the player “garrisons” the battalion, causing the battalion to dig in at their current position. Turning off the “garrison” action takes half a minute of real time, but the battalion gets a defense boost while garrisoned. Garrisoning could happen automatically when logging out, or logged out battalions could still require manual garrisoning. Two options for how garrisoning could work:
    • Battalion deploys a few fixed defenses in the form of a small minefield and turret deployment which is generated on the fly and disappears when they de-garrison.
    • A defense and range boost is applied to a garrisoned battalion, which is turned off when they move. It also gets turned off if a lower-level player attacks a higher-level player’s garrisoned battalion (to discourage “jailing”).
  • Make it so battalion strength is boosted or nerfed based on relative power levels of the battalions, to a certain degree. If a squad of fully equipped L15 TOS-1As attacks a pair of L3 Riflemen, it’s going to be a massacre regardless, but if twelve L14 Riflemen attacked six L7 Riflemen, the stats might wind up being closer to twelve L14s vs nine L11s. This would be tricky since it would require comparison of stats on the fly. It might work better to calculate average range, total DPS capacity, and total HP, and boost the defender by 50% if their total capacity is less than 50% of that of the attacker. This would probably wind up being too finicky to turn into a workable idea, but I included it to share some of the places my brain goes.

And that’s about as deep as we’re going to go into the engine today, but check back at the same time next week for a more in depth dive into Thunder Run and Days of Valor, where Nirgal will give us behind the scenes insight into projects he’s currently working on, and how they fit into the bigger picture of the games.

Like what you see in this Dev Blog, or have suggestions on things you’d like to see Nirgal talk about in the future? Let us know over on our Thunder Run Discord Server (for Thunder Run players), or on Clan HQ (for all other games). See you all next week!