My suggestion would be to:
- Release the visual, QoL, and sound updates with some bug testing on the beta branch. Basically the things that don't affect the gameplay loop to make sure they work and don't suck. The sound system seems like a major feature of this update, but trying to gather feedback on that alongside the sweeping gameplay changes seems foolish.
- After confirming those are all good, then test out all these gameplay changes in the beta branch as well. That way feedback for both can be easily separated.
- Communicate this plan and future plans with players in advance via STEAM posts, not the dev cast only (that most people won't see). This will make it so people know what to expect, when to expect it, and expectations can be tempered. Plus you can get people to hop in to try out the changes early!
Either way, these changes NEED to be tested out in advance. At this point I'm only interested in the update out of curiosity, I have 0 actual hype for it. But if I could get my hands on the changes and they feel GOOD I'll actually get hyped and will probably tell my friends to try to rope them back into the game.
Update from over a year later: Just beta test the update. I don't care anymore if it's properly tested in pieces or just all at once on the beta test. Getting some feedback from a limited run beta test would be good and at least build up hype if it is actually good.
.



suggestion threads
I'm pretty sure you're referring to diego, I don't remember advocating for turrets. Either way that doesn't discredit the benefits of basic inertia but just deflects to another unrelated thing
