i don't see how voluntarily initiating an optional threesome with two sex workers would be considered that but whatever
PLAN B
- Thread starter B
- Start date
Some people tend to lose their mind when Cait is fucked by anyone else than the Champ, they really really really want her to be their exclusive waifu.
I read through the document. Very well written. Nice touch with Nikol's personalities changing the scene. I corrected any typos I found and left some suggestions. I don't know if you ever really read those in the public version. Some are just opinions, maybe they help, maybe they don't... maybe they're the insane rantings of a madman.
he's literally a whore tho, like he isnt dating us or anything
a follower of mallach, who said that even their weddings are...questionable in terms of fidelity and non-c u c k ing?
They're like baby birds, they imprint on the first woman they see in game and get offended she's not your waifu. It's pretty quiet about it here most of the time, but some other places talking about the game absolutely hate Cait for not being Champ only.
Never understood the Cait hate, you literally can opt out of her content, and the one scene prior to that discussion you do have with her is because you take a transformative before a big confrontation so she wants you at your best (which you can still say no to). Would I like Cait all to myself? Sure. But there are already plenty of devoted characters in the game. "Whaaaaat? There is polyamorous characters in my game that pushes me to be polyamorous in? IMPOSSIBRUH"
And that is only including companions. There are so many waifu NPCs out there, while the husbando/futa enjoyers out there can count their loyal spouses on one hand.
I don't have the numbers to check, but it is pretty funny how many fuckable men/futas have harems of their own.
oh, no hate for cait at ALL, i just find it weird that someone would be like "thats my WOMAN" about her when she is, ya know a mallachite priestess
Wasn't directed at you, but just in general in concerns to the conversation at hand.
I personally hate the content type in question regardless of the way it cuts to the point that the only northern cowgirl you can penetrate has is it I find frustrating.
That said, its very odd that Cait would be involved in such conversations. She will literally not sleep with you until you agree you understand that she sleeps around and is unlikely to stop as such behavior as her actual religion. I can only fathom true cuc content for Cait as being a particularly nasty bad end ranging closer to full Nice Time for Roo with mind break shit or something else horrific.
can we stop shitting up b's thread? i'm so sorry for opening pandora's box
I'm mostly not into that content either, but I actually like that couple, especially since the male in question is a cute femboy that you can also plow. I honestly view them more as a triad relationship, rather than just that content - or rather it kind of develops in that direction, but at least everyone enjoys it and it is consensual with them.
Fair. I was waiting for it to get too far, happens when everyone wants to put their 2 cents down... we already made a dollar boys and girls, goal has been hit!
Last edited:
It's okay! It's driving discussion that's related to my content and nobody's being an ass about it. Besides, I'm the one that invited it with that last comment.
Neither of them have been reviewed yet. Neither has Agni's expansion, which has been completed for six months now.
Updated Nikol x Cait with 2,000 words! Between Nikol's dominance, PC's blobishness, and even at least one Cait parser, this is all foreplay. Penetration ought to be next update!
Priority tends to be given to projects that are particularly gigantic in scope - Berwyn, which came with a conclusion to a long-running quest and had a dungeon; Knot Cave; etc - and content that's needed to fill out a newly- or shortly-to-be-implemented area. Kailani got through the pipeline at a decent clip because she was filling out the Windy Peaks. Nikol's base content got through quickly, too, for the same reason. My sex content for Eryka and Astraea got through lickedy-split because they were short and uncomplicated.
Meanwhile, base Zo, Ivaze, Lyric and Tall Lyric, Oma, they're all huge and have dedicated internal systems and logic and none of them filled or are filling a short-term need, so they are thus not important. In devchat, when a coder says that they're free up and ask if there's anything they could do next, they're going to be told to do the smaller stuff before the bigger stuff. Tall Lyric is both complicated and unimportant, so it's pretty natural that they're going to fall down the to-do list until there's nothing else left to-do.
On top of all of that, I'm frequently told that my documents are a pain in the ass to understand from a coding perspective. I'm actually trying to learn javascript on the side because of that.
All that said, if I'm honest, it does get a little grating sometimes. Zo's base content was in there for something like eleven months. They straight-up forgot Nykke 1.0 back in the day and we only realized after Geddy happened to screencap the Trello review queue during a stream one day. I wrote Christmas content for TiTS's Lorelei in December but that was passed over and probably won't see the light of day until next winter. Agni's expansion was even pushed down the Really Big Project priority list recently, so it's not first-come-first-serve. Oma took over a year and I actually started getting really agitated over that. There's logic and reasons why my content takes such a long time to even be reviewed, but I'm not going to pretend that I'm immune to it. A year to be sitting in a queue is a long time and I'm not spending days of my life writing these things for just a paycheck; they're written to be read.
Well, I rarely make a small project. Everything I write is typically several dozen pages long at minimum. Zo's Colosseum content, while roughly eleven pages, still ranks as a 'medium'-sized submission by internal standards, and, being combat content, it's not going to be in-and-out simple to code. I'm also not on the payroll, so my work is still considered community-submissions, even if I'm paid directly by Savin.
Priority tends to be given to projects that are particularly gigantic in scope - Berwyn, which came with a conclusion to a long-running quest and had a dungeon; Knot Cave; etc - and content that's needed to fill out a newly- or shortly-to-be-implemented area. Kailani got through the pipeline at a decent clip because she was filling out the Windy Peaks. Nikol's base content got through quickly, too, for the same reason. My sex content for Eryka and Astraea got through lickedy-split because they were short and uncomplicated.
Meanwhile, base Zo, Ivaze, Lyric and Tall Lyric, Oma, they're all huge and have dedicated internal systems and logic and none of them filled or are filling a short-term need, so they are thus not important. In devchat, when a coder says that they're free up and ask if there's anything they could do next, they're going to be told to do the smaller stuff before the bigger stuff. Tall Lyric is both complicated and unimportant, so it's pretty natural that they're going to fall down the to-do list until there's nothing else left to-do.
On top of all of that, I'm frequently told that my documents are a pain in the ass to understand from a coding perspective. I'm actually trying to learn javascript on the side because of that.
All that said, if I'm honest, it does get a little grating sometimes. Zo's base content was in there for something like eleven months. They straight-up forgot Nykke 1.0 back in the day and we only realized after Geddy happened to screencap the Trello review queue during a stream one day. I wrote Christmas content for TiTS's Lorelei in December but that was passed over and probably won't see the light of day until next winter. Agni's expansion was even pushed down the Really Big Project priority list recently, so it's not first-come-first-serve. Oma took over a year and I actually started getting really agitated over that. There's logic and reasons why my content takes such a long time to even be reviewed, but I'm not going to pretend that I'm immune to it. A year to be sitting in a queue is a long time and I'm not spending days of my life writing these things for just a paycheck; they're written to be read.
The prose to code translation can be awkward. The more variables, the more every tangent or branch needs some sort of explaination. Which means endless notes and comments breaking things up and making it a hard read.
But equally. Approaching it from code first, can make it a gramatical mess when it finally gets on screen.
Swings and roundabouts.
But equally. Approaching it from code first, can make it a gramatical mess when it finally gets on screen.
Swings and roundabouts.
