nsxoxy wrote: Tue Dec 16, 2025 9:19 am
I really like seeing a quality tease and/or one with a novel premise (or both, like this) become the framework for a new one, and seeing what that leads to.
...
I just think there's endless potential for something like this.
I absolutely agree about the potential of Shattered's brilliant idea here! This was what inspired me to revive a dead Milovana account to make something new. In my opinion, Matching Submission was a great idea, right up there with Cock Hero in terms of cleverness, originality, and flexibility. I really really hope that a bunch of people start creating matching teases (because I want to play them!). I'm not even interested in chastity, and Matching Submission was still my favorite tease ever
I did manage to find what I think is a bug from clicking through a bit. It seems like if you skip a user and then encounter them again, they treat it like a continuation, not a first encounter.
Thank you for catching this - there's one user in particular where this is more of an issue because of the way her queue works, and I already have a TODO to fix it.
I'm also not sure if you should be matched and put into the same scene a second time if you started it and were skipped.
This is more of a missing feature due to trying to keep the complexity down. In some cases, I want you to have the option to return after you've been skipped, to give you a chance to try another path. It's a balance between allowing players to explore lots of branches and having a more "realistic" tease. In a few of the matches, I've dropped some stuff into the script to imply that the dommes just flat-out won't bother to remember you.
Maybe I'll make the "you aren't worth remembering" more blatant in some cases. That would keep the logic simple AND add more humiliation to the tease
(Nerd stuff incoming)
I am very aware of a balance between ease of maintenance and richness of the story that occurs here. My main goal is to reduce "breaking" bugs where you get stuck in an endless loop or you can't make any progress. To accomplish that, I am trying to build as much of the logic as possible as reusable code in the init script, instead of complex paths built into the individual tease pages, and I haven't come up with a good way to implement some of the memory-related stuff that doesn't make the script much harder to maintain.
The main issue preventing me from implementing some of the more complex logic I'd like to use is Javascript limitations in the EOS sandbox implementation. Specifically, EOS runs things basically as one-off commands, and it continues running on certain commands. The specific functionality I desperately want is error handling when calling pages.goto, but try... catch blocks don't work with the async calls
Because I can't reliably use error handling, reproducing the same type of logic (like preventing a repeat script if you've skipped the user before) involves copy / pasting JSON chunks into each of the matches - which can be really fragile, especially early in development where I'm changing things frequently.
I did just push an update that keeps track of how often you skip each user, and disables those users from random matching if they've been skipped too many times. I will keep thinking about ways to use this to make matches more interesting.
