[Tease Program] Tease-AI Java (1.4)

[Triple Alfa]

I don't see the problem. Of course that's a downgrade but a downgrade for the users who decides against local images only. It's not a downgrade to your personality in general. If you suggest to use local images or even offer pre tagged folders why not let the users decide if they want the full experience or not?

Say I'm showing a local image of a girl bent over showing her naked ass and accompany it with something like "Look at her all bent over for you. She looks ready to get fucked and all you can do is stroke.". Now replace that image with a random online image displaying a girl showing her clothed ass in a standing position. That to me is unacceptable. It's actually flawed and will probably get complaints/bug reports and rightfully so. It also reflects poorly on the personality and author in general as by releasing that content they give it their seal of "acceptable" at the very least.

Personally I would not feel comfortable releasing something with the message "I know this is shit and broken, but here you go use it if you want to.". That would only reflect poorly on me and my content. And I know from experience that no matter how much you tell people things like "This is unfinished content", "This is an alpha, expect bugs", etc. a lot of them if not most of them will still complain and treat it as if you gave it your final seal of approval. So if you put a feature in you can't just say "Using this feature is not recommended" and expect people to just accept that. Because they won't.

[GodDragon]

I don't see the problem. Of course that's a downgrade but a downgrade for the users who decides against local images only. It's not a downgrade to your personality in general. If you suggest to use local images or even offer pre tagged folders why not let the users decide if they want the full experience or not?

Say I'm showing a local image of a girl bent over showing her naked ass and accompany it with something like "Look at her all bent over for you. She looks ready to get fucked and all you can do is stroke.". Now replace that image with a random online image displaying a girl showing her clothed ass in a standing position. That to me is unacceptable. It's actually flawed and will probably get complaints/bug reports and rightfully so. It also reflects poorly on the personality and author in general as by releasing that content they give it their seal of "acceptable" at the very least.

Personally I would not feel comfortable releasing something with the message "I know this is shit and broken, but here you go use it if you want to.". That would only reflect poorly on me and my content. And I know from experience that no matter how much you tell people things like "This is unfinished content", "This is an alpha, expect bugs", etc. a lot of them if not most of them will still complain and treat it as if you gave it your final seal of approval. So if you put a feature in you can't just say "Using this feature is not recommended" and expect people to just accept that. Because they won't.

Wait why shouldn't you be allowed to show images that come with the personality? I have been talking about category images all the time. Like showCategoryImage("Boobs"); etc. and not showing images from a specific path. That of course will not be generalized.
I said I just don't want personality users to be forced to setup local folders on their own and find pictures themselves.

[izura]

Wait why shouldn't you be allowed to show images that come with the personality? I have been talking about category images all the time. Like showCategoryImage("Boobs"); etc. and not showing images from a specific path. That of course will not be generalized.
I said I just don't want personality users to be forced to setup local folders on their own and find pictures themselves.

I think he was speaking about specific tags in a generalised folder (for example called boobs).

that said I think you don't have to downgrade because of fallbacks.
You are not responsible if the user was lazy / unable to fulfill the preconditions and the creator did not plan a fallback.
The only important thing (for you) is to make sure that every functions have a return value which makes it possible to determine the success or the failure of the function, allowing error handling and if needed a fallback.
In addition, the more detailed you can be, the more real the personality will appear, wich is why i agree with Triple Alfa

[Triple Alfa]

Wait why shouldn't you be allowed to show images that come with the personality? I have been talking about category images all the time. Like showCategoryImage("Boobs"); etc. and not showing images from a specific path. That of course will not be generalized.
I said I just don't want personality users to be forced to setup local folders on their own and find pictures themselves.

I think we've been partially talking past each other. You assume the default currently is generalized local images that in your opinion should be able to be replaced by generalized online images. I did not make the same assumption. I thought you were talking about local images in general since you referred to only very specific local images like Mistress images remaining in your ideal scenario.

Since both my current and past personalities did not use generalized local images as their main source of visual content I did not assume that as the default. What I've been mainly referring to is using local images with more specific requirements than that of very generalized local content that could be replaced with online images. In my experience the more generalized the visual content is the lower the quality of the accompanying text is. That is why I do not view generalized local or online content as a great default option and instead prefer a more controlled and/or curated option.

[meaculpa_uk]

From the TAI Java Alpha thread.

