Last week, we dropped some tough news about ECS and Update 5. Your response? Surprisingly positive. You asked smart questions, gave thoughtful feedback, and kept the discussion productive.

To keep that momentum going, we opened a dedicated Discord channel for community questions. A lot of good ones came in, so we’re bringing some of the highlights here in a cleaned-up Q&A format. The answers come straight from Jacob, thour producer on Deep Rock Galactic: Survivor.

But first…

This one turned into a proper meaty patch. A big balance pass, more overclocks, and one of the most requested bug fixes finally landed. Here are the highlights:

• Save system overhaul - crashes and power outages should no longer wipe your progress. We’ve implemented a new multi-file system with more fail-safes.
  
• Loot crates from end-of-level elites - extra rewards from finishing strong!
  
• Dozens of overclock buffs and new overclocks added - some of the drone overclocks have been buffed by biblical proportions.
  
• Some specialist Gunner love - minigun should be easier to aim, and his passive now scales with upgrades.

• End-of-level Elites now drop loot crates, the faster you kill them, the better the reward.
  
• New Anomaly: Company Man - Just stick to your job and you’ll be alright.
  
• Vanilla Hazard 3 is open for business
  
• Save system overhaul:
  • New save system with rolling saves in 4 files.
    
  • Save files are new kept in a \Users\YourUser\AppData\LocalLow\Funday Games\DRG Survivor\steam\YourSteamID\ subfolder
    
  • Old saves should be automatically migrated to the new system. The old save file is not deleted.

• Fixed an issue where players could lose all their saved data if the computer lost power while playing
  
• Fixed an issue where the drop pod sometimes forced the player off the ramp when the timer hit 0
  
• Fixed a black screen issue that could sometimes occur when the dwarf auto-entered the drop pod
  
• Fixed an issue where clicking the weapons during drop pod interaction, could get you soft-locked in the weapon details screen
  
• Fixed a black screen issue that could occur if you leveled up while in the drop pod
  
• Fixed an issue where the input system would sometimes fire a submit event twice when using a controller. This may have been the cause of some messy UI screens and black screen issues
  
• Fixed an issue where HAZ5 achievements were not achievable. You will have to complete a new HAZ 5 run to get the achievement
  
• Maybe fixed an issue with the Axtender milestone (Axe in Face achievement) sometimes unlocking, even though the level was not cleared. Let us know if it still happens
  
• Fixed an issue where aborting a mission didn’t award progress, now it saves progress and goes to the end screen
  
• Fixed an issue where some mutators that should not be combined were combined, resulting in soft locks. (Looking at you Specialist and Just Pick One)
  
• Fixed an issue where the core pause screen could lose controller interaction when opening/closing/opening it fast
  
• Fixed an issue where loot crates from Huuli Hoarders could spawn off the map if the hoarder was knocked back
  
• Fixed an issue with Drones’ audio lingering
  
• Fixed an issue where the Storm E-Mag overclock would not count projectiles toward Weapon Specialist passive
  
• Fixed wonky d-pad navigation
  
• Fixed an issue where the Dreadnought’s ground spikes could kill ghosts. Totally not realistic
  
• Fixed an issue where the -15 accuracy on LMG Unstable OC Overload, would not apply if the damage type had already been changed (Electrical/Plasma OC)
  
• Fixed an issue where the Breachcutter beam would not apply status effects
  
• The Armskore Coilgun now displays lifetime and the VFX is shown for the entire lifetime
  
• The Armskore Coilgun VFX now properly scales with lifetime
  
• Wave Cooker stats now also show weapon range
  
• Fixed an issue with Nishanka Boltshark X-80 Payload not always sticking to valid targets
  
• Fixed an issue where the ground zone from Krakatoa Protocol Unstable OC would not do damage, but only apply stacks
  
• Impact Axe now properly supports Explosion Radius
  
• Improved the input legend to show controller icons, and fixed an issue where keyboard shortcuts would show up on Steam Deck

• Added Loading Tips. If you don’t like the loading screen waiting for a key press, it can be disabled in settings
  
• Added gameplay tips in the menus
  
• Red Vines in Hollow Bough now do damage when you are too close, instead of when mining them
  
• Red Vines in Hollow Bough no longer regrow when near the drop pod
  
• Added new Weapon icons
  
• Added new end-screen layout
  
• Added weapon damage tracking to the weapon inspect screen
  
• Added a mailing list button in the quit pop-up - sign up for DRG:S news to your inbox!
  
• You no longer have to be quite as close to the drop pod to see through it
  
