Update Flexibility, Ver Number Changes, and Fetish Poll Frequency
TLDR: Ver 3.4 and future versions will be released over smaller updates such as 3.4a.0, 3.4b.0, 3.4c.0, etc. The Fetish Poll will remain active during the entirety of 3.4-.0's cycle, closing on the release of 3.5a.0. Voting power remains the same!
Hello all,
With Ver 3.3 well behind us, we are charging forward to... Ver 3.4? Well, sort of. I wanted to go ahead and prepare everyone for some mostly small changes to how we label our updates. Not the most interesting news, but important nonetheless for book keeping.
As it currently stands, our Version label follows the following scheme: (Act #).(Update #)(Bugfix #). So, 3.4 would be our fourth update of the third act. However, I want flexibility in how often we can publish updates.
So, instead, the next major update you'll see from us will be 3.4a.0 (Act #).(Update Cycle #)(Update letter).(Bugfix) - So, how is this different? Now, Fetish Poll voted scenes will be distributed across 3.4-.0. Then, after they're all added in, we'll move on to 3.5-.0, rinse and repeat! This allows us to do smaller, piecemeal content updates without our wonderful Fetish Poll participants worrying that their anticipated scene was forgotten!
The total amount of Fetish Poll driven scenes per update cycle is not changing, only the frequency at which they're released. The FP victors are always top priority when it comes to new scenes in the game.
The only major change coming as a result of this shift is that whenever 3.4a.0 releases, I will open the Fetish Poll for Ver 3.6-.0 and it will remain open and available for all $10+ Patrons until 3.4-.0 has finished its entire cycle.
Importantly: each non-bugfix update will still follow the typical 2 weeks of Patron exclusivity before going public!
Alright, that was a lot over something so seemingly miniscule, but I've always believed that transparency is key and will always keep you all in the loop about changes, even if they are minor! If you've read this far, I greatly appreciate it!
Log in