"Spicy Java seeming to be the only viable reason for using TAIJava, then a lot of people are wanting to see if it's worth bothering with the port from standard TAI. The original Spicy was a great example of a brilliant idea that was implemented exceedling badly. People just want to know if Java Spicy lives up to the hype and to get a flavour of it. Right now you're blocking development of new personalities for both formats of TAI because no one knows which is better. 1885 effectively killed Miss Blue by releasing Fury but without incorporating the changes from Sweet Patch and making his own changes, so it's now impossible to run both Miss Blue and Fury from the same .exe

This forum is dying and interest is lacking because there's been no communication and developers/scripts writers are just bored of the uncertainty. If you want this place to gather pace, then releasing the Alpha of Spicy Java will at least give folks an idea of where to direct attention to. "

[lotar232]

From the TAI Java Alpha thread.

"Spicy Java seeming to be the only viable reason for using TAIJava, then a lot of people are wanting to see if it's worth bothering with the port from standard TAI. The original Spicy was a great example of a brilliant idea that was implemented exceedling badly. People just want to know if Java Spicy lives up to the hype and to get a flavour of it. Right now you're blocking development of new personalities for both formats of TAI because no one knows which is better. 1885 effectively killed Miss Blue by releasing Fury but without incorporating the changes from Sweet Patch and making his own changes, so it's now impossible to run both Miss Blue and Fury from the same .exe

This forum is dying and interest is lacking because there's been no communication and developers/scripts writers are just bored of the uncertainty. If you want this place to gather pace, then releasing the Alpha of Spicy Java will at least give folks an idea of where to direct attention to. "

