Ren'Py Learning Renpy. Need some help!

[anne O'nymous]

Maybe like this:

style mybigtext:
    size 42
    bold True

This is better for the style creation, but :

Now I'm not sure if the style should be applied inside or outside the vbox

Ren'py do not make its style propagate, so it have to be applied directly to the text.

But there's a way to still simplify this, the

You must be registered to see the links

screen property. It works by defining the prefix that will be used to build the name of the style to apply to each screen statements inside the actual block ; the said name being prefix_statement. Therefore, to apply the same style to all the text screen statements inside a vbox :

# The style need to apply to /text/.
style mybig_text:
    size 42
    bold True

screen two_big_lines:
    vbox:
        # Tell to Ren'py which prefix to use.
        style_prefix "mybig"

        text "line 1"
        text "line 2"

Note that some screen statements, like by example textbutton, are particular because they have more than a single part. Like implied by its name, a textbutton is a combination between the button and the text screen statements. For them, the name of the style is a little more complex :
prefix_outer statement_inner statement

So, for a textbutton you need :

# Style for the /button/ part.
style myStyle_button:
   background "#0F0"
# Style for the /text/ part.
style myStyle_button_text:
   color "#F00"

screen whatever():
    vbox:
        style_prefix "myStyle"

        textbutton "Click me to quit" action Return()


label start:
    call screen whatever
    "End."

 

[Porcus Dev]

This is better for the style creation, but :



Ren'py do not make its style propagate, so it have to be applied directly to the text.

But there's a way to still simplify this, the

You must be registered to see the links

screen property. It works by defining the prefix that will be used to build the name of the style to apply to each screen statements inside the actual block ; the said name being prefix_statement. Therefore, to apply the same style to all the text screen statements inside a vbox :

# The style need to apply to /text/.
style mybig_text:
    size 42
    bold True

screen two_big_lines:
    vbox:
        # Tell to Ren'py which prefix to use.
        style_prefix "mybig"

        text "line 1"
        text "line 2"

Note that some screen statements, like by example textbutton, are particular because they have more than a single part. Like implied by its name, a textbutton is a combination between the button and the text screen statements. For them, the name of the style is a little more complex :
prefix_outer statement_inner statement

So, for a textbutton you need :

# Style for the /button/ part.
style myStyle_button:
   background "#0F0"
# Style for the /text/ part.
style myStyle_button_text:
   color "#F00"

screen whatever():
    vbox:
        style_prefix "myStyle"

        textbutton "Click me to quit" action Return()


label start:
    call screen whatever
    "End."

Ups, I forgot the "prefix"

 

[Higurashika]

Hi again!

I got this simple code for a small notification.

But I've got an error when I use quick save button. It's like notice_text has no value. How to fix it?

Spoiler

You don't have permission to view the spoiler content. Log in or register now.

 

[recreation]

Hi again!

I got this simple code for a small notification.

But I've got an error when I use quick save button. It's like notice_text has no value. How to fix it?

Spoiler

You don't have permission to view the spoiler content. Log in or register now.

Just asking, did you delete/overwrite the original notify screen?

 

[Higurashika]

did you delete/overwrite the original notify screen?

No.. but what do you mean by "original notify screen"? I just want to make pop-up notification, not to replace vanilla.

p.s. now I see where is the problem. Now I need to figure out how to fix this.

 

[recreation]

No.. but what do you mean by "original notify screen"? I just want to make pop-up notification, not to replace vanilla.

in screens.rpy there is a screen notify(message):
That's the usual notification message you get when saving, you're basically overwriting it. I guess this might cause your problem.

 

[Higurashika]

That's the usual notification message you get when saving, you're basically overwriting it. I guess this might cause your problem.

Yeah this is a problem.. for now I decided to use simple renpy.notify(message) function. It seems pop-up notification is too complicated for me.

 

[Porcus Dev]

Here's a good notification system
https://f95zone.to/threads/image-displayed-in-notification.24761/#post-1527449

 

[anne O'nymous]

Here's a good notification system
https://f95zone.to/threads/image-displayed-in-notification.24761/#post-1527449

There's also a "text only" variation in my mod for super powered, but it need to be searched in the bunch of code in the AONmod.rpy file.

 

[Higurashika]

Guys, I need a help. I got a screen with player's info. But I want to add information there later, after some playing time. How I can do this?

 

[anne O'nymous]

Guys, I need a help. I got a screen with player's info. But I want to add information there later, after some playing time. How I can do this?

Well, you just need to condition the display of the information, by using the

You must be registered to see the links

screen statement.

screen myScreen():

    vbox:
        text "Some information [myVar]"
        text "Other information [otherVar]"
        text "Oh, look, information [aVar]"
        # Here come the delayed information.
        # Will be shown only if /aFlag/ is /true/.
        showif aFlag == true:
            text "And this information come later [delayedVar]"

# By default, do NOT show the delayed information
default aFlag = false

label whatever:
    [...]
    # It's time to show the delayed information
    $ aFlag = true

Alternatively, if the said information have to be in the middle of others and you want to keep a clean and constant presentation, something like :

• Some information
• Other information
• Oh, look, information
• Yet another information

You can combine

You must be registered to see the links

and the

You must be registered to see the links

screen statement.

screen myScreen():

    vbox:
        [...]
        text "Oh, look, information [aVar]"
        if aFlag == true:
            text "And this information come later [delayedVar]" 
        else:
            null height 20
        text "Yet another information [aNewVar]"

Just adjust the value of null to match the number of vertical pixels normally used to display the line of text.

 

[Higurashika]

Thanks again anne O'nymous! How does it work with several vars? Just use aFlag, bFlag, etc or something else?

 

[Higurashika]

Unusual problem. I removed aFlag from code , but the game still sees this var and shows showif statements.

 

[recreation]

Just use aFlag, bFlag...?

Yes.

Unusual problem. I removed aFlag from code , but the game still sees this var and shows showif statements.

If you're using autoreload: Restarting renpy should help.

 

[Higurashika]

If you're using autoreload: Restarting renpy should help.

What is autoreload? Nope, restart didn't work. Maybe I should use something to reload my custom screen?

 

[recreation]

What is autoreload? Nope, restart didn't work. Maybe I should use something to reload my custom screen?

If you're in the game, press ctrl + R. The game will automatically releoad when you make (and save) changes to your script files, that's autoreload.

 

[anne O'nymous]

Unusual problem. I removed aFlag from code , but the game still sees this var and shows showif statements.

If the variable wasn't here, Ren'py would have thrown an error screen. Therefore, it's because the variable is still seen as existing.

It happen when you load a saved game. Ren'py check nothing. It just see that the save say "hey, there's a variable named [whatever], with a value of [something]", and create it. So a variable you thought you removed will still be seen in any game after a load. And reloading the script make Ren'py perform an invisible save/load, which lead to the same problem.


On a side note regarding variable persistence, sometimes it's not the variable but its value that stay. Depending of how you created it, when you restart the game without quitting it, some variables will keep the value they had, and not be reset to their starting value. It's especially true for variable created in an init block.

 

[Higurashika]

It happen when you load a saved game. Ren'py check nothing. It just see that the save say "hey, there's a variable named [whatever], with a value of [something]", and create it. So a variable you thought you removed will still be seen in any game after a load. And reloading the script make Ren'py perform an invisible save/load, which lead to the same problem.

I always quit and restart, when I do changes in code. So this seems a true reason. I use the prev save, thank you!

 

[Higurashika]

I'm here again

Let's say I have a lot of vars.

a = false
b = false
c = false
d = false
...
n = false

Through dialog I may change them or may not. I have a route where they weren't changed, so how could I code the condition like

if a == false and b == false and c == false .... :
jump

I know I can't use so many "ands".

 

[tk99]

If you're in the game, press ctrl + R. The game will automatically releoad when you make (and save) changes to your script files, that's autoreload.

When I press CTRL it skippes/forwardes?