APC & Rapid Deployment Radio Bug Fix

Greetings Leaders,

We wanted to give an early heads up on a couple of things we’re fixing in DomiNations. Much like our 13.6 update, we have a litany of work we’re doing for 13.7 and beyond. Our next major update is looking to land in July, so no need to scramble! But there were a couple of bug fixes we wanted to make folks aware that we’re tackling.

APC & Rapid Deployment Radio

APC has seen a surge in popularity (AWESOME!), but when they’re equipped with the Rapid Deployment Radio at Level 20, things get a little too spicy (Not Awesome). The implementation of APCs has been a newer go-to tactic for many players, and we’ve loved seeing the community come together to build upon this effective strategy.

We love to watch the progress you all make with Troop compositions and strategies. The APC has spiked in victory rates, and at a glance, it wasn’t immediately clear as to what caused this spike that grew well beyond all of you simply optimizing your Artifacts and Munitions. After reviewing information from countless battles, we discovered that the Rapid Deployment Radio Munition had a bug that allowed the APC to spawn Troops beyond their spawn limit. This resulted in an overwhelming offense that defensive buildings stood almost no chance of stopping.

In update 13.7, the APC will not be changed directly; instead, it will correctly adhere to its Troop Limit, as intended, even when equipped with the Rapid Deployment Radio.

Counter Offensive & Machine Gun Towers

We’ve also been made aware of an issue impacting Machine Gun Towers and players who have Counter Offensive chapter 3 researched in their library. The bug restricts the Machine Gun Tower’s Suppression to a single Troop as opposed to every Troop within its area of effect.

We’re working to implement this fix, but it might not make our 13.7 update due to time constraints.

That’s all we have to share for today! We’re keeping an eye on the 13.6 release and noting the above-mentioned issues and the Bastion Slowdown not working in this release. We’ll be working diligently to get these fixes to you as soon as possible, just as diligently as you have been reporting them to our CS Team! We just ask for a bit of patience as we add these to our currently planned workload.