• There never were secret levels and there certainly aren’t more now

• Class Rank XP and credit gain boosted by ~10%
  
• Supply Pod now does less damage to elites and bosses at higher hazard levels (Elite 100/90/80/65/50%) (Boss 33/30/27/24/20%)
  
• Enemies move faster on higher hazards
  • ~+2% enemy move speed on haz3
    
  • ~+4% enemy move speed on haz4
    
  • ~+6% enemy move speed on haz5
• Reduced the enemy speed bonus when enemies grow stronger (8% -> 5%)
  
• Enemy HP has been buffed about 5% on stages 2-5 to compensate for the added power creep of elite loot crates and overclock buffs
  
• Wardens lingering shield duration is lowered from 2 sec to 0.5 sec
  
• Mini Exploders
  • Base HP is now 200 (was 210)
    
  • Base Damage is now 12 (was 15)
• Deploying turrets when standing still is now a lot faster!
  
• After level 100 it requires more XP to level up
  
• Some scaling artifacts now have max stacks
  • Pay2Win Console has been nerfed to 2.5% damage pr. reroll instead of 3%. Also been capped to 100 max stacks
    
  • Gold Scanner - stops working after 1500 gold mined per scanner
    
  • Nitra Scanner - stops working after 1000 Nitra mined per scanner
• You will no longer receive speed upgrades after hitting +100% speed in the skill category (not counting artifacts and meta)
  
• You will no longer receive mining upgrades after hitting +150% mining speed in the skill category (not counting artifacts and meta)
  
• Knockback now has diminishing returns. When enough knockback has been applied the enemy will be knockback immune for 1.2 seconds

• Ark-Tek Cryo Guard
  • Crisis Protocol:
    • Now gives +25% damage and +25% potency
  • Disposable Tech (redesign):
    • Now reverses the effects of the lifetime stat (+Lifetime = short drone lifespan)
      
    • Drones drop ground zones that scale positively with lifetime!
      
    • +100% lifetime (was -20%)
      
    • +40% Reload Speed (was +30%)
  • Personal Space Invaders:
    • Increased range reduction to -65% (was -50%)
• Cryo Grenade
  • The Favourite:
    • -20% reload speed and -20% potency to all other weapons (was -30% reload speed and -30% potency to all other weapons)
• Deepcore GK2
  • Big Game Hunter:
    • +10% crit damage
      
    • +10% crit chance
• Drak-25 Plasma Carbine
  • Bigger Mags:
    • Reload Speed -10% (was -20%)
  • Storm E-Mag:
    • Now fires 36 bullets (was 18)
• Jury-Rigged Boomstick
  • Bigger Mags:
    • Reload Speed -10% (was -20%)
  • Mini Pellets:
    • Reduced damage penalty to -10% damage (was -20%)
  • Thick Boy
    • +200% Piercing
      
    • +200% Weapon Range
      
    • Potency now also scales with clip size
• M1000 Classic
  • Bigger Mags:
    • Reload Speed -10% (was -20%)
  • Thick Boy:
    • Potency now also scales with clip size
• Nishanka Boltshark X-80
  • Payload:
    • Damage scale on explosion increased to +100% (was +50%)
• TH-0R Bug Taser
  • Explosive Reload:
    • Greater explosion radius
      
    • 50% stronger knockback
  • Sidearm:
    • -20% damage to this weapon (was -25%)
• Voltaic Stun Sweeper
  • NEW OC: Potent Juice:
    • +35% Potency
  • Big Game Hunter:
    • +10% crit damage
      
    • +10% crit chance
  • High Velocity Bullets is now called Lightweight Alloy:
    • Weapon Range reduced to +30% (was +50%)
      
    • Reload Speed +15%
  • Sidearm:
    • -20% damage to this weapon (was -25%)
• Zhukov NUK17
  • Bigger Mags:
    • Reload Speed -10% (was -20%)
  • Explosive Reload:
    • Greater explosion radius
      
    • 50% stronger knockback
  • Omni Barrel:
    • Reload speed reduced to +100% (was +200%)
      
    • Damage increased to +50% (was +30%)
      
    • Piercing +50%

• Weapon Specialist Passive now scales (50%) with global damage upgrades as well as projectile and kinetic tag upgrades
  
• ArmsKore Coil Gun
  • The Armskore Coilgun now has the [LASTING] tag to show that the beam scales with lifetime.
    
  • NEW OC: Spliced Emitter:
    • +50% lifetime
      
    • +50% weapon range
      
    • +30% damage
  • Explosive Reload:
    • Greater explosion radius
      
    • 50% stronger knockback
