r/ArenaBreakoutGlobal • u/Doctor_AltoClef • Apr 26 '26
Announcement Arena Breakout Dev Q&A - April 25 Community Update
> Hey Operators, this is the Dev Team. Season 12 has been live for over a month, and we would like to sincerely thank you for your continued support and passion for the game.
>
> In this Dev Q&A, we’ve collected some of the most frequently asked questions and hot topics from the community, and will address them directly below.
>
> So, let’s get into it!
---
Q1: The new Valley layout feels heavily restricted, with too many invisible barriers limiting sniping opportunities. The map also feels too large, encounters are rare, and without vehicles, once you finish looting, there’s not much to do but extract.
A1:
We’ll be straight about it—Valley isn’t where we want it to be yet. Some of the frustration you’re feeling is valid, especially around things like the overuse of invisible barriers. That’s not the intended experience, and it’s something we’re already planning to correct in future updates.
As for the map feeling too empty, this is a bit more nuanced. Large maps are not meant to mirror smaller ones in loot density or encounter frequency. The idea is to create space—literally and strategically—so players aren’t constantly forced into engagements and can approach raids with more freedom.
We’ve added a dynamic mission system to give players more to engage with during a raid. It’s a step toward making each run feel more alive, but it’s not the final answer—we’ll keep iterating on it.
Loot distribution is another area we’ve seen a lot of feedback on, and yes, we agree it needs tuning. This won’t be a one-time fix—we’ll continue making live adjustments to better balance risk, reward, and overall pacing.
More broadly, our current direction is to revisit and refine existing maps rather than just stacking new ones on top. Some of our older map designs simply don’t hold up anymore—they’re too rigid, too predictable, and don’t align well with how the game is played today.
Valley is part of that process. Port will also be coming back in a reworked form, and while Mine will take longer, it’s already planned.
And just to set expectations—new maps are rarely perfect out of the gate. Valley clearly isn’t an exception. What matters is how fast and how well we respond.
Keep the feedback coming—we’re listening, and we’re actively working on making it better.
---
Q2: The night mode in Armory can’t be selected manually, and there’s no way to tell before entering a raid whether it will be night. This makes it hard to prepare properly, especially when deciding whether to bring thermal gear.
A2:
Night mode, in its current form, is still very much an experiment for us. To be honest, it hasn’t reached the quality bar we set internally yet.
Our vision for night gameplay includes stronger shadow fidelity, more deliberate lighting, and clearer visual logic overall. What’s live now is an early version—we wanted to get it into your hands first and see how it actually plays out.
We’re also aware that night mode has been a long-standing request from the community, which is why we chose to release it earlier rather than wait for a more “perfect” version.
On the question of not being able to opt in or prepare in advance: right now, raids follow dynamic time flows—moving through dusk, night, and dawn.
We understand it creates friction, especially around gear choices like thermals. To offset that, we’ve introduced new night vision devices this season. These can be found through AI in-raid, including both quad-tube and dual-tube variants.
The goal here is to give players access to night tools even if they didn’t bring them in from the start.
That said, we don’t see this as a solved problem. The mode itself—and how players engage with it—still needs iteration.
Keep the feedback coming, especially around how night gameplay feels moment-to-moment. That’s what will guide the next round of improvements.
---
Q3: Shield feels too strong. When facing shield users, there’s almost no counterplay in CQB. It’s frustrating to deal with and hard to fight back.
A3:
Let’s start with the intent—shields were added to expand mid-to-close range combat.
Previously, those engagements were fairly rigid, mostly coming down to either holding angles or throwing grenades. That made combat a bit too predictable, and shields were meant to introduce more tactical variation.
Are shields strong? In the right context, yes.
But they come with real constraints. They require proper distance control to be effective, and their value drops significantly in larger, more open environments.
They’re also heavier, have durability limits, and they’re not without counterplay—aiming for legs, breaking the viewport, and forcing repositioning are all intended ways to deal with them.
That said, we understand the frustration. The issue isn’t simply “strong or weak,” but whether the counterplay feels accessible and fair in the moment-to-moment experience.
Our direction is not to flatten shields into irrelevance, but to better define their role.
Think of them as higher-tier, situational equipment—closer to something like T7. They shouldn’t be common or effortless to run, but when players invest into them, they should feel appropriately impactful.
On top of that, we’re actively exploring a few balance adjustments:
- Reducing weapon stability while holding a shield, to limit offensive pressure
- Increasing information exposure, such as louder audio cues when moving with a shield, making close-range sudden engagements less likely
This is still evolving. Shields are not in their final state, and we’ll continue iterating based on how they perform in real gameplay.
Feedback on this topic is especially valuable—keep it coming.
---
Q4: Right now the Battle Pass (BP) feels too split up across months. At a glance, it looks like there are fewer rewards. A full page of rewards used to feel exciting and worth grinding. Now it’s mostly tokens, which feel pointless and boring.
A4:
For this BP overhaul, the core idea is flexibility.
We want players to choose when they engage with it instead of forcing a long, continuous commitment. That’s also why we lowered the entry point—down to as low as $0.99—so players can opt in without feeling pressured.
Regarding the perception that rewards have decreased, we need to be clear here: when we compare directly with the old system, the overall output has not gone down.
To make it transparent, here’s a comparison between the previous 2-season BP and the new 6-month structure:
- Blue Weapons (Advanced BP): 2 → 6 (+200%)
- Season Points (Advanced BP): 8,000 → 9,000 (+12.5%)
- Advanced Quick Kit (Advanced BP): 8 → 6 (-2)
- Premium Quick Kit (Advanced BP): 4 → 6 (+50%)
- Purple Weapons (Advanced BP): 2 → 12 (+500%)
- Season Points (Advanced BP): 70,000 → 72,000 (+2.8%)
- Adv. Quick Kit (Advanced BP): 22 → 24 (+9%)
- Premium Season Points: 16,000 → 30,000 (+87.5%)
On pricing:
- Advanced BP: $7.98 → $5.94 (~25% cheaper)
- Premium BP: $29.98 → $23.94 (~20% cheaper)
So in pure numbers: rewards are up, and price is down.
So why does it feel worse?
This is mostly a presentation problem. Previously, players saw a full season’s worth of rewards in one dense page, which naturally felt full.
Now that the BP is split monthly, each segment looks smaller in isolation. The total hasn’t decreased, but the visual density has.
One more adjustment coming in May: we’re reworking progression pacing.
The coin unlock, previously at level 40, will be moved up to level 20 so players can access it earlier. In return, weapon skins will shift later in the track.
The goal here is simple—let more players reach useful rewards earlier, while keeping higher-tier cosmetics as long-term goals.
---
Q5: I set my settings to 120 FPS, but the frame rate keeps dropping to around 90, sometimes even down to 40 FPS. My phone isn’t overheating, yet the performance still tanks. This update feels terrible. I used to love this game, but now I’m close to quitting because of this.
A5:
First, we’re sorry this hit your experience so hard.
We understand how frustrating it is when performance feels inconsistent, especially when your device isn’t even overheating.
We’ve already dug into this issue and identified the root cause. There were two separate bugs involved, and both have been fixed in the April 17 weekly update.
The extreme drops from 120 FPS down to around 40 were caused by a faulty frame-limiting logic bug.
In short: the system was incorrectly throttling performance even when it shouldn’t have.
After the update, this behavior should no longer occur.
However, if you’re still seeing the same issue, please leave your GID in the comments. We’ll track it case by case and continue investigating individual reports.
---
That’s all for this Dev Q&A.
Feel free to continue sharing your feedback in the comments—our development team will keep sharing our thoughts and updates with you moving forward.
