[BUG] What's to come?

[SethK]

There a bug in the tease "What's to come?":
https://milovana.com/webteases/showtease.php?id=51047

After you pick how many edges/hits you have left the tease does not continue but hangs. So, dark0512 if you are reading it could you fix this please? (I haven't found a thread for this tease, that's why I went ahead and created this one.)

[dark0512]

Do you remember how many it said you had left or does it freeze before that?

[SethK]

It hung before that. I've tried it two times, ones with numbers I cannot remember and the second time I figured I would go with 15 and 30. The reason for this is that 5 edges were followed by 10 ballbusts which led me to believe that I might be fine with those values.

[dark0512]

I tried to look at it yesterday but didn't have time to figure out what's causing the issue.

Can you try it with the same number of ballbusts vs edges? (like 15 and 15, or something like that)? I think I know what's causing it and wondering if that number needs to be equal.

[fapnip]

I tried to look at it yesterday but didn't have time to figure out what's causing the issue.

It's on page '21-punishBalls-1'

In your last "IF" action, your condition is "punishEdges < 1;" note the ";". Can't have those in conditions. Drop the ";" and it should work.

(A quick glance through your tease's JSON shows you have another ";" in an IF condition on page '9-Variables': "varCock >= 1;"
-- That IF will also crash.)

Also, you're allowing players to enter numbers, but not really validating them. They could enter a non-number that may make things unpredictable. You could validate the number they entered with an IF condition like:

Code: Select all

isNaN(edgesLeft)

If that evaluates true, then they didn't enter a valid number.

Another thing I noticed was that your string match condition of things like this are awfully strict:

Code: Select all

beg1 == "I am very sorry Mistress Jennifer. I will do anything for your forgiveness."

Accidentally miss some punctuation, add an extra space, or get the case of a letter wrong, and it'll evaluate false.

Using a regular expression, you can be a little more lose in matching with something like:

Code: Select all

beg1 && beg1.match(/^\s*I[ ']*a*m *(very[, ]*)+ *sorry *Mistress *Jennifer[\.,\s ]*I[' ]*w*i*ll *do *anything *for *your *forgiveness[\.,\s ]*$/i)

This would match on "I'm very sorry mistress jennifer Ill do anything for your forgiveness" as well as "I am very sorry Mistress Jennifer. I will do anything for YOUR forgiveness.", "I am very, very very sorry Mistress Jennifer. I will do anything for your forgiveness.", etc. etc.

Edit:
You could also add an extra punishment check with another IF condition of something like:

Code: Select all

beg1.match(/(fuck|bitch|pussy|suck|cock|dick)/i)

That would match any of those words in the string -- and you could decide to beat them into submission if so.

[dark0512]

Thanks!

I went ahead and made the corrections.

I will take a look at your suggestions. I greatly appreciate them. I'm not sure i'll use them in this tease, but will implement them in the tease i'm currently working on.

[sklavealex]

I had the same bug today.

I choose 40 and 20.

[SleeplessSub]

Unfortunately, the bug is still there. Too bad I only found this topic afterwards
FYI I had 18 and 10. Is there a combination that is known to have worked before?
Because I would like to see how it continues and finish this great tease