Ren'Py RubyRed Trainer: A BDSM RWBY Parody Trainer [v0.04.5] [Fatbot]

[Fatbot]

So all-in, building on prior work, I've identified about 80 places where alternate pathways, new stat adjustments, or whole new skits, need to be written.
They're now all annotated and described so I can get to the nitty-gritty of making them all work.

As I did so (and grafted on new currently hidden stats and set a load of other stuff up) it occurred to me that the CNC enjoyers will have less varied sex scenes than everyone else, and so amended a previously added if hidden "broken" stat's role too.
This will allow for each CNC sex act to have 5 versions, gated at 0%, 25%, 50%, 75% & 100%; with Ruby offering first escalating resistance that must be overcome with increased manipulation or savagery, and then breaking entirely under your abuse.
These gates can also be used to make it simpler to trigger the evening visits based on the CNC stats (which will over-ride non-cnc stuff until Ruby "Recovers"), allowing for 8 new evening visit scenes; as Ruby either play-acts rationalising what you did and recovers some trust in you, OR tries increasingly desperate attempts to get you to stop.
Depending on whether her "break" or "recover" is highest. These I can set to test for a trigger every night, and then after you leave the CNC pathway I can leave replays to be accessible on the currently blank Monday night.

It's going to be a fair bit of work to get it all in place, but once it is it'll be developable concurrent with the other content. But since it'll be a slog and one I can hide behind a single set trigger I will take breaks from it occasionally so I can get the next Academic (train and punish) steps (along with the study BJ) into the game.

Anyway, enough boring Dev talk.
Here's another spanked MILF, because spanking and MILFs, and posts and so on.
I think Kali likes this treatment a LOT more than Willow did.........

 

[madchef]

So all-in, building on prior work, I've identified about 80 places where alternate pathways, new stat adjustments, or whole new skits, need to be written.
They're now all annotated and described so I can get to the nitty-gritty of making them all work.

As I did so (and grafted on new currently hidden stats and set a load of other stuff up) it occurred to me that the CNC enjoyers will have less varied sex scenes than everyone else, and so amended a previously added if hidden "broken" stat's role too.
This will allow for each CNC sex act to have 5 versions, gated at 0%, 25%, 50%, 75% & 100%; with Ruby offering first escalating resistance that must be overcome with increased manipulation or savagery, and then breaking entirely under your abuse.
These gates can also be used to make it simpler to trigger the evening visits based on the CNC stats (which will over-ride non-cnc stuff until Ruby "Recovers"), allowing for 8 new evening visit scenes; as Ruby either play-acts rationalising what you did and recovers some trust in you, OR tries increasingly desperate attempts to get you to stop.
Depending on whether her "break" or "recover" is highest. These I can set to test for a trigger every night, and then after you leave the CNC pathway I can leave replays to be accessible on the currently blank Monday night.

It's going to be a fair bit of work to get it all in place, but once it is it'll be developable concurrent with the other content. But since it'll be a slog and one I can hide behind a single set trigger I will take breaks from it occasionally so I can get the next Academic (train and punish) steps (along with the study BJ) into the game.

Anyway, enough boring Dev talk.
Here's another spanked MILF, because spanking and MILFs, and posts and so on.
I think Kali likes this treatment a LOT more than Willow did.........
View attachment 5253267

All good, but don't you think you're steering this project right into scope creep territory? You're constantly announcing adding this or that... yet so far the existing gameplay loop consists of a bunch of repetitive tasks, unfinished punishment system and hotdogging + baby-stepping BJs. Plus persistent bugs here and there.

Why not finish what's already there and then think about adding new features? Get rid of the 'not implemented yet' stuff first. CNCNCNCNC can wait.

 

[Fatbot]

All good, but don't you think you're steering this project right into scope creep territory? You're constantly announcing adding this or that... yet so far the existing gameplay loop consists of a bunch of repetitive tasks, unfinished punishment system and hotdogging + baby-stepping BJs. Plus persistent bugs here and there.

Why not finish what's already there and then think about adding new features? Get rid of the 'not implemented yet' stuff first. CNCNCNCNC can wait.

This is actually a potentially solid choice.
I could roll out the rest of punishment and training far quicker this way.
And then do the CNC at the end, possibly as an entirely separate loop rather than integrated as it is currently intended.

There is a but though, and not the fun kind.

The rate of art roll-out is, due to budget constraints, very slow. So the quicker I push through the training content the more shitty proc-gen I have to squeeze in to placeholder it all amd the larger the gap between coded and completed content gets.
Assuming I went hard through Xmas I could probably roll out all of the training and sex written content for Ruby, the frameworks for it all are in place now so it's mostly just a case of bulk creative writing and bugfixes.

The trade-off there is that in that time I'll be able to afford 2 more commissions from DK.
And most of the generic sprites aren't even done yet, let alone the NSFW content.

If I don't pace the content releases to the art I'll end up with the game sat in a hugely prolonged period of "wait for new art" with no new content.

Also if there's a persistent bug please let me know where and I'll fix it.

And here's where my inexperience in this field comes in, because this is my first time making something as I release it to an audience (heck it's my first time making any game for anyone but myself at all).

