Milovana.com

Back in 2012, tommyberlin86 created an HTML5 player. It's been great for mobile teases but there are a few outstanding issues (like visible timers and sound support) that Tommy no longer seems to be around to fix.

So I'd like to pick up where he left off and try my hand at recreating my own. Not only to fix these bugs but to add a few extra features, too. (And to get some "exciting" web-dev practice in.)

The first issue I'm running into, though, is how to fetch the tease XML files via the tease ID. Is anyone able to point me in the right direction?

For future explorers with the same question
Flash Tease Solution:

Flash teases are saved in the raw Nyx format, which can be retrieved with the URL
https://milovana.com/webteases/getscript.php?id=XXXXX

Classic Tease Solution:

No solution found yet to retrieve full script as a single document. Current implementation is to loop through each existing html page in the tease which takes nearly a second per page.

Would prefer a one-page solution to reduce requests from the server and speed up retrieval.

Something else that might be helpful would be a master list of available <tags>, if such a thing exists.

Thanks for any help you may be able to provide!

You can get the Nyx code by going to for example https://milovana.com/webteases/getscript.php?id=21418

The first issue I'm running into, though, is how to fetch the tease XML files via the tease ID. Is anyone able to point me in the right direction?

There is a downloader for TeaseMe/GuideMe available. He downloads the XML and all images of a tease.

Thanks for the replies! With these and a little direction from philo I think I've got what I need to get started. I'll try to keep this thread updated as I make progress.

So I'm just a few elements away from a fully functional php web-based parser and TeaseMe XML exporter.

There are a few items I found in philo's exporter with whose purposes I'm not familiar.
Would any veteran flashtease makers be able to fill me in on what these do?

Unknown Elements
must(self:
mustnot(self:

goto(target: as opposed to go(target:

instruc(set:
instruc(unset:
instruc(mult:

Unknown delay attributes
delay( time="", start-with="", target="", onTriggered="", style="" )

Ph0enixAsh wrote:Unknown Elements
must(self:
mustnot(self:

goto(target: as opposed to go(target:

instruc(set:
instruc(unset:
instruc(mult:

Unknown delay attributes
delay( time="", start-with="", target="", onTriggered="", style="" )

go(target) creates a Continue button while goto(target) immediately redirects to the target without user interaction.

The instruc and action parts of a page(text?, media?, action?, hidden?, instruc?) show up in the sidebar, while media and text (not to be confused with text(text)) represents the main content.

Almost anywhere you can use [vert|horiz|mult](e0..) to stack elements vertically, horizontally or on top of each other. Understandably stacking of non-visual elements is usually done with mult.

There is no such start-with and/or onTriggered in delay(time, target, style?). Also these arguments don't seem to be used in any tease. But it's not a problem, the viewer ignores all unknown codes and arguments.

PCM2
must(self, action0..) creates a PCM2-must relationship for self. Meaning all actionX actions must be "set" (see below) for the self action (usually a page) to be runnable.

On the other hand mustnot(self, action0..) makes self unavailable if any actionX action is set.

set(action0..) sets actions, unset(action0..) unsets actions. What more can I say? Initially all actions can run only once. When you run it, it gets set, so next time you try running it it would get skipped. But you can also set it programmatically, for example to skip it without having ever been run. And on the other hand you can unset it to make it runnable. On top of that you can use repeat[add|del|set](target, count) to change the number of runs for an action to actually be regarded as set. (Not to be confused with repeat(count,max?).) In the end this boils down to two variables, number of runs and repeats, which you can use to ignore an action if its runs >= its repeats. And the only command that even pays attention to this constraint is range(from, to, prefix?). Same goes for numactions(self, count) and numactionsfrom(self, count, since), which make an action only available after a certain count of actions have been run (optionally counting from the first run of some since action).