I feel like Kobold AI is a little censored
I tried out a non-consensual story and it just lead to punishment instantly/doesnt even write and just goes to the end or even turning into a greentext type story
It may have been skill issue in my prompts but it seemed to be a little bias against it
That was with Erebus 2.7B
Might be a combination of prompt/memory/AN and the type of stuff Erebus is trained on. Sometimes the AI needs a little steering to get what you're going for. The one thing I've struggled (hah!) with when it comes to non-con is that the "victim" always eventually ends up moaning in pleasure and begging for more, no matter how I set it up or guide it. That's... generally not how non-con works, but I suspect this is down to the training data used for Erebus. There might be better models for that kind of stuff, not sure.
Really? I couldn't get the AI to stop trying to show one character crying and struggling in vain yesterday. I had a pretty explicitly non-con setup though, a female knight defeated by a succubus. (I had a burning desire for a "K-kill me already!" story setup. I'm, uh, 300+ replies in now) Try using the Genre tag in the Author's Note Template in the Memory button, on the bottom left. Erebus knows [Genre: <comma-separated list of genres>] to set those. Switch them up when a new scene starts. If you give the character some written motivation and reactions in-scene as well, the AI is better at using that. Delete any mention of the character acting out of character! This is super important! The AI makes educated guesses based on context, but will continue to be a scatter-brained creative until you establish a pattern. The more unrelated content you allow to mingle, the more confused it gets. If it can't reconcile two conflicting facts, it flip flops, and that's not fun to read unless you like seeing dying AI bullshit like early AI Dungeon.
Speaking of patterns, if it starts to repeat actions you need to change things up or end the scene. Like my scene mentioning the succubus' tail wrapped around someone's leg and her wings flapping or fidgeting. Every 3 lines. I wish it would stop showing characters blushing every 10th line, but that's a hallmark of cheap smut and unrelated.
As for the Over Too Soon issue which is a classic, click Retry to re-generate the reply. Use it often! Delete parts of the reply you don't like, if some is good. If the climax still happens, check the preceding story for leading sentences. Someone's face grimacing, feeling something rising, etc, can lead the AI to make the conclusion happen immediately. You may need to rewrite a bit, or again, change up the scene a bit. Switch poses, start some dirty talk, etc.
One more bit of advice is to lower your standards a bit. Good stories have some foreshadowing, which the smutty AI Erebus simply can't handle without serious railroading, and why bother at that point if it's going to be a struggle. So instead, just say outright what's going to happen or what a character is going to do, then let the AI say how. (I had a character brew a potion late at night in secret, and the AI wouldn't stop bringing it up the next day. EVERYONE wanted to look at it and drink it or splash it on someone else or explain that it's an aphrodisiac in the next scene, until I resolved the plot thread with the brewer refusing to explain when asked.)
Lastly, get used to clarifying sentences in scenes with multiple characters with the same gender or role. "She puts her hand on her shoulder." Whose hand? Whose shoulder? The AI is gonna get confused. "Sarah puts her hand on the younger woman's shoulder." Okay, the AI now knows what's going on, and won't incorrectly assume. It gets much worse with sex involved, since the AI likes to bring actions up again or conclude them. Bad assumptions mean the dick is in someone else. Expect to need to correct characters and roles/titles too when the AI makes a mistake, or that mistake will stick around.