• BRT7 Burst Fire Gun
  • Bigger Mags:
    • Reload Speed -10% (was -20%)
  • Omni Barrel:
    • Reload speed reduced to +100% (was +200%)
      
    • Damage increased to +50% (was +30%)
      
    • Piercing +50%
  • Sidearm:
    • -20% damage to this weapon (was -25%)
• “Bulldog” Heavy Revolver
  • NEW UOC: Super Reload Shield
    • +100% armor while reloading
      
    • +75% Damage
      
    • +50% Fire Rate
      
    • -25% Reload Speed
  • Bigger Mags:
    • Reload Speed -10% (was -20%)
  • Reload Shield:
    • +25% Fire Rate
• Firefly Hunter Drone
  • Behaviour Chip: Defensive:
    • +2 extra drones
      
    • -10% Weapon range
  • Disposable Tech (redesign):
    • Now reverses the effects of the lifetime stat (+Lifetime = short drone lifespan)
      
    • Drones drop ground zones that scale positively with lifetime!
      
    • +100% lifetime (was -20%)
      
    • +40% Reload Speed (was +30%)
  • Drone Mining Damage:
    • Increased mining damage by 100%
  • Fuel Leak:
    • +20% Potency
• Incendiary Grenade
  • Feedback Harness:
    • Cooldown reduced to 10 sec (was 15)
      
    • Throws 1 more grenade
  • Potent Juice:
    • No longer gives -10% damage
  • Tape Some Nails to It:
    • +10% Damage
• “Lead Storm” Powered Minigun
  • Spread reduced to 8 (was 15)
    
  • Firing cone increased to 150 degrees (was 120)
    
  • Damage increased to 18 (was 16)
    
  • Base potency increased to 7 (was 6)
    
  • Bigger Mags:
    • Reload Speed -10% (was -20%)
  • Reload Shield:
    • +25% Fire Rate
• Seismic Repulsor
  • Disposable Tech:
    • +100% Reload Speed (was +30%)
      
    • -50% Lifetime (was -20%)
• Tactical Lead Burster
  • NEW OC: Fusion Turbines:
    • +20% Lifetime
  • Tape Some Nails to It:
    • +10% Damage
• “Thunderhead” Heavy Autocannon
  • Bigger Mags:
    • Reload Speed -10% (was -20%)
  • The Tightest of Springs:
    • 125% fire rate (was 150%)

• Breach Cutter
  • New UOC: Experimental Cluster Projectiles
    • Splits into smaller plasma projectiles
• Deepcore PGL
  • Bigger Mags:
    • Reload Speed -10% (was -20%)
• Hi-Volt Thunderbird
  • NEW OC: Potent Juice:
    • +35% Potency
  • NEW UOC: More Drones
    • +3 drones
  • Crisis Protocol:
    • Now gives +25% damage and +25% potency
  • Disposable Tech (redesign):
    • Now reverses the effects of the lifetime stat (+Lifetime = short drone lifespan)
      
    • Drones drop ground zones that scale positively with lifetime!
      
    • +100% lifetime (was -20%)
      
    • +40% Reload Speed (was +30%)
• LOK-1 Smart Rifle
  • Bigger Mags:
    • Reload Speed -10% (was -20%)
• LMG Gun Platform
  • Base damage increased to 20 (was 18)
    
  • OC Extra Capacity:
    • +1 Turret
      
    • +10% Damage
  • UOC Extra Capacity:
    • +3 Turrets
      
    • +10% Damage
  • LMG Overload:
    • Fire rate reduced to +100% (was +150%)
  • Removed: Disposable Tech
• Plasma Burster
  • Tape Some Nails to It:
    • +10% Damage
• “Stubby” Voltaic SMG
  • Explosive Reload:
    • Greater explosion radius
      
    • 50% stronger knockback
  • Impact Punch:
    • Removed the -10% potency penalty
  • Sidearm:
    • -20% damage to this weapon (was -25%)
  • Storm E-Mag:
    • Now fires 36 bullets (was 24)
• Shredder Swarm Grenade
  • NEW OC: Electrified Dispenser:
    • Drones tether to the grenade with an electrical arc
  • NEW OC: Tape some Ice to it!
    • Adds a cryo explosion to the grenade
