- Jun 17, 2017
- 5,685
- 28,710
I've been working on coding a 'capture' routine for at least one girl (Stargirl), so that others can see how I had intended for this to work.
Essentially, once Batgirl, Black Canary and Huntress are captured, Stargirl is added to Roulette's 'recruit list', and once you've talked to Roulette about her, she's 'moved' to Lex's 'recruit list' until you visit the Lexcorp Labs, at which point Lex tinkers with stuff and she's then added to the 'target list'. The associated dialogues are in Stargirl.rpy, under label Stargirl_recruit.
This is how I intended for each Heroine to be handled, i.e. all associated conversations would be in the associated label Girl_recruit, and all 'moves' between various 'list pools' handled there once she's been 'flagged' as an active potential target.
This still requires an 'initial handshake' which is currently being handled in script.rpy, but for 'new' girls I had intended for an 'initial recruit check' to be made when a new folder is added to /girls for a new girl. Essentially the girl would have been added to a 'pending girls' list, and then each night the pending girls list would be checked for conditionals to see if she should be 'flagged' at that point in time.
This would allow people to just 'handle' everything in that girl's .rpy file, and the person that created that girlpack could set whatever conditions they wanted, example:
nightly check for new pending girls, if girl in list...
I haven't tested this specific code example (so it may need a bit of fine tuning, I'm just sharing the idea here), but this is the general idea r.e. how to 'contain' recruit text inside of each girl's individual .rpy file, hence avoiding the need to touch talshop.rpy, script.rpy etc.
Again, this is to enable anyone to add any girl at any time, as long as they follow the 'rules of recruiting'. Also, the folder detection routine would need to be re-enabled (it's commented out in the code in script.rpy currently, 'cuz lint didn't like it, but I did test it previously. There's probably a cleaner way to do what I was trying to do, I coded that about 4-5 months ago and have learned a few things since then).
I'm also adding an example of 'first time this menu has been visited' text for the Devices interface in the Lexcorp Labs. This is essentially 'tutorial' text that explains how the Lexcon AI Mind Control Devices are handled, i.e. which screens you can purchase devices, and how to upgrade the devices.
I had intended to add 'click to upgrade device' functionality for each girl to the Assignments screen, but that'll have to wait for now. The Heroine Profiles screen has that functionality already.
Anyways, yeah just taking a bit of time to include examples of how things could work, at least as it relates to how I envisioned such things.
Essentially, once Batgirl, Black Canary and Huntress are captured, Stargirl is added to Roulette's 'recruit list', and once you've talked to Roulette about her, she's 'moved' to Lex's 'recruit list' until you visit the Lexcorp Labs, at which point Lex tinkers with stuff and she's then added to the 'target list'. The associated dialogues are in Stargirl.rpy, under label Stargirl_recruit.
This is how I intended for each Heroine to be handled, i.e. all associated conversations would be in the associated label Girl_recruit, and all 'moves' between various 'list pools' handled there once she's been 'flagged' as an active potential target.
This still requires an 'initial handshake' which is currently being handled in script.rpy, but for 'new' girls I had intended for an 'initial recruit check' to be made when a new folder is added to /girls for a new girl. Essentially the girl would have been added to a 'pending girls' list, and then each night the pending girls list would be checked for conditionals to see if she should be 'flagged' at that point in time.
This would allow people to just 'handle' everything in that girl's .rpy file, and the person that created that girlpack could set whatever conditions they wanted, example:
nightly check for new pending girls, if girl in list...
Code:
if len(pending_girls) > 0:
blah blah code while i < len(pending_girls):
$newrecruit = pending_girls[i]
jump expression newrecruit + "_recruit"
---
label Amazonia_recruit:
if WonderWoman_corruption > 27 and Amazonia_chat == -3:
"As Lex is waking up, Roulette sends him a text message "Ask Wonder Woman about rogue Amazons..."
"Lex goes to Wonder Woman's cell, and blah blah she tells him about Amazonia. She mentions that Tala might know more about her..."
$Tala_RecruitList.append("Amazonia")
$x = pending_girls.index("Amazonia")
$pending_girls.pop(x)
$Amazonia_chat = -2
#Then when you talk to Tala about girls, the Amazonia conversations begin, essentially a menu option for Amazonia appears, which jumps you back to Amazonia_recruit...
elif Amazonia_chat == -2:
tala "Yez, I've heard of this girl. Give me a few days to rezearch zhis..."
$Amazonia_talk_day = day
$Amazonia_chat = -1
elif Amazonia_chat == -1:
if Amazonia_talk_day > day -3: #Tala needs 3 days to research this.
tala "I need more time, baby!"
else:
tala "I found her! You vill need zhis talisman to capture her..."
$Amazonia_chat = 0
$x = Tala_RecruitList.index("Amazonia")
$Tala_RecruitList.pop(x)
$target_list.append("Amazonia")
---Again, this is to enable anyone to add any girl at any time, as long as they follow the 'rules of recruiting'. Also, the folder detection routine would need to be re-enabled (it's commented out in the code in script.rpy currently, 'cuz lint didn't like it, but I did test it previously. There's probably a cleaner way to do what I was trying to do, I coded that about 4-5 months ago and have learned a few things since then).
I'm also adding an example of 'first time this menu has been visited' text for the Devices interface in the Lexcorp Labs. This is essentially 'tutorial' text that explains how the Lexcon AI Mind Control Devices are handled, i.e. which screens you can purchase devices, and how to upgrade the devices.
I had intended to add 'click to upgrade device' functionality for each girl to the Assignments screen, but that'll have to wait for now. The Heroine Profiles screen has that functionality already.
Anyways, yeah just taking a bit of time to include examples of how things could work, at least as it relates to how I envisioned such things.
Last edited:
