I see a lot of requests on this subreddit get shot down because Psyonix "has more important things to do". However, it's important to remember that in the software development process, you have multiple people simultaneously working on multiple different features.

Think of it this way:

Imagine five chefs in a restaurant working on multiple table's orders. Not only will there be enough space in the kitchen for all five chefs to work on their individual meals, but trying to have all five chefs work on the same meal simultaneously will leave a lot of them either standing around doing nothing--or worse, constantly getting in each other's way as they try to coordinate who's even doing what for a task that would be just as easily handled by a single person.

Software development is much the same way: You have multiple developers all working on multiple features, and while you will certainly have devs working together on larger problems, it's extremely important that they make sure to stay out of each other's way with what specific parts they're working on.

Much like the chef example, there's only so much that actually needs to be done, and only so many ways that you can break the task down into smaller parts to divide it between multiple people before it just becomes a pointless mess.

So does Psyonix have more important things to do? Of course they do. They always will. That's just how things go.

But please, stop shooting down requests and suggestions just because there's more important things on their to-do list as if it's exclusively a "one or the other" decision, because that's simply not how it works.

That's like demanding the kitchen never work on desert because the main course is too critical, only to find two of your chefs furiously working away while the other three stand their twiddling their thumbs because doing otherwise would simply be getting in the way.

And even if there is just so much broken with the game that every single dev in the office has something critical to work on... what about once they don't? What about once there's been enough of the issues fixed that they legitimately don't have something "more important to work on" any more? Do we want to just keep burying ideas, leaving them with no ideas for what sort of content the community is interested in?

Saying "we can discuss that once the bugs are fixed" isn't even that reasonable either. There's a whole process of finalizing, testing, polishing, approving, and delivering each version of the game that we get our hands on. During that process, many of the devs are going to be tasked with starting work on the next update, because otherwise, they'd be sitting around doing nothing. In short, because of the development process, we often don't receive bug fixes until well after said bug fixes have already been finished. (And no, that's not a reason to bitch at Psyonix; that's just how software development goes.)

So in short:

1. Only so many developers can reasonably work on the same issue at once.
2. There are only ever going to be so many "critical issues" at any given time to go around.
3. There will be--and likely very frequently is--plenty of time that developers would have literally nothing to do if Psyonix focused exclusively on critical issues and ignored everything else.

And that's not even touching the simple fact that different developers are skilled at different things, making some of them totally inappropriate to even go near certain issues.

tl;dr: Trying to argue that Psyonix has "more important things to do" fundamentally ignores how software is typically developed, and usually only serves to bury suggestions that could further improve the game rather than actually solve any of those issues any faster.

(Disclaimer: I'm half asleep, so if I did any of the words poorly and made much confuse, then in my defense: Oops.)

(Edit: Also, before anyone gets confused, no, I don't mean to imply I'm a Psyonix dev with that title. I am not. I'm just a software dev that's worked within several different development teams of various sizes, and thus understand how the software development process tends to work.)