tigrotto wrote: ↑Wed Jan 31, 2018 2:40 pm
Just an information: can we add end scripts to HoT?
If yes, do they need to have a particular structure?
Thanks!
Well, there a few things you can miss with other ends, like the fetishes and some variables changing something, but the most important parts you need to include are:
Code: Select all
@NullResponse @DeleteFlag(AV_CrashReport)
and
@Flag(AV_DecOrg) @NullResponse @IncreaseOrgasmChance
@Flag(AV_IncRuin) @NullResponse @DecreaseRuinChance
@Flag(AV_IncOrg) @NullResponse @DecreaseOrgasmChance
@Flag(AV_DecRuin) @NullResponse @IncreaseRuinChance
@NullResponse @DeleteFlag(AV_DecOrg, AV_IncRuin, AV_IncOrg, AV_DecRuin)*
* I think I included that line in the start script too, but it's a good idea to keep there.
The new update will have a variable to keep track of the orgasm/ruin/denied ends. So, if you want to make compatible already, you need to include this in the @OrgasmDecide parts:
@ChangeVar[AV_EndDenied]=[AV_EndDenied]+[1]
@NullResponse @SetVar[AV_EndCum]=[0]
@NullResponse @SetVar[AV_EndRuin]=[0]
You need to do +1 for the actual results, and reset the others (you need to make for all 3 results).
I only created a few lines using that (in the start module), but could be useful in more places.
ABOUT THE MEMORY UPDATE
I am still fighting with the MissBlue modules
. Just add a @RamdomLink did not work. The fact is, if a module just have @NullResponses till a @CallReturn, TeaseAI will think just a @CallReturn happened in the stroke cycle.
I will need to put a single line, in the first line of the modules with something like "aaand, almost there, etc" to trigger the module.
And I have a few new ideas about the memory part.