It is obvious listening to the rising discontent across online channels that the current patch delivery model is not working. Backers are getting fed up with the constant broken release churn. Software development is most effective when "Quality Releases" and "Feature Releases" are treated as separate development cycles. A "Quality" Release should focus exclusively on improving the existing product through bug fixes, performance optimization, stability improvements, usability enhancements, technical debt reduction, and security updates. By avoiding new functionality during these cycles, development and testing teams can accurately measure the impact of quality improvements and reduce the risk of introducing new defects. CIG your current monthly cadence of patches is perfect for a quality release cycle. Issues that are addressed make it, issues that don't go to the next monthly patch. (btw you can still monetize your idiotic armor and ship skins bundles on the monthly quality patch, yeah we're not stupid we know why you have a monthly release, your accountants want paced income) 2. A "Feature" Release should focus on delivering new capabilities, expanding gameplay or functionality, and validating the product roadmap. These releases drive innovation and provide users with new experiences and tools. This cycle certainly can align with your events and major milestones (IAE, CitizenCon, Alien Week, Invictus, etc...) Separating the two Cycles provides several benefits: Clearer development priorities. More effective testing and validation. Reduced risk of regressions. Better measurement of quality improvements. Increased user confidence and satisfaction. TLDR: Feature Releases add value, while Quality Releases protect value. Both are essential, but combining them into the same release as currently implemented is complete madness. CIG you have no choice, you will have to go to a dual cycle release post 1.0, there simply no other choice, so start now and give your backers some relief from the shitfest broken releases.