CTI - Community

{
  "actions": [
    {
      "start": "draw",
      "type": "instruction",
      "fors": "instant",
      "action": "1/3/3",
      "until": "type:picture"
    }
  ]
}

Rothaon wrote:Untils aren't trigering now. :')

Code: Select all

{
  "actions": [
    {
      "start": "draw",
      "type": "instruction",
      "fors": "instant",
      "action": "1/3/3",
      "until": "type:picture"
    }
  ]
}

Rewinding isn't that necesary if it's causing troubles.

Rothaon wrote:Untils aren't trigering now. :')

playsafe wrote:If you're searching for new ideas to enhance your program, you could add a "suggested amount of pictures" feature to it. But it's rather unimportant.
One thing I'd like to see in all the programs here would be audio feedback, eg a sound when a picture is changing and a different one when an instruction card was drawn. That way one could watch a video without having one eye on the slideshow.

Rothaon wrote:How is start: start supposed to work? From my tests it works like start: draw

Rothaon wrote:Also the delay parameters seems to be ignored.

Rothaon wrote:I'm trying to get a way to separate allowed cums from forbidden ones

Rothaon wrote:PS: I just noticed that conditional only stops the code from running, not the card from showing. I gues it's how it's supposed to work, but it may be worth noting it int he wiki

Rothaon wrote:Edit: With slidetime the * and / operators seem to be doing to math in ms. *2 chancges 10s to 20000s and the / just makes it 0 xD

Simon wrote:

Rothaon wrote:I'm trying to get a way to separate allowed cums from forbidden ones

If you give explain this in a little more detail I might be able to help you

{"actions":[{"start":"start","type":"chastity","action":"true","fors":"type:picture","until":"type:cum:ruin"},{"start":"start","fors":"instant","type":"instruction","action":"Start","until":"type:cum:ruin"}]}

{ "actions":[{"start":"draw","type":"strokecount","action":"+1","fors":"type:cum:ruin","until":"type:cum:any"},{"start":"draw","fors":"instant","type":"instruction","action":"SC +1 When you get a ruined orgasm. Until you cum, edge or ruin.","until":"type:cum:any"}]}

Rothaon wrote:I'm not quoting everythinig

Rothaon wrote:I forgot to add that you should avoid slidecount going below 1. Or 0. Actually I think that if slidecount gets to 0 you just skip to the next instruction.

Rothaon wrote:- Until the end of the tease if you edge, get into chastity.
- SC 20 If you edge before next instruction get into chastity. Then get back to whatever your SC was.

The 1st one would use fors:type:cum:edge until:end
And the 2nd one fors:type:cum:Edge:force until:type:instruction

But if you encounter them both, both will fire, even if you're forced to.

Rothaon wrote:Post testing stuff: Start cards aren't show. The picture itself. I don't care much about the picture itself but it would be good for instructions to be shown, so they know what is going on.

| +

Code: Select all

{"actions":[{"start":"start","type":"chastity","action":"true","fors":"type:picture","until":"type:cum:ruin"},{"start":"start","fors":"instant","type":"instruction","action":"Start","until":"type:cum:ruin"}]}

Also, if one start card is chosen twice, there's no way to know. (I was chasing a multiplier bug and it was just this. xD )

Rothaon wrote:Instruction where the fors is the same as the until seems to not be triggering.

| +

Code: Select all

{ "actions":[{"start":"draw","type":"strokecount","action":"+1","fors":"type:cum:ruin","until":"type:cum:any"},{"start":"draw","fors":"instant","type":"instruction","action":"SC +1 When you get a ruined orgasm. Until you cum, edge or ruin.","until":"type:cum:any"}]}