Some really really basic EOS questions.

[ritewriter]

Working on my first tease. I'm a total noob when it comes to EOS or any javascripting really. A few super basic questions:

Is there a preferred platform/browser to work on. I seem to have a lot of problems using Safari/ios. Edge/PC appears to be much better.

Is there a limit to the number of pix you can upload into galleries?

If I autoadvance dialogue for a section, how long do folks typical hold each sentence? I was going with 4s. Too long? Too short?

If I create a variable like mcname, then run a segment but not the entire thing, the say sections that include mcname don't seem to come up. I assume this is normal and not a mistake on my part?

How do I create a slideshow effect? In other words, is there a way to run a series of image in a row with a determined delay between them (.5s) without using SAY between them?

Thanks in advance for answers. I know they're all pretty basic. I'm sure I'll have more as I go along.

[kerkersklave]

Is there a preferred platform/browser to work on. I seem to have a lot of problems using Safari/ios. Edge/PC appears to be much better.

Firefox and Chrome both work well for me.

Is there a limit to the number of pix you can upload into galleries?

At least not a low limit, I think I have put more than 100 images in there and can't remember that anyone ever mentioned a limit.

If I autoadvance dialogue for a section, how long do folks typical hold each sentence? I was going with 4s. Too long? Too short?

I would not use automatically advancing dialog. Reading speeds vary a lot and you also have to consider non native speakers. As a reader I prefer if I have to click for each step. I can do that without actively thinking about it and read a text at my preferred speed, stop. Teases, that use some kind of timer for advancing dialog usually annoy me, either, I have to wait, or I miss crucial information.

How do I create a slideshow effect? In other words, is there a way to run a series of image in a row with a determined delay between them (.5s) without using SAY between them?

Timer actions can be completely hidden.

[indyc]

Is there a limit to the number of pix you can upload into galleries?

My tease is over 10,000 pictures right now and that has not been a limiting factor that I have seen yet. The limitation that I have run into is that it is pretty finicky about what jpeg type it will upload and seems to not allow any picture over 7 or 8 megabytes large or so. Oh how much nicer things would be if it allowed png and gif...

I might also be hitting the actual limit for how long your code can be but it seems to depend on server load at the time of publishing. I wouldn't worry about it because I would be surprised if anyone else is making teases that large.

If I autoadvance dialogue for a section, how long do folks typical hold each sentence? I was going with 4s. Too long? Too short?

I will back kerkersklave up by saying use the pause option for dialog as often as you can. This allows for the user to progress through the tease at their own pace. I am probably more annoyed than they are of teases that make me wait to move onto the next section to read or see.

How do I create a slideshow effect? In other words, is there a way to run a series of image in a row with a determined delay between them (.5s) without using SAY between them?

A .5s timer is more of a gif, though you can do photos in that way (I did gifs in the tease like that for months) I highly suggest you use fapnips program to do any gifs. If you PM me I am happy to walk you through step by step how to accomplish this or even do it for you if you wish. (for that matter PM me with ANY questions and I can give quick specific answers)

Also, I had decimal timers like that ".5s" and while the preview runs without errors, it will give you errors when it is time to publish. Make sure that the time is stated as "0.5s" instead.

[fenway]

Heyo,

Ah yes, the EOS blues. I remember when I started using it three months ago. It's a great tool and I hope you get used to it really quickly!

About autoscrolling text, I personally love it. My least favorite thing is when I have to er... free up a hand to use my keyboard or mouse when I'm trying to enjoy a Milovana creation. It can be a huge hassle if you're using toys, or have lube on yourself, to have to click something during a tease.

I understand the points these fine gentlemen have about considering non-native speakers, or being able to control the pace of text themselves. These points are excellent to consider. And ultimately, the answer to this part of your question/post depends on you.

I guess what I would say is create a tease that you're happy with and fooey on anyone who doesn't like it. I write my teases for myself and if others enjoy them, then that's great! I use autoscrolling text because that's what I want in the teases I play. And though some people might not like it, if I'm happy with my creation, then that's fine. :)

For autoscrolling text, I try to imagine the pacing of what's being said by hearing it like a conversation in my head. Then I slow it down a few seconds to account for the difference in speed for reading. So far, my teases have been received very positively (and to think, I was just going to keep them all to myself and never post any!).

Anyway, best of luck with your content creating! I'm sure you'll make something amazing!

[indyc]

On the note of timers or pauses for text. (with the pros and cons listed by everyone) What you can do is have skippable timers. Where it will run automatically for users but you can click to speed it up if you wish. This is something you can play with to see what feels best if you choose to go that route.

To do this make a say action. Then select "custom", set a timer to whatever you think is appropriate, and then select the toggle "allow user to skip the wait". That way everyone wins... I think? Of course I don't suggest this in the middle of a metronome section should you have one but everywhere else would be a big help to people like me.

[fenway]

Interesting. You can do this????

How many extra steps does this take to program on each page????

[indyc]

Interesting. You can do this????

How many extra steps does this take to program on each page????

I gave every step, it is as simple as that. (you just have to do it for each say action individually) I am excited if you implement this yourself in your teases.

I don't do this much on my own tease because of the vast number of pictures and choices. (It is more of a video game than instructions) Anytime someone wants to see a picture longer I want to let them.

[fenway]

I gave every step, it is as simple as that. (you just have to do it for each say action individually) I am excited if you implement this yourself in your teases.

I don't do this much on my own tease because of the vast number of pictures and choices. (It is more of a video game than instructions) Anytime someone wants to see a picture longer I want to let them.

I will give it a try!

[ritewriter]

Thank you for the responses! If folks don't mind, I'm going to use this topic as a kind of "help ritewriter through his first tease." Hopefully other noobs will find it useful.

