HTML Accidental Woman [v1.27.2 Cheats] [ThaumX]
Is the Tight Threads custom clothing store implemented? After entering the store, there's basically a blanck screen with no custom clothing creation.
Just went through it and I LOVE IT. I love the intense amount of detail and can't wait for the content to really start coming in. There seems to be a glitch in the right side menu with the status since the "cumming" status didn't go away after I fucked someone in the dressing room. Also, when the realtor comes around, she calls me Miss Drumph instead of the last name I had changed it to.
Does the current content of the game allow the main character to become a futanari? Is the futa tag still limited to that one side character?
I don't really see how he lacks planning considering how its all going to plan with it being in alpha currently, still in the framework phase I believe
Having a proper testing procedure, and committing to carrying it out, is a part of planning. Just to name one example. Another is not releasing alpha (or in this case, pre-alpha) code to the general public. Releasing code to the general public is called an "open beta".
Not knowing what is involved in the software development process, such as what is an alpha, a beta, and how to test, are fundamental failures in planning. In other words, poor project management.
- Jun 3, 2017
- 84
- 40
Oh, I get that we're still in the framework development phase. My problem is that the framework has major problems:
Having this happen once would be annoying...but it happens EVERY morning.
You don't have permission to view the spoiler content.
Log in or register now.
Shouldn't happen at all, because if at least a minimal amount of basic internal (alpha) testing was done then you'd not run into this sort of problem. Code released to the public (for open beta) should at least be stable. What these sorts of bug reports show is that they're not playtesting their own game before they allow someone to upload it.
By analogy, it's like shipping a car to a dealer that has not had doors installed, nor airbags, nor interior panels. And when the dealer gets it he discovers that it was sent with the wrong sized tires, wrong grade of engine oil, and just enough of the fluids to keep the engine from instantly blowing a gasket, throwing a rod, or having the transmission seize. And barely enough charge in the battery to start the engine -- once, since no one checked to see if the alternator is recharging the battery.
Sorry, but there are different definitions for alpha/beta etc versions, and all the early acces titles certainly watered things down, but the following definitions is what I learned, and what I've heard a lot of other people use.
pre alpha = Planning
alpha = feature/content implementation
beta = (mostly) Feature Complete and mainly bugfixing and refining of features and content.
It really doesn't matter if your code is public or not. you can have open/closed alphas and open/closed betas, depending on your preferences.
Minecraft for example used a similar system, though they still added a bunch of features and content during beta and even after release.
And there are lots and lots of alpha open source projects out there, that aren't exactly stable or feature complete as well, and guess what, that's exactly what is to be expected from an alpha software.
pre alpha = Planning
alpha = feature/content implementation
beta = (mostly) Feature Complete and mainly bugfixing and refining of features and content.
It really doesn't matter if your code is public or not. you can have open/closed alphas and open/closed betas, depending on your preferences.
Minecraft for example used a similar system, though they still added a bunch of features and content during beta and even after release.
And there are lots and lots of alpha open source projects out there, that aren't exactly stable or feature complete as well, and guess what, that's exactly what is to be expected from an alpha software.
Alpha software is supposed to be feature-complete and ready for internal testing. If the design is still in flux, coding should not have even begun yet, much less have a half-assed piece of software thrown at testers to waste their time on. Let's assume that the design has been frozen. Then the next phase of the software development cycle is to code. From start to finish, per the project's design documents which detail requirements and specifications. When coding is complete, then it's ready for alpha (internal) testing. Once the software has been deemed stable, then it can be presented to outside testers (typically the customers who ordered/paid for it to be made, or in the case of most games, your prospective customers) in the form of first a closed beta, then a wider, open beta. During the alpha and beta testing phases the only thing that should be changing in the code is the squashing of bugs. This is not where features get added. Features might be disabled or removed during testing, but this is usually due to a failure in project management to keep a project on schedule and within budget.
Unfortunately, the advent of so-called early access (a thinly veiled form of greed on the part of developers with insufficient funding to accomplish their goals) has led to some development houses releasing code for projects that haven't even had their feature specifications frozen, much less being code-complete and ready for alpha testing. Sites like Patreon have only exacerbated this trend. Yes, it empowers developers to be able to get projects off the ground that otherwise would never see the light of day. But it also makes a shambles of project management and software development. And players pay a price, not just in dollars, but all too often dealing with programs that are hastily written, or unstable, or poorly documented, or just plain shoddy. And that doesn't even begin to look at the issue of developers that milk their patrons, month after month, for money while providing little to no value. How long has this game been in "development"? (That's a rhetorical question.) All the while milking patrons. To their credit they do say up front that it's not at a playable stage yet. If a project is so grandiose that it's going to take 2+ years to reach a playable point, then it shouldn't be on Patreon. It should be on Kickstarter (assuming that KS allows porn, which I'm not sure it does).
Unfortunately, the advent of so-called early access (a thinly veiled form of greed on the part of developers with insufficient funding to accomplish their goals) has led to some development houses releasing code for projects that haven't even had their feature specifications frozen, much less being code-complete and ready for alpha testing. Sites like Patreon have only exacerbated this trend. Yes, it empowers developers to be able to get projects off the ground that otherwise would never see the light of day. But it also makes a shambles of project management and software development. And players pay a price, not just in dollars, but all too often dealing with programs that are hastily written, or unstable, or poorly documented, or just plain shoddy. And that doesn't even begin to look at the issue of developers that milk their patrons, month after month, for money while providing little to no value. How long has this game been in "development"? (That's a rhetorical question.) All the while milking patrons. To their credit they do say up front that it's not at a playable stage yet. If a project is so grandiose that it's going to take 2+ years to reach a playable point, then it shouldn't be on Patreon. It should be on Kickstarter (assuming that KS allows porn, which I'm not sure it does).
Just like some people have different definitions of what is a 'fact'. "Alternative facts"? A euphemism for misleading and/or lying. Facts are subject to interpretation, but they cannot be denied. You can't just make shit up and get away with it. Well, not until recently, it seems. Unfortunately, that's also the case with re-labeling what is an alpha or a beta.
Calling something an alpha or a beta, when it's not even half-baked yet, is just pandering to the ignorance and/or stupidity of those that never bothered to learn how to do professional software development. Accepting their definitions is enabling a continuation of that ignorance and/or stupidity.
I'm not talking about alpha and beta testing phases, that some (but not all) developers use to distinguish between public and non public testing, I'm talking about development phases.
And I learned these definitions over 20 years ago, so well before the advent of early access games.
Also there is a big difference between corporate dev cycles (which need, by virtue of being a corporate project, a much stricter definition), and other development cycles.
I get it, you would probably make it different, and that's fine. But not everyone goes by your definitions, and not everyone uses corporate dev cycles.
Different sized project with different sized teams need different dev cycles. There is no one true meaning to alpha, beta etc. stages.
So you calling him wrong on that, doesn't mean that much, other than you are stuck in your own ways.
A much more open dev cycle with broader definitions and less strict restrictions can be more benefitial for some devs, and especially for creativity, and the freedom to change or replace functionality, can be beneficial to some projects, especially in small teams.
It certainly comes at the risk of feature creep or stalling development, but I see no signs for that in this project.
He stated his plans very clearly at the beginning, and has a road map somewhere, and whilst I haven't checked it in a while and confirmed it, I'm pretty sure he said that he'll be working on the framework before adding content, and as far as I'm informed (again, I haven't crosschecked it, because I had no reason to do so) he's still pretty on course with that.
As in regards of Patreon: I really haven't checked his numbers, but wether or not a certain project is worth supporting or not is only yours to decide for yourself. In general I don't support any patreon projects, for the simple fact, that I can't afford it. I also don't agree on monthly pay cycles for the most part, but everyone has to make that decision for themselves, and again everyone has his own opinion on that. The only thing you can do, that is sensible is to vote with your money, and voice your opinion in either direction at the author directly in a respectfull manner.
Posting in here most likely will accomplish nothing, especially if you do it in a way, that states your opinion on how you would do dev cycles as a fact that everyone has to agree to, when it quite obviously isn't everyones opinion, or even usefull for every project.
In any case I'm off to bed. Happy new year everyone, have a good one.
Edit:
And I learned these definitions over 20 years ago, so well before the advent of early access games.
Also there is a big difference between corporate dev cycles (which need, by virtue of being a corporate project, a much stricter definition), and other development cycles.
I get it, you would probably make it different, and that's fine. But not everyone goes by your definitions, and not everyone uses corporate dev cycles.
Different sized project with different sized teams need different dev cycles. There is no one true meaning to alpha, beta etc. stages.
So you calling him wrong on that, doesn't mean that much, other than you are stuck in your own ways.
A much more open dev cycle with broader definitions and less strict restrictions can be more benefitial for some devs, and especially for creativity, and the freedom to change or replace functionality, can be beneficial to some projects, especially in small teams.
It certainly comes at the risk of feature creep or stalling development, but I see no signs for that in this project.
He stated his plans very clearly at the beginning, and has a road map somewhere, and whilst I haven't checked it in a while and confirmed it, I'm pretty sure he said that he'll be working on the framework before adding content, and as far as I'm informed (again, I haven't crosschecked it, because I had no reason to do so) he's still pretty on course with that.
As in regards of Patreon: I really haven't checked his numbers, but wether or not a certain project is worth supporting or not is only yours to decide for yourself. In general I don't support any patreon projects, for the simple fact, that I can't afford it. I also don't agree on monthly pay cycles for the most part, but everyone has to make that decision for themselves, and again everyone has his own opinion on that. The only thing you can do, that is sensible is to vote with your money, and voice your opinion in either direction at the author directly in a respectfull manner.
Posting in here most likely will accomplish nothing, especially if you do it in a way, that states your opinion on how you would do dev cycles as a fact that everyone has to agree to, when it quite obviously isn't everyones opinion, or even usefull for every project.
In any case I'm off to bed. Happy new year everyone, have a good one.
Edit:
Sorry, the only one relabeling alpha and beta dev cycles is you
- May 4, 2017
- 704
- 613
Could you please upload bigger images next time it is updated? Cause I can't see anything. Ty. 
