vinfamy
patreon
IMPORTANT: New Release Schedule for Less Bugs and More Ambitious New Content
🕑 Added 2023-04-10 06:57:30 +0000 UTC(Rest assured, there will still be 3 kinks a month, more consistently so, even.)
As you know, I switched to the current 3-updates-a-month release schedule (usually around the 8th, 18th and 28th of each month) about 2 years ago to fulfill the promise of the $1000 milestone. While it hasn't been too difficult to actually release 3 updates a month, I think it's time to admit that the release schedule has been harming the overall quality of the project.
First, the obvious: 3 updates a month has introduced so many more bugs that pile up more and more each month, worsening the players' experience by the month. Because I only have 10 days max to work on each update (significantly less if it's Feb, or Christmas etc), by the time I've finished the new content for each update's kink, it's usually around on the ETA or at most one day before ETA so the playtesting and bugfixing is usually rushed. You might have noticed in recent months I've tried to mitigate this by not being so strict on the 8th-18th-28th dates and have taken a day or two extra if needed for bugfixing until I felt comfortable enough to release the update. Still, a day or two extra playtesting on my own doesn't guarantee that I have been able to detect all the bugs let alone fix them, because LifePlay is a lifesim sandbox that's getting bigger and bigger, there are just so many playstyles and variables that honestly, the only way to detect all the bugs is with the community's help with all the different players playing the game. There have been times in the past where I felt I took the time needed for playtesting and felt pretty confident about releasing an update, only to find out within days of the release from the community there's a game-breaking bug when playing a specific type of player character. This has turned into a bit of fear and instead of looking forward to people enjoying each new update, more often than not, I'm nervous about whether there might be a game-breaking bug I missed. Furthermore, when I don't have enough time to fix bugs, I have even less time to support modders and expand modders' API, which has killed the modding scene a bit.
Being terrified about bugs causes a more serious but less obvious problem: new content has become stale and 'safety first'. When I'm already overwhelmed by existing bugs, it's extremely hard to get over that fear and reluctance to work on new content that is ambitious, aka dangerous in terms of potentially breaking things. This includes a lot of good ideas I see every week in the Discord brainstorm, that I feel guilty to skip, but is too worried about it messing with existing systems and introducing game-breaking bugs. Instead, especially when I know there are already a lot of existing bugs I haven't go to yet, I've usually stuck to adding new scenes (i.e. lpscene files) only for the particular kink, rather than working on more advanced stuffs. I'm sure many players don't mind just new scenes, but there's a limit to what the lpscene format can do and tbh, with the game already having modding capacity for third parties to make their own mods full of new scenes, tbh just being a writer of scenes isn't the best use of the developer's time. I really should be working on the advance stuffs that modders can't as well as improving the API for modders so that they can make more mods aka far more scenes that I can write by myself anyway.
So, here's the new release schedule. Two updates per month:
- Each month's Beta Update is released between the 18th to 21st of each month. This Beta adds all the new content for the month for all three winning kinks of that month.
- Each month's Stable Update is released between the 28th to 31st of each month. This update adds no new content is all about fixing bugs and expanding modders' API.
Between the two updates, there will be a public beta testing + modders' requests period (about 10 days) on Discord and GitHub (I will post a new GitHub repo link for this when the next update comes out) where everyone is welcome to playtest the beta update and report bugs so that I can fix them. The advanced bug reporters can directly do pull requests on Github for scenes. Of course, it's perfectly understandable if you just skip the Beta update and only play the Stable update each month, but the more people playtest the Beta update and report bugs, the more effective the system will be.
This way, not only will I have more time + community help when it comes to detecting and fixing bugs, but also for the Beta update, because it's a beta update with players knowingly volunteering to playtest, I don't have to be so afraid of adding the more ambitious new content that might break things. Sure, I'll have 20 days instead of 30 days to work on each month's three kinks. This will lead to a reduction in new scenes written by me directly and a switch of focus to me working on expanding systems and adding advanced hard-coded content that modders can't. However, hopefully with each month's Stable update now also expanding modders' API to support them more, the new scenes coming from modders will be far more numerous than what I used to write myself anyway. Also, there will be consistently 3 kinks each month now (the 2 top of the poll + 1 chosen as unlucky loser), no more occasional bugfix-update that takes away one kink.
To fit the new release schedule, new versioning numbers will be used for clarity. So accordingly, the next 4 updates upcoming will be:
- v 2023.04 Beta (paul Ince..., Vore, University). ETA 18th-21st April.
- v 2023.04 Stable. ETA 28th-30th April.
- v 2023.05 Beta (Fantasy Races, Pregnancy + one more kink to be voted on). ETA 18th-21st May. (you might recall Pregnancy is the update I 'owed' from last month)
- v 2023.05 Stable. ETA 28th-31th May.
Thank you for your support to date and I hope you can understand and support this new release schedule going forward. I genuinely felt the project was going off track with the last release schedule and this is the only way to get back on track, stay on top of the bugs, add more ambitious content and revive the modding scene.
Comments
GreenSpartan111
Hey, any idea when the next update is?
oh, 1 other thing I forgot to say, when you do the updates can you also list the bugs that you addressed? For example, beta or not I would like to know when it's safe to turn bonus points back on or run the In My Place quest, etc. beta is all fine and good but there's not much point testing a known issue that has not been addressed unless you like allot of "still broke" reports.
if you recall April was ALREADY slated for bug fixes as the 3rd, Vin said nothing about NOT doing that, he just forgot to articulate that in the schedule above. personally I approve of this change, I've always believed beta test was the way to go. But a reminder to Vin, you have a dedicated group of followers, some of whom-especially the modders-are quite tech savvy, and several of them are I believe willing to help you with the bugfixes. I would propose you open up more of the code to those willing to help you, and to get over inconsistencies in those fixes have them submit the fixes to you with you as the ultimate arbiter of what gets put into the official patches. I'm not that tech-savvy but I know my native language, I'm personally willing to work on talk file entries for spelling/grammar-although you will still need to fix the part where they tie to precisely where the penetration is occurring ;) Regardless, this is a smart move, quality control is essential for any product
Matt Gorman
So 1 stable release per month with all 3 kinks? What about all the bugs there already?
SailorChaz
I would like to propose separate beta and stable branches, such that this month's beta is about new content and this month's stable is about fixing long-standing and previous-beta release bugs. That's a whole month of test/report/squash for each beta. And players get a legitimate choice of buggy-lateststuff-beta versus smooth-notsonew-stable. For both user groups, each month yields a fairly significant increase in content or capability. So April-stable squashes March-beta, and older, errors. April-beta contains new content and only critical patches. Also, I think it's not unreasonable for you to periodically declare a month, or more, of hardcore refactor/infrastructure work when you feel constrained by current capabilities or when the engine makes features faster or easier to implement.
Lee Thompson
As one of the modders, this sounds like a step in the right direction. I think if the base game can have some bugs squashed and the modding API sorted out, there will be lots of additional content for people.