I've decided to shelve my Clinic tease for a bit and do a shorter one to figure out EOS. Going well so far. Or it was. But...

I've run into a strange bug/error. I have three simples page, just a series of say commands right now, that all with the same goto. No matter what I do, that GOTO just fails. I've renamed it. Deleted it entirely. Changed the name of the target and rebuilt it from scratch except for the branching choice it contains. When I test, it always fails to load from every direction.

What am I doing wrong? It won't even load as simple SAY command.

ON FURTHER TESTING: The problem seems to be the CHOICE command in the target page. If I include one, the page fails. If I don't, the page will run. But the second I add a CHOICE it fails again, even if it's a completely new one. Any ideas of what's wrong?

Also, my one unanswered question was about testing variable like MCNAME or whatever. Is there a way to test a page with a variable call up in isolation without running the page for the variable setting? It's a drag to have a test fail every time I hit the MCNAME call up.

Thank you again. I'm enjoying the process of building a tease/choose your own adventure novella. Hopefully I can figure all this out and actually publish.

[indyc]

Feel free to PM me the share link of your tease so I can figure out exactly what is going wrong instead of guessing. There is a share link to the left of the eos editor.

I am curious to know what your bug/error looks like. Is the tease failing to load or does it just have a freeze when it runs? I find the vast majority of my freezes are caused by using a variable that is misspelled or has not been created yet.

The common mistake in choices is that they default with the destination set to be the beginning of your tease. That would cause it to loop but I doubt that is what is happening.

Also, my one unanswered question was about testing variable like MCNAME or whatever. Is there a way to test a page with a variable call up in isolation without running the page for the variable setting? It's a drag to have a test fail every time I hit the MCNAME call up.

I am not sure I understand the question really but in the options there is a place called initiation script (init script). It is highly suggested to define all variables you will use here first otherwise it is likely to call freezes and null values when the variable is used. For example
x=0;
name=null;

Once your variables are working you should be able to test each page starting from that page using the preview button in the upper right of that page instead of the preview to the left.

[ritewriter]

Lol, getting ready to send it, I accidentally hit the publish button, which caused an error check which flagged the issue so I could fix it. Will PM you what I have so far. Just the say functions though. So ignore if you want or see what I’m trying to do if interested

[ritewriter]

Okay, next thing I’m struggling with.

I only have one stat for the game. It’s WILL, and measures the mc’s ability to stand up to the antagonist.

Since it’s a short game. WILL starts at 10, is invisible, and decreases based on certain choices.

What I’m trying to write is a kind of Will Save. So if the MC wants to do something that requires will, I want to check against the stat, but in a random invisible way. So basically generate a random # 1-20 and if it’s less than or equal to the current will, the character can exert his will.

Can anyone break down how to do that?

[indyc]

Of course! This is how I would do exactly what you are asking(all stolen from other people's code who know what they are doing viewtopic.php?f=2&t=23845):

Init script:
will=10;
function randomIntFromInterval(max,min){ //random generator
return Math.floor(Math.random()*(max-min+1)+min);
rand=0;

Test to make sure it is working by making a separate page called "Test":
rand = Math.floor(Math.random() * (20 - 1 + 1)) + 1;
say function that says "Your number is <rand>"
Choice function - "Reroll" -go to "Test"

It should look like the attachment. If that is working well after previewing it, you then would go to the page you want to do your will check on and do something like this second attachment:

Ok, now that we have all of that out of the way, now for my opinions. THANK YOU SO MUCH for making a game with a will check, we need more games like this. That being said, studying game design for over 10 years, your suggestion hurts me haha.

A random number between 1-20 is absurdly high. You could fail in all situations and succeed in nearly all situations. I know that maybe this still sounds interesting to you but think instead that the random number as stated will be twice as impactful as your will. This will make your choices hardly matter at all and people just reset their playthrough to get the outcomes they want.

Instead I would highly suggest making a random number between 0-2(or something like that).
rand = Math.floor(Math.random() * (2 - 0 + 1)) + 0;
Then early in the game your if statement can have a fail if "rand>will"
but later in the game the fail becomes "rand+5>will"
and then "rand+8>will" even later.

This is just the first example that comes in my mind and I would HIGHLY suggest playing with your own figures to see what feels right even if you always want there to be a small chance of failure. What I would also do is decrease your own will every time there is a will check. It is somewhat thematic after all. Good luck

[ritewriter]

This is insanely helpful. Thank you!

Trying to execute this and I'm having an issue with the code line
rand=0
On the init script I keep getting an error and it won't run and the quickfix fails.
rand is grayed out. 0 is green but has a line under it.
When I hit return I get unreachable code detected 7027 error for that line.
It looks like rand is undefined as a function?

[indyc]

Trying to execute this and I'm having an issue with the code line
rand=0
On the init script I keep getting an error and it won't run and the quickfix fails.
rand is grayed out. 0 is green but has a line under it.
When I hit return I get unreachable code detected 7027 error for that line.
It looks like rand is undefined as a function?

Sorry, I didn't get a notification that you edited this and were asking for help.

rand is not a function, it is just a variable. You can call it whatever you want as long as you keep it the same through the tease.
The errors you are getting are more likely because of the:
function randomIntFromInterval(max,min){ //random generator
return Math.floor(Math.random()*(max-min+1)+min);
}

(I might have also forgotten to copy past that last } there, not sure. Try adding that first and see what happens)

I may have written it wrong here. I honestly know so little about it that it would be hard for me to diagnose here. If you send me a link of your last working tease I can likely find out why and fix it for you and return it.

If to get it working you need to add // at the beginning of the new lines of code that would probably be best. This turns code into comments that the program would not run and would not cause an error.