Why not have a set time for the servers in the back end to just reset every day?asked by BioNukes

That's one thing I forgot to put on the list of things we've changed this year, which is that we take maintenance windows. We used to never do that. Now, why not do this every day, right? The issue that you get is that it's not just resetting the server. So rebooting the servers, reloading the game shard from persistence and continuing, you're going to get right back in the same situation. So let's imagine. We're going to talk about cleanup density a bit later, but let's go back to the 3.x days where we persist all the data in the shard and we have deep intersections. So a ship entered another ship. It's an intersection. It's costing on the server. The server FPS is now shit. Super low. Physics threads using all the resources. And then you're like, OK, cool. Let's do a daily reset. It's going to fix that, right? So you go through it. You reboot it. Cool. Now the server reloads from persistence, and those ships are still intersecting. And so you're right back where you were. So you would look at the graphs, and you'd see FPS super low, zero during the reset, 30, then 5 instantly. And so what we've done for this is, now we have way more systems to deal with this, to reclaim performance for these cases. So first of all, we detect them. But also, we do emit fresh shards periodically. So we kind of decide when that happens. When we do massive weekly maintenance, we don't take it every week, but we do it when we have to make configuration changes or things like that. We'll take a downtime. And we're probably going to emit new shards and or run the repair on some of those shards. And then that will help. So we kind of do that. We just don't do it systematically, because the reality is that's not completely how it works for the backend persistence side of this. And it's not something that we can solve easily because the conditions are kind of too great. You need the shard to be live to solve these things.