Events: Once Upon a Time…(Hows and Whys of Events)

A little history on events.

Once upon a time…

I wanted a device that would help me strip on stage cause doing it manually was panicky for me.

I envisioned 3 strip events. Initially they were done manually by pressing a button for each item.  But then I got an idea to automate the process.  Less showtime stress.

And so thus were born 10 events and with it the concept of AUTO.

AutoStrip on certain events that would happen a certain amount of time into the routine after pressing play

1 remove my gloves
2 remove my top
3 remove my bottoms

But then i wanted to describe what was going on using this new feature called EMOTES.  It was new to me at the time.

So I had 3 AutoEmote events

1,I begin to remove my gloves
2,I am now going to remove my top
3,and i now dare to pull down my bottoms

All fine and dandy…Worked like a charm…BUT…

,,,the problem was that by the time you read the EMOTE and eyes returned to the stage, the item of clothing was already off and the effect of stripping was lost.

So I pouted like Winnie at having to:
1) renumber events I had and
2) having to create 3 new events…

Aafter all. I only had 10….they’re going like flies because eventually Ii will add an event to open the curtain and another event to close the curtain so soon 3 + 3 + 1 + 1….wow 8 events…almost out.  There would only be 2 left.

So on AutoStrip I did the Winnie-Renumber move…Its an old skating move (smiles).

2 remove my gloves
4 remove my top
6 remove my bottoms

Now the emotes can happen before the strip so people have time to read the emote and then return to see the actual strip

*evehts might have then look like this


The emotes happen 7 seconds before the strip allowing time to read the emotes.

Then i realized…hmmm….why not just tell the HUD to emote 7 seconds before the key event. That would save events.

And so the concept of “Lead-Time” was born. Time BEFORE an event that something happens :LEADing into the key event.

So a new entry on the *config nc was born

Now all i need is 3 events


and so strip looks the same

1 remove my gloves
2 remove my top
3 remove my bottoms

and emotes are now brainless

1,I begin to remove my gloves
2,i am now going to remove my top
3,and i now dare to pull down my bottoms

they will actually fire 7 seconds prior to the emote times of 30,60,90 = 23, 53, 83

Now mind you many people find the concept of lead-times and delay times challenging and would rather just create extra events. That is fine cause now we have 20 events. You can live and die and never use lead or delay times. Just an extra hand tool if you CAN grasp the idea.  But if it confuses you then please ignore it.

A nice thing is you can change the time of the strip and the emote automatically moves with them.

SexyS invented Lead-Time.

She used to wake up at noon for Kats noon class. But found she had no time to get there cause she could not move in an INSTANT…so she got the idea of a lead-time and set her alarm-clock 30 minutes ahead of Kats class.

She wanted to remember to get to Kat’s class at 12pm noon. So she set her alarm clock for 11:30am. She allowed 30 minutes lead-time to get to class.

Then her husband seeing how handy her alarm clock was, bought her a new SmartWatch. It queries Kats internet calendar via WiFi thru the Internet and sets her watches alarm to always be 30 minutes prior to Kats class time. So now she just goes to sleep and never has to worry if Kat changes her class time. Sexy has the new AutoKatsClassLeadTime,30 minutes set in her new SmartWatch.


That’s how the HUD works. It sets its internal alarm clock to go off not just once like Sexys SmartWatch, but several times, once for each event. Each time it goes off it checks what it needs to do. Sexys smartwatch actually has a voice command that tells her “Go to Kats Class”. (Sexy wants the next version of the watch that can set several alarms thru out the day, like the HUD, that tells her what to do all day long so she doesnt have to remember anything)

Each time it goes off it checks its checklist to see if it has anything to do…if not it goes back to sleep.

It checks if it has
1) to strip?
2) to emote?
3) to adorn?
4) to announce?
5) to autofx?

each time it goes off. It can do all of them or some of them or none of them each time an event triggers.

AutoFX was born as a catch all because i ran out of buttons. So AutoFX does “EVERYTHING ELSE” that I might think of now and in the future. You learned how to start and stop particles in class using AutoFX.

If I had space for more buttons i might have had an AutoParticles button, as an example.

I also wanted to say that way back in the day stripping was a self-contained activity.

Stuff didn’t just come off…we had an animation that made it look as if you were removing garments. And you could specify an animation or pose that happened before the actual strip and one that happened after the actual strip. Even had particles that could fire and accentuate and draw attention to the strip.

This all happened using a HUD feature called AutoPose that has since been retired. An idea before and after its time.

Because stripping was out and dancing was in. Clothes now just came off in a split second and don’t dare interrupt the main dance sequence. Don’t blink or you will miss it.  Emoting used to always happen. Now its a rarity. To each his own. Time marches on. Entertainment evolves.

Of course the HUD had no ability to sequence dances…as it was thought that you played them on the fly. I used to improvise…way back in the day.

So as people started to think of more things to ‘do in a routine’, the need for more events happened.

They asked for 15 thinking no-one would ever need more than. But i wisely decided I didn’t want to keep adding new events so I opted for 20 events.
This (lead-time) is just one way to extend the effective number of events….Kat and I were thinking of all the other ways. There may be as many as 7 or 8 additional ways that you will learn over time so do not feel limited if you are used to using another method that seems have an endless amount time segments with which to trigger activity.