• Voltaic Shock Fence
  • NEW UOC: Rapid Deployment
    • Deploys all turrets at once
  • Disposable Tech:
    • Leaves an electrical ground zone
      
    • Reload speed reduced to +20% (was +30%)
  • OC Extra Capacity:
    • +1 Turret
      
    • -10% Weapon Range
  • UOC Extra Capacity:
    • +3 Turrets
      
    • -30% Weapon Range
• “Warthog” Auto 210
  • Mini Pellets:
    • Reduced damage penalty to -10% damage (was -20%)

• C.R.S.P.R. Flamethrower
  • Spliced Emitter
    • Damage +50% (was +30%)
      
    • Potency +50%
• Colette Wave Cooker
  • NEW OC: Centralized Reflector:
    • Adds an additional beam in the opposite direction
• Corrosive Sludge Pump
  • NEW UOC: Top-Shelf Sludge
    • Adds electricity to the ground zone
  • Impact Punch:
    • Removed the -10% potency penalty
• Cryo Cannon
  • Potent Juice:
    • No longer gives -10% damage
  • Spliced Emitter:
    • Damage +50% (was +30%)
      
    • Potency +50%
• High Explosive Grenade
  • Feedback Harness:
    • Cooldown reduced to 10 sec (was 15)
      
    • Throws 1 more grenade
• Impact Axe
  • NEW UOC: Colossal Twinblade
    • Larger axe
  • NEW UOC: Fan of Axes
    • 3 smaller axes
  • Removed: More Axes
• K1-P Viper Drone
  • Behaviour Chip: Defensive:
    • +2 extra drones
      
    • -10% Weapon range
  • Crisis Protocol:
    • Now gives +25% damage and +25% potency
  • Disposable Tech (redesign):
    • Now reverses the effects of the lifetime stat (+Lifetime = short drone lifespan)
      
    • Drones drop ground zones that scale positively with lifetime!
      
    • +100% lifetime (was -20%)
      
    • +40% Reload Speed (was +30%)
• Krakatoa Sentinel
  • Extra Capacity:
    • +10% Weapon range
  • Krakatoa Protocol:
    • Now also spawns an electrical ground zone
  • Removed: Disposable Tech
• Neurotoxin Grenade
  • Feedback Harness:
    • Cooldown reduced to 10 sec (was 15)
      
    • Throws 1 more grenade
  • Potent Juice:
    • No longer gives -10% damage
  • Tape Some Nails to It:
    • +10% Damage
• Subata 120
  • Akimbo:
    • Fire rate +15%
      
    • Potency +15%
  • Bigger Mags:
    • Reload Speed -10% (was -20%)
  • Sidearm:
    • -20% damage to this weapon (was -25%)

---

This Q&A started in our Discord, where the team first answered these questions directly. What you’re reading here is a cleaned-up version. Same core answers, just a bit more structured, with some extra context where it helped.
If you want the raw, unfiltered version, it’s still up in the #what-happened-to-update-5 channel on Discord.

Q: Why did the team pursue ECS in the first place?

ECS (Entity Component System) is an optional system in the Unity game engine that changes how we structure games. Instead of being object-oriented, it’s data-oriented, which makes it far more efficient at scale.

It’s powerful, but there’s a reason it’s not the default. ECS forces you to structure the game more like a computer handles data than how a human thinks about objects.

For a game like Deep Rock Galactic: Survivor, where there are unlimited objects and players constantly push the limits of what’s possible, that kind of performance boost felt worth chasing.

It wasn’t an easy shift. It required rewriting the core game from scratch. But we believed the long-term gains would justify the effort.

---

Q: What happened? Why did you decide to postpone it now, after months of work?

The short version is: We tried to make it work. We really did.

We were proud of what we’d built, and we still are. But chasing ECS meant putting off everything else we wanted to do. We kept running into the same dilemma: keep rewriting, or support the live game players were enjoying.

But by the time we had a playable ECS build, it was clear how much was still missing: biomes, bosses and even a few core systems.

Meanwhile, the team was split. Designers started feeling guilty just for designing. Every new feature added to the to-do list for the ECS rewrite. You either pushed forward and made things worse, or you held back and felt useless. Which in turn made the devs working on it feel guilty for blocking the rest of the team, completing a stressful loop that was far removed from how we used to work.

It wore people down. Features we were excited to build started feeling like problems and we kept having to compromise on our ambitions.

Something had to give.

We had some tough conversations internally and with Ghost Ship - who, by the way, have been incredibly supportive through this whole thing, their empathy and comradery has been a massive support. In the end we had to make the call to delay ECS and Endless mode with it.

