Yeah, it sort of just depends on the severity and it depends on the difficulty of the fix.

The next thing we need to consider when prioritizing bugs is the impact on planning.

So with game development, time is a resource and we are limited in what we can achieve.

We can't do everything we want with the game.

So every bug we fix or feature that we add comes at a cost.

And that cost is other bugs and other features that we could fix or add.

So anything we choose to do will impact the planning of the project.

And without careful consideration for our plans, the project will spiral out of control and we'll never get it done.

Now, that doesn't mean that our plans are final and they're just rigid and we're just going to roll with them forever.

It's not as if we don't consider the current circumstances of what's going on.

We frequently change our plans, which is one reason why we don't publicly state our plans because they change all the time.

But it is important that we have something concrete to strive for because that provides us direction.

And without direction, we run into issues.

And so when prioritizing bugs and features with respect to planning, we try and get the best bang for our buck possible.

So sometimes multiple bugs or suggestions on the QA side, for example, can be addressed with a single carefully designed feature.

And those kind of features or additions, that's a goldmine where we can get a lot of wins just for one feature.

And that's what we need to be really, really mindful of and what we need to strive to look for so that we can get as much done in as little time as possible.