I genuinely don't know what will be best for the audience overall, a paced but slow rollout that staggers content and art. Or pushing out the content but balooning the gap between the two.

Any experienced developers, or financial backers of projects with consumer end experience, wanna weigh in?

Away from PC, but CGI butt as a feedback reward to follow.

 

[Fatbot]

Finishing off the MILF set as a feedback reward for madchef , now I'm at the PC.

 

[jwagne51]

As I did so (and grafted on new currently hidden stats and set a load of other stuff up) it occurred to me that the CNC enjoyers will have less varied sex scenes than everyone else, and so amended a previously added if hidden "broken" stat's role too.
This will allow for each CNC sex act to have 5 versions, gated at 0%, 25%, 50%, 75% & 100%; with Ruby offering first escalating resistance that must be overcome with increased manipulation or savagery, and then breaking entirely under your abuse.
These gates can also be used to make it simpler to trigger the evening visits based on the CNC stats (which will over-ride non-cnc stuff until Ruby "Recovers"), allowing for 8 new evening visit scenes; as Ruby either play-acts rationalising what you did and recovers some trust in you, OR tries increasingly desperate attempts to get you to stop.
Depending on whether her "break" or "recover" is highest. These I can set to test for a trigger every night, and then after you leave the CNC pathway I can leave replays to be accessible on the currently blank Monday night.

So from my understand CNC stands for Consensual Non Consent which means it's the sub that determines if it's actually CNC instead of NC. And if they don't explicitly say you can do that then it's just plain Non Consent or coercion.

 

[madchef]

So from my understand CNC stands for Consensual Non Consent which means it's the sub that determines if it's actually CNC instead of NC. And if they don't explicitly say you can do that then it's just plain Non Consent or coercion.

Basically, CNC is a relatively new fashionable term for rape-play, or a 'no safe word' scenario. The kink community prefers to use this innocuous acronym to the latter, older term, which might be triggering to some, apart from sounding incriminating.

 

[Fatbot]

So from my understand CNC stands for Consensual Non Consent which means it's the sub that determines if it's actually CNC instead of NC. And if they don't explicitly say you can do that then it's just plain Non Consent or coercion.

Yeah, hence the up-top discussion of character consent and the re-iteration that Ruby's into it when sex acts and the option are explained during the tutorial.

I mean, she's an illustration of an alternate version of a cartoon character, so she can neither consent nor be harmed obviously.

But as I write this I like to picture the whole thing as Ruby and the MC playing out a corruption/coercion scenario that they are both enthisiastic and excited participants in.
They're just super method about it.
And could end if (although it is of course impossible) their play exceeded either player's boundaries (and Ruby can get quite demanding and depraved as you level up her invisible stats and reward her, so it's hypothetically possible both directions in this fantasy scenario).

Basically, CNC is a relatively new fashionable term for rape-play, or a 'no safe word' scenario. The kink community prefers to use this innocuous acronym to the latter, older term, which might be triggering to some, apart from sounding incriminating.

CNC isn't nescessarily a "no safeword" scenario, it's just that most consent models expect more explicit expression of prior consent and more careful discussion of prior actions and check-ins etc.
CNC doesn't always, but can (IMO should) have an escape option.
And needn't even include sex, CNC can extend to expressly consenting to a punishment you hate but accept as necessary (as an example), even though that is how we're using it here.

Kink has a LOT of consent frameworks, which makes sense given how easily it could slide into a traumatising experience without them.
All of which are both valid for some, and open for valid criticism.
Personally I prescribe to RACK (risk aware consentual kink) because I'm of the opinion that "safe" is a relative term and too open to misunderstanding between partners; and because nothing is without an element of risk, being more aware of it is ultimately safer than blanket labelling some activities safe and others not.

 

[Fatbot]

Longer between posts than usual, sorry about that.
I'm working on Ruby's 2nd levels of training and punishment in the Study, as I slowly roll through all the tags and triggers for CNC.
Meanwhile the Patreon is filling up, so we're only about $15 away from the next art commission.
Currently I'm thinking the over-desk content for the study.
All quietly rattling away behind the scenes.
This sadly means no update, but since we had a really thoughtful session of both feedback and discussion I thought I'd chuck out another AI doodah as well
Continuing our milf run here's what Stable Diffusion thinks Summer Rose would be like if she'd survived.

 

[Fatbot]

Family visits are wonderful fun, but making pornography in the same room as your septuagenarian mother while she watches her shows is NOT something I personally want to try.
Hence the radio silence for the last 3 weeks
She's away without me today, but then it's another 3 weeks :O
So this is a VERY slow period.
None the less I've made good use of the day of freedom to get in touch with Darkkitsu and commission the art for Ruby's tied over desk spankings
Now onwards to getting more of the Coursework and Tied Kneel on Chair written content done
It'll probably be a month before I drop anything of substance, and 3 weeks more of little to no comment from me, but at least we'll get two new written activities AND new NSFW art out of it

On the subject of NSFW art, Ruby's readying herself for the "fun" to come.
Something she may regret......