When we finally made the call to postpone ECS, it unblocked the whole team and we could immediately start working on the same game again.

Since then, the mood has changed dramatically. Designers are pitching again, developers are adding to the game again and we are getting in touch with what we have, a game we are massively proud of with an amazing community that we want to see flourish.

We are getting back to what worked for the first 4 updates. An iterative process where we build and add one thing at a time, as a team, while we play and have fun making the best damn Survivor-like we can.

We hope you'll feel that shift in Patch 4.2.

---

Q: Why not just delay the update a little longer and finish ECS first?

That was the original plan. We kept hoping we’d make it. But by the end of Q1, we still had months of work left just to rebuild what we already had.

Pushing ECS further would’ve meant more waiting and even less momentum. And more importantly, the rest of the team was already stuck, not by choice, but because the systems they needed weren’t ready.

Postponing ECS lets us work together again.

---

Q: Is ECS scrapped completely, or is it just postponed?

It’s postponed, not scrapped. We still believe in ECS. For a game like ours, where the number of objects on screen can grow fast, it’s still the right long-term solution.

But we want to return to it when, and in a way, where it isn't dependent on others and it wont block progress or create friction across the team. And that way, give it the time it needs to be done properly.

Full Explanation from our Lead Programmer, Martin (If you can't see the "Show More" button - try opening the patch notes in a browser):
[expand type=Full Explanation from our Lead Programmer, Martin=false]
I'm Martin, the lead programmer on DRG: Survivor.

I decided to do a little write up going into a bit more detail about what this ECS rewrite thing is, since there are a lot of questions about it, and a few misconceptions out there.
It's hard to write about this without getting technical so if you dont care about cpu caches, Object Oriented Programming vs Data Oriented Design etc, this post is probably not for you. If this sounds interesting, stick around.

Whenever I talk about performance gains and “factor x speedups” in this blogpost, I am talking about the game code, which runs on the CPU. The other half of the equation is rendering which partly takes place on the GPU, and is not accounted for in this post.

The headline term is "ECS" but the important term is "Data Oriented Design" which is the underlying programming philosophy behind Unity ECS.

DRG: Survivor is made with the Unity Engine and our game logic is written in the Object Oriented Programming paradigm (OOP style), which is one of the most common paradigms in a lot of software.
Now, I'm actually fairly proud of how quickly we created the game (15-ish months) and how well the game performed (frame rate wise) at the Early Access launch.
We are simulating, animating and rendering A LOT of stuff on screen when things get a bit wild.
However, with the plans we have for this game, we need way better performance than what we can achieve with the current code base and OOP.
The current codebase was written with the objective of being very flexible and easy to change. We change stuff 50 times a day during initial development. This is no longer the case.

OOP is designed to accommodate how a human (programmer) brain thinks about objects, and almost feels designed to hide away stuff from the CPU at every turn, making the CPU's job harder. Yet, lots of software is written this way because of how fast computers actually are today. For most things it doesn't matter (I disagree but that's the consensus out there). But for games, it absolutely matters.

Another paradigm is Data Oriented Design (DOD), which means writing code in a way that accommodates how a computer actually works.
DOD code will try to minimize how often the CPU has to fetch data from main memory (the RAM sticks you put in your computer). The CPU itself has a tiny bit of memory built-in. This is called "Cache". You will see this on CPU specs when shopping : L1 cache, L2 cache etc. When writing DOD code, you are working to make sure that as much data as possible is ready in the cache BEFORE the CPU actually needs it, so it doesn't have to ask for the data from main memory. You can't entirely avoid this, but you can minimize how often it happens. You do this by putting careful thought into how you lay out your data in memory. A lot of programmers aren't used to thinking this way.

Here is an example as to why avoiding a main memory fetch is important (the numbers below are somewhat made up, not entirely accurate):

A common thing we do in games is to measure distance (say, from the player to an enemy). A common approach to this is to measure the SQUARE of the distance instead. We do this because a raw distance calculation involves a square root. That's an "expensive" operation for a cpu. Lets say a square root costs 25 cycles (dont worry about what a cycle is). We calculate the square distance instead, let's say that costs 12 cycles. Yay!
However, in most cases with OOP code, we don't have the player position OR the enemy position ready for the CPU in cache, so we have to fetch those from main memory before we can do any calculations. That costs about 200 cycles(!). So we are doing this useless square distance optimization for something where just getting the numbers we need into the cpu is 90% of the total cost.
This cost is inherently there in every line of OOP code. This cost is the reason why you can only optimize to a certain point in a large OOP codebase. Its "death by a thousand cuts"

If you extrapolate this example into everything we do, you can see how there are massive performance gains to be had here. In fact, that goes for most software you use on a daily basis, but that's a different rant for a different day.

In Unity, it hasn't really been possible to do proper DOD, but right around the time when we started development on DRG:S, Unity released v1.0 of their DOD framework (called DOTS - which ECS is part of). We didn't take advantage of it back then, because it would have been massively irresponsible of me to employ a brand new and largely untested technology on a big important project like this one. But things are different now. Unity ECS is deemed stable and functional. We know what the game is, we know where we want it to go, and we don't have to experiment nearly as much as we did on day 1.

Another massive advantage to writing DRG:S in ECS, is that Unity has a special compiler called the Burst Compiler, which we can now take full advantage of. This is as close as you can get to a free "5-20x performance increase" button. It's just that good, but requires our code to be written a certain way for it to compile for us (the technical jargon for this is no managed objects, or no reference types, and no garbage collector).
It also enables us to more easily and safely use multi-threading where applicable, which means to split the work over the multiple cores in your CPU, doing more things in parallel instead of sequentially. That's a deep, deep topic, I won't get into here.

So, we decided it was worth it to rewrite almost every line of code that you, the player, interact with after the initial loading screen. (UI code and menu code is largely unchanged).

Was it worth it?
I've seen people speculate that maybe we weren't seeing the performance increases we were hoping for. I'm happy to report: that isn't the case. In some internal test cases we have had the screen covered in glyphids, standing shoulder to shoulder (or mandible to mandible) with the game maintaining a framerate of 300. This doesn't mean the game will run at 300 FPS for you, because these were slightly artificial tests without any sound processing or VFX running. But it's far, far faster than what the current codebase is capable of.

Unfortunately, I made a classic programmer blunder and underestimated how long this entire rewrite would take.

There are deadlines we have to meet in order to ship v 1.0 to you guys and we have exceeded several of those by now. So the decision was made to pause the ECS rewrite, work on shipping 1.0 and then resume work on ECS (+ the game features it will unlock for us) at some point after the release of 1.0. For you, it means that things will still get to you, but the order is different than what you (and we) thought it would be.
1.0 does not mean the end of development for us, we intend to keep going.

I can only apologize, it sucks when we miss deadlines (trust me, I know) but that's unfortunately how game development goes sometimes.

I skipped over a lot of complexity here, but I hope this write up has helped shed some light on what Data Oriented Design is from a high level perspective , and why we aim to get it done.
[/expand]

---

Q: Will it be harder to switch to ECS later, once more content has been added?

Yes, it’ll take longer. There’ll be more content to migrate when we pick it back up. But the core systems are already in place, and most of what’s left is repetitive implementation, not new design work.

---

Q: Can the work done so far still be used later?

Yes. It won’t be starting from scratch again. But we don’t expect to come back to it at full speed on day one either. It’ll take time to ramp up again once we decide it’s the right time.

---

Q: Will the performance improvements happen after 1.0, or as part of it?

After. We want to decouple 1.0 from ECS so that performance refactoring doesn’t block other features. That pressure, on both the ECS devs and everyone else, is what led to this pivot in the first place. We’ll return to performance upgrades when we can do them right.

---

Q: With endless mode being postponed, does this mean other updates will be pushed ahead of it? Bosco, more bosses, etc?


It might. With ECS postponed, we have the developer bandwidth to make a 1.0 that lives up to our ambitions. What comes after isn’t set in stone, but we may adjust the order of future updates depending on which features create the least friction when ECS returns.

We’ll share more roadmap updates after 4.2. But honestly, we try not to lock things down too early. Focusing on the current update before committing to the next one has worked well for us so far. It lets us adjust our perception of what the game needs based on the current state and not some abstract expectation made months in advance. This way we stay agile and responsive to player sentiment and our own ambitions for the game.

---

Q: How does this affect the 1.0 release?

It lets us focus on building a 1.0 with some features we are really excited to make and share.

What happens after 1.0 isn’t locked in yet, but we’ll prioritise features that won’t need to be redone once ECS returns.

---

Q: What’s next after 4.2? Is 1.0 the next update?

Not set in (rock &) stone yet. We're going to share a new roadmap that explains what's next soon.

---

Q: Will anything be reset when 1.0 comes out? (Progress, upgrades, masteries?)

No. Patch 4.2 won’t reset anything, and we don’t currently have plans to reset anything for 1.0 either.