Milovana.com

tBone wrote:

genome231 wrote:The folders are empty when using the link.
Shifting from mega to something else, cant seem to get that to work right...

If downloading keeps bugging I will considder (probably) do it as zipfiles.
Right now there isn't any heavy media files :)
But I have plans to introduce certain videos, audios and pictures. But it will remain plans till I get everything else working :)

Bug at chain ruin --> looking into that now.

Thanks for bugreporting

Regards

You should always zip/rar/7zip something you upload if there are a bunch of files, regardless of size.

Sub_Loki wrote:Ran into this bug

Spoiler: show

::: TYPO :::
::: FileText = F:\New folder\Scripts\SpicyTease\Stroke\End\GNMChainRuin.txt ::: LineVal = 3
::: TauntText = F:\New folder\Scripts\SpicyTease\Stroke\StrokeTaunts_2.txt ::: LineVal = 29
::: ResponseFile = ::: LineVal = 15

and she got stuck at chain ruin and it wouldn't start at all sadly :(

genome231 wrote:

Sub_Loki wrote:Ran into this bug

Spoiler: show

::: TYPO :::
::: FileText = F:\New folder\Scripts\SpicyTease\Stroke\End\GNMChainRuin.txt ::: LineVal = 3
::: TauntText = F:\New folder\Scripts\SpicyTease\Stroke\StrokeTaunts_2.txt ::: LineVal = 29
::: ResponseFile = ::: LineVal = 15

and she got stuck at chain ruin and it wouldn't start at all sadly :(

Apparently I cant reproduce your bug, which have me thinking you might be missing some CallReturns or similar.
There have been problems with the download link, and i'm working on a fix for that now. It will probably be compressed to a zipfile and shared through MediaFire but I am waiting for it to finish uploading :)

Let me know if your bug reappears with the new download.

Regards
Genome

Tepi wrote:There is some inconsistency in the scripts. One that comes to mind in some end scripts you have "@ChanceX(chastity)" when the block itself is named "(Chastity)", and I guess that's what throws an error. Also in the end scripts you have @Goto(DommeApathy) when it is actually @GotoDommeApathy, without the parenthesis.

I don't know if you already have, but it might help to keep a small note somewhere with the most used commands so you get them right, until you don't need it anymore. Would save you some work if you didn't need to hunt as many bugs.

RandomStranger wrote:Found one problem with "GNMAcceptDeal"

When asked if you feel you need training, answering yes will lead to a error and stop the current session.
Problem i think is due to a @Goto command right after the @CallReturn. After removing the @Goto it worked fine, but honestly i dont really know how these scripts work so i dont know if that causes issues with anything else down the line.

You think this works?
[yes]Excellent! @Goto(Call1)
[no]That's a shame 
@AcceptAnswer Anyways...
(Continue1)
bla
bla
bla
@End
(Call1)
@NullResponse @CallReturn(sometext.txt)
@NullResponse @Goto(Continue1)
@End

RandomStranger wrote:Found one problem with "GNMAcceptDeal"

When asked if you feel you need training, answering yes will lead to a error and stop the current session.
Problem i think is due to a @Goto command right after the @CallReturn. After removing the @Goto it worked fine, but honestly i dont really know how these scripts work so i dont know if that causes issues with anything else down the line.

genome231 wrote:Updated to 1.10

Regards
Genome

Daragorn wrote:

genome231 wrote:Updated to 1.10

Regards
Genome

Just downloaded it...i am curious to see what you have come up with

A suggestion....by looking at some of your scripts, i've seen that you have many places where you have different @Chance() on the same line, for ex. GNMChastityOff.txt where you have lines like:
@NullResponse @RapidTextOn @Chance10(Joking1), @Chance10(Joking2), @Chance10(Joking3), @Chance10(Joking4), @Chance10(Joking5), @Chance40(EasyRelease), @Goto(NoChance)

From my experience, that won't work....teaseAI will only consider a single @Chanche() and @Goto() per line....the other ones are skipped (it is a bug obviously, but i noticed it a few times).
So, in this case, for example, if it misses Joking1, it will directly use NoChance, ignoring all the other possibilities (tested it myself.....10 times in a row i always went to NoChance....).
I suggest you split each @Chance() in its own line with a @NullResponse. It will take a little more to go through it (but actually that's because now they are all being really checked )....that's how i deal with multiple chances, and it works fine.
You can have the last @Chance() on the same line as @Goto() because those will work togheter, but not more than 1 @Chance().

At the same time, if you want to have different possibilities all with the same chances to happen, you can use @Goto(line1,line2,line3,line4) <------teaseAI will randomly pick from one of those for you

For example, your link packs right now either go to the first one or, if missed, the last one (due to the @Goto()).
Chancge your:
@NullResponse @Chance08(Link1), @Chance08(Link2), @Chance08(Link3), @Chance08(Link4), @Chance08(Link5), @Chance08(Link6), @Chance08(Link7), @Chance08(Link8), @Chance08(Link9), @Chance08(Link10), @Chance08(Link11), @Chance08(Link12), @Chance08(Link17), @Chance08(Link18), @Goto(Link20)

With:
@Goto(Link1,Link2,Link3,Link4,Link5,Link6,Link7,Link8,Link9,Link10,Link11,Link12,Link17,Link18,Link20)
And it will do what you wanted it to do