Toggles with EOS

[dark0512]

How are the toggles put in an EOS tease? I can't seem to figure it out. When I say toggles, toggling certain options on or off before starting a tease.

I thought I saw a how-to on this at one time, but can't seem to find it.

[indyc]

If you were trying to toggle "censorship" for example you would make a button for it. If the player clicks the censorship "choice" button you would then have an eval function called censor=true or whatever you want to call it. Remember to write all of the variables you will use in the init script page in your options, for example
censor=false;
Playername=null;

Then later in the tease when you have a censored photo you want to show the player you make an if statement:
If(censor)
Then: Add censored photo here
Else: Show some other photo, text, or nothing

I hope this makes sense, let me know if you want me to make screenshots and walk you through it.

If you are asking how to put them in the same button that you click on or off, you would loop the page. I can explain how to do this too if this is what you were looking for.

[dark0512]

If you are asking how to put them in the same button that you click on or off, you would loop the page. I can explain how to do this too if this is what you were looking for.

This is what i'm trying to do. I don't have an example of a tease right now, but where a single page has an "options" then goes to a few different options with toggles. I can't figure out how to get the actual toggles.

I know I can do eval statements based on using a "choice" but can only figure out doing that one at a time.

It's possible it's tied to the "enable" and "disable", but I can't figure out how to use them.

[indyc]

The one that most recently comes to mind that you are describing is xxxcom. I would actually not suggest doing it this way unless you have a reason a player would want to go change it mid game with game saves or something. The only way I have been able to get "enable" and "disable" to work right is by disabling pages which doesn't help you where with toggles.

If you still want to make toggles, I would do it by making the options button take you to a page, for my example we can call it options1.

Page "Options1" has the choices/buttons
CBT On , Ruin On, Sounds On

If I click CBT on, it triggers an eval "cbt=false;" followed by a go-to to page "options2"
"Options2" would have the buttons
CBT Off, Ruin on, Sounds On
If you would click CBT off then it triggers an eval "cbt=true" followed by a go-to page "options1"

I realize that doing it this way means you would need to make 6 different pages for 3 buttons. Your tease has a ton of them so I don't know if I suggest it.(someone probably has a better way)

The other issue with toggles is that if I see "CBT off" is that telling me that it is already off or that by pressing it I turn CBT off? You can solve this by adding a say action each time that tells you if it is off or on but again, it is a lot of work that is not needed in games without backtracking/save loading.

On a side note, a minor bit of opinion/feedback in your own tease, I would either remove or heavily reduce the timers between each of your questions about activating or deactivating an aspect. Currently it takes a really long time to get into the meat of your tease and much of it is because of those timers. Good luck!

[RemiHiyama]

I realize that doing it this way means you would need to make 6 different pages for 3 buttons. Your tease has a ton of them so I don't know if I suggest it.(someone probably has a better way)

There's a couple different ways.

One is having your eval be, for example

Code: Select all

cbt = !cbt

That will set it to whatever it isn't currently. In that kind of setup it's also a good idea to have say actions on your options page that will tell what the current settings are.

If you wanted to have something like a setting that went through three different options, you could do something like

Code: Select all

cbt = cbt + 1; if (cbt > 2) cbt = 0

And if you wanted to have it say something different on the buttons depending on the settings... You can still do it with one page. Choice buttons default to always being visible, but you can toggle that and enter an expression, with the button only displaying if the expression is true. Done right, you can make it look like the button is changing, when it's really one button being hidden and another being shown. (Sadly, dynamic text on button labels... doesn't really work.)

[dark0512]

Perfect! Thanks for the help!!