Streamline 'used' buttons/options?

[LeonDaydreamer]

Hi, I recently released a game: Put A Sock In It!

In it, we had a system in which previously selected options were faded out. My programmer used individual variables to keep track of this, and simply show a colored button for a selection that has never been played before or a grayed out button for a selection that has been played before.

However, if you have 1000 options, it would require 1000 variables to do it this way, and I know that Ren'Py doesn't exactly have arrays (only lists)... not sure how I could use those with an index of options. I was hoping to get a programmer's perspective on this subject about whether there was a straightforward way of doing this (and/or if there was already a feature implemented in Ren'Py that I'm not aware of)...

I also considered using renpy.seen_label(label) to keep track of previously selected options, but seen_label is persistent data, I wasn't sure if there was an equivalent of this for every new game you make?

Thanks!

[Ocelot]

I know that Ren'Py doesn't exactly have arrays (only lists)

In Python, lists are what in other languages you would call arrays/vectors/whatever: dynamic sequence container. You can use it as array.

Or iterate over it in more Pythonic way. Something like:

Code: Select all

default choices = [
    ('drink tea', False, 'drink.tea'),
    ('drink coffee', False, 'drink.coffee'),
    ('drink sode', False, 'drink.out_of_soda'),
]

#In game script:
screen choose_drink:
    vbox:
        for choice_text, seen, menu_label in choices:
            if not seen:
                # create active button
                # it should set second value in tuple in corresponding list element to True and return third tuple element
            else:
                # create inactive button

label choose_menu:
    call screen choose_drink
    jump expression _return

[LeonDaydreamer]

In Python, lists are what in other languages you would call arrays/vectors/whatever: dynamic sequence container. You can use it as array....

Alright, so you would recommend using lists to handle this. Thanks Ocelot! :)