It’s been strangely sunny these past few days (normally, the winter is several straight months of rain - it’s the most “British” thing about British Columbia), and I’m not sure if I enjoy it or not.
I also pushed a new build to my playtesters this morning, with about 25k words of new content, so I’m currently under a barrage of “yo, everything’s broken” reports.
I really miss quicktest.
What happened to quicktest? Or is this for a non-ChoiceScript game?
Shadow of the Eagles is in Twine, so yeah, bit different.
I’ve never used twine, so I don’t know if this is helpful, but some folks on the intfiction forums were talking about automated testing methods for twine.
That’s why I enjoy using ren’py. 
Note to future writers, Never ever try to retcon a character. Especially doing something as dumb as making them gender selectable or gender dependent if they have been in a lot of scenes and mentioned a lot.
That kinda sounds like a continuation to “don’t write a series”.
If the story potential wasn’t good enough for me to bear with it, I would cancel it and strangle my past self. I might still strangle my past self if it were possible tho.
Okay I am working on something currently, I want to do genderflipping with ROs, What is a good method for handling this, I understand choicescript for the most part but I have a big question
Is it better to do if/else labels based on gender or create variables for pronouns? What do you prefer to do personally?
Any advice or opinions on this will greatly help!
Depending on if the script for the gender flavor changes drastically or not, multireplace will be your best friend. if/else is nice for multiple paragraphs or the need to use multireplace for different variables (since multireplace cannot be nestled into multireplace).
Setting up a variable for the character gender try :
*create char_boygirl 1
*create plural false
*comment 1 = male 2 = female 3 = nonbinary
@{char_boygirl He | She | They} @{plural eat | eats} the apple.
That would show up as: He/She eats the apple. or They eat the apple.
There are other and probably easier ways to go about it, but that’s the method I’ve managed to get working lol.
I hope it helps make things a bit smoother than typing out full *if statements the entire time!
ETA: Because I like to abuse multireplace, I also sometimes (more like always) just use it for longer text that doesn’t include any other multireplace. For example:
@{char_boygirl He sits on the wooden chair. "Nope. That chair is too hard." So, he tries the next one. | She braids her hair, staring at her reflection with a small look of disdain. "No, no. I need to try that again." | They dance to music, feet flying as if carried by wings. Someone throws coins in their direction.}
As long as you don’t need paragraph breaks, it works nicely, though I guess sometimes the downside is that it’s less legible during editing, particularly if you have a lot of variations.
I do add some flavor changes for gender but I generally go with IF statements (If that is the case) but I will try your suggestion!
Personally, I do a mix of both depending on what the situation is, if it’s a big scene then I use if and else since I want the male and female versions to be different. If it’s a small scene then I just use variables.
Yea thats what I am looking at doing for the most part!
solid plan, if it isn’t broke then don’t fix it.
I’d suggest using a variable for common varied words such as ${he} or ${they}. Multireplace is fine but having to type it out every time has more chance of typos or other errors.
This is broadly how I do it:
Where there are bigger changes, I tend to use if/else blocks when writing as I personally find it more readable, and then change it to multireplace once I’ve finished the paragraph. (As mentioned you’ll only want to use multireplace if there isn’t a line break, though.)
This is one of the major reasons my Twine games are under 20,000 words or so. Best of luck bug squishing! 
To add on to @HarrisPS, I tend to have a lot of variables that will adjust most plural words on the fly without a multitier replacement. My issue with using @{Gender he's | she's | they're } is that I might misspell one of the three words once, and QuickTest won’t catch it, but if it is a single variable like ${HeSheS} it will.
*set GHimHer {GenesisGender&"HimHer"}
*set GHeShe {GenesisGender&"HeShe"}
*set GManWoman {GenesisGender&"ManWoman"}
*set GMenWomen {GenesisGender&"MenWomen"}
*set GHisHer {GenesisGender&"HisHer"}
*set GHisHers {GenesisGender&"HisHers"}
*set GMrMs {GenesisGender&"MrMs"}
*set GSirMaam {GenesisGender&"SirMaam"}
*set GMaleFemale {GenesisGender&"MaleFemale"}
*set GBoyGirl {GenesisGender&"BoyGirl"}
*set GGender GenesisGender
*if GHeShe = "they"
*set GHeShes "they're"
*set GHeSheIs "they are"
*set GHeSheWas "they were"
*set GHeSheHas "they have"
*set GHeSheGives "they gave"
*set GHisHersIs "theirs are"
*set Gs ""
*set Ges ""
*set Gies "y"
*else
*set GHeShes (HeShe&"'s")
*set GHeSheIs (HeShe&" is")
*set GHeSheWas (HeShe&" was")
*set GHeSheHas (HeShe&" has")
*set GHeSheGives (HeShe&" gives")
*set GHisHersIs (HisHers&" is")
*set Gs "s"
*set Ges "es"
*set Gies "ies"
example of it used:
The stale air of the room is suffocating. I attempt to open the door to the next room, but the door does not open. Genesis has the same issue when ${GHeShe} tr${Gies} to leave.
Yeah, over time I’ve started going for things like ${pthey} ${ptry} or similar which has reduced my errors a massive amount as well as being easier for me to type.
I almost did it like that! But then I started to think of other ies/y ending words that might come up and decided I’d rather have a variable just for swapping those letters. This way I can write ${HeShe} part${ies} all night long without making a multitier exception or a variable just for that word.
Definitely, whatever works best! I’ve seen others do it that way too.
In other news, when writing this morning I realised that one of the planned polyamorous configurations for the secret project just doesn’t make sense with the personalities and principles involved. But a different one does make sense, hooray! (This game will likely have… certainly two, likely three polyamory options by the time it’s done, so players who are really into certain characters will be able to open up different kinds of relationships with them. It’s interesting doing this with non-gender-selectable characters, as I’ve only ever written it with selectable ones before.)
My goal for the final few days of January is to either get to 300K words, finish the “festival” sequence I’m working on, or both. Preferably both, but it’s hard to maintain quick pace with all the exams I have to deal with.
i’m excited to see your set-gender ROs when the time comes!! i’ve loved all the gender-variable ones in your projects, of course, but your writing has such good exploration of transness and queerness in general that i’m excited to see it all done with set-gender characters.