Greetings, first time poster, long time lurker.
So, let me start by saying, this program, is amazing. It's really cool, and i've been trying it out ever since release.
Lately, i've started tinkering with my own scripts, after before usually just fixing typo's and bugs in other people's scripts.. or rigging chances... or *cough* removing chastity *cough*.
Anyway, the inclusion of the glitter contacts and the possibilities have made me pick up writing my own scripts, and it's pretty straight forward to get into. (At least for me, i'm a programmer, so something as 'simple' as writing scripts is not that hard to understand)
However, i've stumbled over a roadblock, involving the glitter commands.
When running a script that has a question asked and the answer being by a glitter contact, like so:
Isn't that great?
[yeah] @Contact1 #EmoteSmile We'll have lots of fun together!
[nope] @Contact1 Well, tough luck, because i'm here to stay #PetName #EmoteSmile
@AcceptedAnswer @Contact1 It's fine it's fine, just go already #ShortName. #EmoteSmile
This script, when answering, will make it skip all lines, and proceed as if i answered a question way further down the line.
This will conistently keep happening, untill it suddenly finds an end point. Or it stabilizes by getting into a section where the (main) domme is replying to the question.
This particular script will run the reply command of what i just linked, But will read the @Goto command (but not the actual reply itself) of a different question.
So this particular question, makes the programn continue as if you answered:
@Contact1 Sounds good?
[yes] @Contact1 #EmoteHappy @Goto(Accept)
[no] @Contact1 #EmoteAww @Goto(NAccept)
@DifferentAnswer @Contact1 #YesOrNo
I think it just picks whichever answer you picked, so first or second, even though the actual keywords are different for the answer. But that is my observation thus far.
I haven't really discovered a pattern other than that it seems to pick questions that have a @AcceptedAnswer or @DifferentAnswer as its go to point, and it appears to simply be the next in the text file.
I know the glitter incorporation in main modules are still in the work, so i've build in work arounds to try and deal with not being able to use @Edge for instance. And the keyword Close is off limits as well.
So in my case i use:
@Contact1 #Edge
[on edge] @Contact1 #StopStrokingEdge
Which suffers from the same problem, that it skips ahead.. probably the same problem as the one i described above.
Some of the other scripts ive made using the main domme work fine. It just gets messy, and not in a good way, when incorporating the glitter contacts in main modules
Lastly, i'd have a request to be able to run commands in glitter modules. I was tinkering around with writing a script where the domme would allow the glitter contacts to 'vote' wether you get to cum or not. By using 3 variables. A CumRequirement, A CumCounter and an AnswerCounter.
Example: CumRequirement is 4, meaning you'd need 4 points to get to have an orgasm. And say 2 (half) to get a ruined orgasm.
The cumcounter starts at 0.
The main module will enter a loop, waiting for all glitter contacts to have answered to the domme's call. (which reminds me, it would be nice to be able to force this. Since they dont always seem to all respond, even if you set post frequency on max)
The glitter script would be:
What do you think girls? Can he come?
@Contact1 Hmmm.. nope. Let him suffer some more. #EmoteSmile #Answers+1
@Contact1 Only if he covers my #Face with his #Cum. #EmoteMoan #CC+2 #Answers+1
@Contact1 No just edge him endlessly. #EmoteLaugh #Answers+1
@Contact1 He can, but it has to be ruined... #EmoteMoan #CC+1 #Answers+1
@Contact1 I'd ruin him all over my #Ass #EmoteLaugh #CC+1 #Answers+1
@Contact2 Hmmm.. i wish i could #Swallow all of his #Cum, spraying it all over my #Mouth. #EmoteMoan #CC+2 #Answers+1
@Contact2 Dont let him shoot his #Cum. Make him #Surrender. #Laugh #Answers+1
@Contact2 I want to see him cover #ShortName her #Chest. #EmoteMoan #CC+1 #Answers+1
@Contact2 Let him ruin it all over your #Face. #Laugh #CC+1 #Answers+1
@Contact2 I want his #Cum inside of me... #EmoteMoan #CC+2 #Answers+1
@Contact3 Hmmm i'm #Fantasizing about you #Swallowing his #Cum #ShortName #CC+2 #Answers+1
@Contact3 No.. make him #Beg first. #EmoteLaugh #Answers+1
@Contact3 Only if he ruins it. #EmoteSmile #CC+1 #Answers+1
@Contact3 I'd milk him inches away from my #Face, only to then let him ruin it. #EmoteSmile #CC+1 #Answers+1
@Contact3 If you let him cum, save his #Cum for me. I'll #Swallow it next time we have our session. #EmoteMoan #CC+1 #Answers+1
Now basically, each glitter contact has 5 possible answers. They all up the Answer count by one. So the loop will know when to end. And depending on which answer they chose, you'll get either 0,1 or 2 points. Excuse my usage of #CC and #Answers etc, there used to be @ChangeVar in there, but i tried to find a workaround by putting the actual ChangeVar statement in a response file, figuring maybe that would do the trick.. it didn't. So #CC is in fact a @ChangeVar(cumCounter) = @ChangeVar(cumCounter) + 1 or 2 respectively.
The main logic in the module would simply be in a loop waiting for the answer variable to reach 3, then it would compare the cumCounter to the cumRequirement, and send the user off from there.
After appearing to not have made any typo's whatsoever, and by manually observing the state of each variable, i noticed it doesn't appear you can use these commands in the glitter app like that, so my idea got kinda shut down. None of the variables changed based on the glitter app responses.
If it helps my scripts are all run with the Swiss personality. Since well, i like that one the best.
I'm probably able to further answer any question, and/or run a trial if you need to know something. And you can PM me if you want.
And thats it for my first post, phew, quite a long one. (Ahem Ladies..)
All in all i'm amazed by this program thus far, and ofcourse it's still in beta. But it's already amazing.