So, I've been doing some research and going through various scripts...
I think one of the biggest problems with TeaseAI is nicely seen in a script like this:
@NullResponse @Flag(FirstDungeon) @Goto(Base)
@NullResponse @SetFlag(FirstDungeon)
@SystemMessage #VANC #VANP Welcome to the dungeon #SubName
@SystemMessage #VANC #VANP Here you complete punishments given to you by your #DomHonorific
@SystemMessage #VANC #VANP A punishment usually lasts 20-30 minutes
@SystemMessage #VANC #VANP Punishments are here to deter you from poor behaviour
@SystemMessage #VANC #VANP Punishments wont be fun, they wont include pain
@SystemMessage #VANC #VANP You wont love them and thats the purphase
@SystemMessage #VANC #VANP Dont forget that!
(Base)
@SystemMessage #VANC #VANP #SlaveName @If[Punishment]<[1]Then(NoPunishments)
@Variable[Punishment]>[1] @SystemMessage #VANC #VANP You have @ShowVar[Punishment] punishments pending
@Variable[Punishment]=[1] @SystemMessage #VANC #VANP You have one punishment pending
@SystemMessage #VANC #VANP Do you wish to do a punishment?
[yes] @SystemMessage #VANC #VANP #Good @Goto(Punishment)
[no] @SystemMessage #VANC #VANP Okay then @Goto(End)
@DifferentAnswer @SystemMessage #VANC #VANP Yes or no?
(Punishment)
@NullResponse @Goto(1)
(1)
@NullResponse @CallReturn(CR\Dungeon\P1.txt)
@NullResponse @Goto(Base)
(NoPunishments)
@SystemMessage #VANC #VANP You have 0 punishments pending
@SystemMessage #VANC #VANP Good boy
@End
(End)
@End
@SystemMessage #VANC #VANP
It's not readable, it's not maintainable and, most definitely, it's not easy to write. No wonder not many people write content for Tease AI, because most people would probably just go mad. To be honest, after seeing the state of the source of code and after seeing scripts like this, I can't help but wonder - how it's even possible the software even runs?
Rewriting the code to be 100% compatible with existing scripts wouldn't help much in terms of dealing with bugs. Sure, I can make sure the software doesn't crash like it does now, but the scripts will be still buggy and problematic to deal with. To help with that, I'd have to either create a VERY complex editor or simply find a way to make scripts easier to write.
I think it's not only that there are few content creators, but those who would be interested are probably scared away by scripts like this. We're left with like 2-3 people. Writing personalities currently takes way too much time and people see the creator doesn't really have the time for maintaining the project. It's not the first time he disappeared without a trace and I'd bet it's not the last time either.
Combined all factors together, I think it would be a shame to let this die altogether. Currently I'm working on a complete rewrite and rethinking all possibilities. I'll let you guys know when I have something usable, so you can give me some feedback on it.
Ldroamer
that sounds interesting. I think implementing the ability to start/pause/stop an audio track should be a part of a software like this. I'm not that sure about support for e-stim devices, especially not if there isn't some unified API to work with, but I think that should be doable as well, as long as there would be enough interest for it.
Daragorn
yes, that is true. Rewriting the software without any help with writing the actual content wouldn't help much.