I've been playing a fork of Spicy in TAJ for about a year now, periodically syncing to the main branch and making compatability fixes, but I have a lower bar for Polish than Godragon, and I stopped trying to sync 4-5 months ago. I've also started experimenting with doing toy integrations in some of my spicy scripts (Pishock &lovense have API's you can ping from javascript to issue a shock or control a lovense vibrator)... which work for me, but might make my branch of code clunky if you don't have the same toys as I, (and I would need to write onboarding code to coach users how to set up the toys, where I've just jammed some constants in the code)

One other shadow hanging over TAI Java is the Nashorn warnings I keep seeing... I think at some point someone is going to have to port TAI Java itself to GraalVM (or whatever the new engine is) or else we'll find one day that TAI Java won't run on current Java installs.... I'm a little leery of investing a lot of time polishing my Spicy fork without seeing anyone go after that potential issue.

[ski23]

From the TAI Java Alpha thread.

"Spicy Java seeming to be the only viable reason for using TAIJava, then a lot of people are wanting to see if it's worth bothering with the port from standard TAI. The original Spicy was a great example of a brilliant idea that was implemented exceedling badly. People just want to know if Java Spicy lives up to the hype and to get a flavour of it. Right now you're blocking development of new personalities for both formats of TAI because no one knows which is better. 1885 effectively killed Miss Blue by releasing Fury but without incorporating the changes from Sweet Patch and making his own changes, so it's now impossible to run both Miss Blue and Fury from the same .exe

This forum is dying and interest is lacking because there's been no communication and developers/scripts writers are just bored of the uncertainty. If you want this place to gather pace, then releasing the Alpha of Spicy Java will at least give folks an idea of where to direct attention to. "

I've been playing a fork of Spicy in TAJ for about a year now, periodically syncing to the main branch and making compatability fixes, but I have a lower bar for Polish than Godragon, and I stopped trying to sync 4-5 months ago. I've also started experimenting with doing toy integrations in some of my spicy scripts (Pishock &lovense have API's you can ping from javascript to issue a shock or control a lovense vibrator)... which work for me, but might make my branch of code clunky if you don't have the same toys as I, (and I would need to write onboarding code to coach users how to set up the toys, where I've just jammed some constants in the code)

One other shadow hanging over TAI Java is the Nashorn warnings I keep seeing... I think at some point someone is going to have to port TAI Java itself to GraalVM (or whatever the new engine is) or else we'll find one day that TAI Java won't run on current Java installs.... I'm a little leery of investing a lot of time polishing my Spicy fork without seeing anyone go after that potential issue.

Regarding spicy, I can't speak for that as I'm not involved in that project. However, there are other personalities for TAJ in the works mainly one that I'm working on and others. You have to understand though that I can't work on this full time and I have a full time job, relationship, and other hobbies. Regarding Nashorn, Tease AI Java will never break one day because of this. All those warnings are saying is that nashorn will be removed in a later version of Java. However, when we upgrade to that version of Java we would have to deal with that so it's not something that would just break because we would have to upgrade to that version anyway. Furthermore, moving to Graal is a priority and is definitely going to happen. On the topic of personalities, I can't give much info on when certain personalities will or won't come out. GodDragon and I have created this platform as a way to make personalities and it has way more possibilities than the original TAI but at the end of the day it can't always just be the 2 of us making both TAJ and every personality. There have been many weeks that I have worked in excess of 40 hours a week on this project and it isn't sustainable to continue at that rate all the time.

[lotar232]

From the TAI Java Alpha thread.

"Spicy Java seeming to be the only viable reason for using TAIJava, then a lot of people are wanting to see if it's worth bothering with the port from standard TAI. The original Spicy was a great example of a brilliant idea that was implemented exceedling badly. People just want to know if Java Spicy lives up to the hype and to get a flavour of it. Right now you're blocking development of new personalities for both formats of TAI because no one knows which is better. 1885 effectively killed Miss Blue by releasing Fury but without incorporating the changes from Sweet Patch and making his own changes, so it's now impossible to run both Miss Blue and Fury from the same .exe

This forum is dying and interest is lacking because there's been no communication and developers/scripts writers are just bored of the uncertainty. If you want this place to gather pace, then releasing the Alpha of Spicy Java will at least give folks an idea of where to direct attention to. "

I've been playing a fork of Spicy in TAJ for about a year now, periodically syncing to the main branch and making compatability fixes, but I have a lower bar for Polish than Godragon, and I stopped trying to sync 4-5 months ago. I've also started experimenting with doing toy integrations in some of my spicy scripts (Pishock &lovense have API's you can ping from javascript to issue a shock or control a lovense vibrator)... which work for me, but might make my branch of code clunky if you don't have the same toys as I, (and I would need to write onboarding code to coach users how to set up the toys, where I've just jammed some constants in the code)

One other shadow hanging over TAI Java is the Nashorn warnings I keep seeing... I think at some point someone is going to have to port TAI Java itself to GraalVM (or whatever the new engine is) or else we'll find one day that TAI Java won't run on current Java installs.... I'm a little leery of investing a lot of time polishing my Spicy fork without seeing anyone go after that potential issue.

Regarding spicy, I can't speak for that as I'm not involved in that project. However, there are other personalities for TAJ in the works mainly one that I'm working on and others. You have to understand though that I can't work on this full time and I have a full time job, relationship, and other hobbies. Regarding Nashorn, Tease AI Java will never break one day because of this. All those warnings are saying is that nashorn will be removed in a later version of Java. However, when we upgrade to that version of Java we would have to deal with that so it's not something that would just break because we would have to upgrade to that version anyway. Furthermore, moving to Graal is a priority and is definitely going to happen. On the topic of personalities, I can't give much info on when certain personalities will or won't come out. GodDragon and I have created this platform as a way to make personalities and it has way more possibilities than the original TAI but at the end of the day it can't always just be the 2 of us making both TAJ and every personality. There have been many weeks that I have worked in excess of 40 hours a week on this project and it isn't sustainable to continue at that rate all the time.

sorry, I think I misspoke about the Nashorn issue... by "current" I meant "current in the future".... i.e. at some point in the future we would need to port to GraalVM or provide hokey install instructions to newcomers to find an old version of Java thats still compatible.... if there's some long period of time where TAJ won't run and people are waiting for TAJ itself to get fixed to match Auto-updated Java installs, that might be a roadblock to developers...

[ski23]

I've been playing a fork of Spicy in TAJ for about a year now, periodically syncing to the main branch and making compatability fixes, but I have a lower bar for Polish than Godragon, and I stopped trying to sync 4-5 months ago. I've also started experimenting with doing toy integrations in some of my spicy scripts (Pishock &lovense have API's you can ping from javascript to issue a shock or control a lovense vibrator)... which work for me, but might make my branch of code clunky if you don't have the same toys as I, (and I would need to write onboarding code to coach users how to set up the toys, where I've just jammed some constants in the code)

One other shadow hanging over TAI Java is the Nashorn warnings I keep seeing... I think at some point someone is going to have to port TAI Java itself to GraalVM (or whatever the new engine is) or else we'll find one day that TAI Java won't run on current Java installs.... I'm a little leery of investing a lot of time polishing my Spicy fork without seeing anyone go after that potential issue.

Regarding spicy, I can't speak for that as I'm not involved in that project. However, there are other personalities for TAJ in the works mainly one that I'm working on and others. You have to understand though that I can't work on this full time and I have a full time job, relationship, and other hobbies. Regarding Nashorn, Tease AI Java will never break one day because of this. All those warnings are saying is that nashorn will be removed in a later version of Java. However, when we upgrade to that version of Java we would have to deal with that so it's not something that would just break because we would have to upgrade to that version anyway. Furthermore, moving to Graal is a priority and is definitely going to happen. On the topic of personalities, I can't give much info on when certain personalities will or won't come out. GodDragon and I have created this platform as a way to make personalities and it has way more possibilities than the original TAI but at the end of the day it can't always just be the 2 of us making both TAJ and every personality. There have been many weeks that I have worked in excess of 40 hours a week on this project and it isn't sustainable to continue at that rate all the time.

sorry, I think I misspoke about the Nashorn issue... by "current" I meant "current in the future".... i.e. at some point in the future we would need to port to GraalVM or provide hokey install instructions to newcomers to find an old version of Java thats still compatible.... if there's some long period of time where TAJ won't run and people are waiting for TAJ itself to get fixed to match Auto-updated Java installs, that might be a roadblock to developers...

When I get a chance I'll go ahead and start experimenting with Graal and see if I can get some stuff working with it so it's ready.

[Wrought_in_Iron]

From the TAI Java Alpha thread.

"Spicy Java seeming to be the only viable reason for using TAIJava, then a lot of people are wanting to see if it's worth bothering with the port from standard TAI. The original Spicy was a great example of a brilliant idea that was implemented exceedling badly. People just want to know if Java Spicy lives up to the hype and to get a flavour of it. Right now you're blocking development of new personalities for both formats of TAI because no one knows which is better. 1885 effectively killed Miss Blue by releasing Fury but without incorporating the changes from Sweet Patch and making his own changes, so it's now impossible to run both Miss Blue and Fury from the same .exe

This forum is dying and interest is lacking because there's been no communication and developers/scripts writers are just bored of the uncertainty. If you want this place to gather pace, then releasing the Alpha of Spicy Java will at least give folks an idea of where to direct attention to. "

I'm not sure if you're suggesting that something runs in a broken form, but running Miss Blue off the Fury patch has worked fine for me.

[lotar232]

Regarding spicy, I can't speak for that as I'm not involved in that project. However, there are other personalities for TAJ in the works mainly one that I'm working on and others. You have to understand though that I can't work on this full time and I have a full time job, relationship, and other hobbies. Regarding Nashorn, Tease AI Java will never break one day because of this. All those warnings are saying is that nashorn will be removed in a later version of Java. However, when we upgrade to that version of Java we would have to deal with that so it's not something that would just break because we would have to upgrade to that version anyway. Furthermore, moving to Graal is a priority and is definitely going to happen. On the topic of personalities, I can't give much info on when certain personalities will or won't come out. GodDragon and I have created this platform as a way to make personalities and it has way more possibilities than the original TAI but at the end of the day it can't always just be the 2 of us making both TAJ and every personality. There have been many weeks that I have worked in excess of 40 hours a week on this project and it isn't sustainable to continue at that rate all the time.

sorry, I think I misspoke about the Nashorn issue... by "current" I meant "current in the future".... i.e. at some point in the future we would need to port to GraalVM or provide hokey install instructions to newcomers to find an old version of Java thats still compatible.... if there's some long period of time where TAJ won't run and people are waiting for TAJ itself to get fixed to match Auto-updated Java installs, that might be a roadblock to developers...

When I get a chance I'll go ahead and start experimenting with Graal and see if I can get some stuff working with it so it's ready.

that would be great...Thanks! if it at least gets scoped out we'll know how hard it will be to do the conversion.

[GodDragon]

sorry, I think I misspoke about the Nashorn issue... by "current" I meant "current in the future".... i.e. at some point in the future we would need to port to GraalVM or provide hokey install instructions to newcomers to find an old version of Java thats still compatible.... if there's some long period of time where TAJ won't run and people are waiting for TAJ itself to get fixed to match Auto-updated Java installs, that might be a roadblock to developers...

When I get a chance I'll go ahead and start experimenting with Graal and see if I can get some stuff working with it so it's ready.

that would be great...Thanks! if it at least gets scoped out we'll know how hard it will be to do the conversion.

Shouldn't be too hard. GraalVM supports a Nashorn legacy mode so nothing should change. Only things we need to deal with is how internal function registers like sendMessage work. But otherwise it shouldn't be a problem at all.

[SilentSix]

A little new to this, but unless im blind...... how the hell do I run this? I have Java installed. Thanks in advance!

[Spielers]

A little new to this, but unless im blind...... how the hell do I run this? I have Java installed. Thanks in advance!

simple dobble click the TeaseAI.jar

[SilentSix]

A little new to this, but unless im blind...... how the hell do I run this? I have Java installed. Thanks in advance!

simple dobble click the TeaseAI.jar

Unless I did something wrong, im getting a rar file.