TeaseHub is getting a restart as a website and is looking for preview testers!

[Teddibaer]

Hello all,

TeaseHub, the alternative and upgrade to EOS that launched a couple of years ago but was discontinued due to a lack of interest is getting a restart as a website as opposed to downloadable software. Hopefully this will help getting people excited about new possibilities with modern, well-supported and maintained teasing software.

If you're not aware of TeaseHub, it's a fully hosted teasing platform with a modern editor and player in one, just like EOS. For more info and screenshots (they are still relevant as everything was just ported over to the browser) please have a look at the original post: viewtopic.php?t=25246

Some work remains before a public launch but I'm looking for some testers who are willing to run the website through it's paces. You can import your tease straight from Milo with just a couple of clicks.

As it stands the editor and player are fully working and all features of EOS are supported and working (apart from any possible bugs that is). Testing basically entails using the platform to either create or edit a tease in the custom editor or play a tease you created or know very well. I'm looking for general feedback, bugs and EOS inconsistencies.

If you're interested please send me a DM here or on Discord (preferred): teddibaer

Thanks and till soon!

[indyc]

I've been testing it for a while and wanted everyone to know that I'm really impressed so far!

Have you ever wanted to create teases faster and then later put them on Milovana? I think this has that potential one day.

Have you ever wanted to make teases with png, gif, forms of video, copy pasting entire sections, keyboard support, saves, and potentially far more? I also think it has potential! The more feedback Teddibaer gets the faster we can get these features up and running!

[nsxoxy]

This seems like it could be a potentially important project, but I'm curious if there's any more information you could offer as to what the testing process entails.

[Teddibaer]

This seems like it could be a potentially important project, but I'm curious if there's any more information you could offer as to what the testing process entails.

I sure can!

As it stands the editor and player are fully working and all features of EOS are supported and working (apart from any possible bugs that is). Testing basically entails using the platform to either create or edit a tease in the custom editor or play a tease you created or know very well. I'm looking for general feedback, bugs and EOS inconsistencies.

Added to first post

[qatguy]

i am very interested.

please let me test.

[collie.alex]

As a current tease maker, I am very interested in testing this out.

[Morexis]

Hi Teddibaer! I'm not familiar with TeaseHub yet, but it sounds very promising and I'd love to give it a try!
I've just recently started working on a new game, so experimenting with a new editor with more features could fit perfectly now.

[Teddibaer]

Hi Teddibaer! I'm not familiar with TeaseHub yet, but it sounds very promising and I'd love to give it a try!
I've just recently started working on a new game, so experimenting with a new editor with more features could fit perfectly now.

Thanks! I sent you a DM on Discord if you don't mind.
All others were contacted as well

[PlayfulGuy]

I'm very interested in seeing this project develop and continue, but can't really commit to any significant testing right now.

I'll be watching for updates.

PG

[Teddibaer]

A few of you have contacted me and some of you have ran some very good tests with great feedback. Thank you!

I'm currently finishing a new feature which should make debugging complex teases a lot easier: the debugging sidebar. Right in the player itself it shows all actions for the current page and highlights the current action. The debug step toggle button (the pause icon) - when enabled - pauses on all normally instantaneous actions like page switches, evals etc) and requires an extra click to run that action and continue. This effectively makes debugging much easier as you can actually tell what's going on action-by-action.

Also, as the tease Javascript code runs natively in browser Web Workers instead of in a VM like EOS you are able to use your browser developer tools to debug your scripts even further as you can execute code straight in your tease sandbox with the normal console and use debugger; statements, breakpoints and all other JS debug features your developer tools provide. This also means that all modern ECMAScript features are available for you to use. Nifty!

I'm still looking for a few more testers so if you're interested please send me a DM.

I'm very interested in seeing this project develop and continue, but can't really commit to any significant testing right now.

I'll be watching for updates.

PG

Great to hear you're interested to follow the project! Feel free to DM me if you just want to have a quick play with it, would love to hear your first impressions too.

[Darigaaz]

I just discovered this thread. Is this project still ongoing because I might be interested in helping. Especially if indyc is impressed by the work done

[indyc]

I just discovered this thread. Is this project still ongoing because I might be interested in helping. Especially if indyc is impressed by the work done

Not only am I very impressed (it was nearly 1:1 when work on it paused not to mention all the other hypotheticals that it could allow), I check in every week hoping that work resumes because it would be a total gamechanger on my end.