Version 2.6 Release!



You read that right everyone: Version 2.6 of the GUI Template is finally here! It's been a long time coming so we apologize for the wait, but we did manage to test it with both Ren'Py 7.5.1 and 8.0.1 and can confirm that it works as intended.

Changelog:

  • Eileen sprite was updated to a newer version of Mannequin
  • History Screen was updated to the latest version of the Separated History Code, which now has true variable message heights!
  • New code comments to better explain some functions, some TODO reminders in areas you should customize before release
  • Optimized code in various places
  • All new scrolling credits code, courtesy of bobcgames
  • Added a line for custom cursor images
  • Added a line to ensure that hyperlink text in the interface matches the rest of the interface typeface
  • Fixed issues between Typeface, Font Size, and Line Spacing occasionally having either all or no options selected on the Preferences screen
  • New custom screenshake effect implemented, with ability to switch back to the default hpunch
  • Minor adjustments to the demo script
  • The option to change the ADV and NVL textbox image was removed

Regarding the last point: Many developers we spoke to did not utilize the feature, and we could not find an efficient way to tie the textbox and text color together. Tying too many actions to a single button has caused issues in the past, and we'd like to ensure that the template is easy for most developers to use. Thank you for your understanding!

Please be sure to download the new template to use in your future projects. If you encounter any errors we may have missed, please leave a comment on the page and we'll do our best to fix them in a more timely manner this time (we'll try to, at least!).

Thank you for your time, and may your development endeavors succeed!

Files

GUI_Template_v2.6.zip 12 MB
Jul 22, 2022

Get Ren'Py All-In-One GUI Template

Download NowName your own price

Comments

Log in with itch.io to leave a comment.

One thing that's bugged me for a couple of versions is the Music Room Previous/Next button functions are swapped (Clicking Next plays the previous track and vice-versa).

I tried fixing this by renaming the audio files with prefixes (01, 02, etc) and messing with $redefine_resources but kept getting errors.

I ended up having to edit multiple files to get it fixed. =/
Yes, I could have just swapped the actions on the buttons in extras.rpy, but my OCD wouldn't let me. lol.

Also, it's a LOT of work to adjust the template and GUI for 1280x720.

Hi there, we went back into the extras.rpy file to check the behavior of the Music Room and the buttons are supposedly labeled correctly, according to the documentation.

            hbox:
            # Buttons that let us advance through tracks.
                textbutton "Previous" action mr.Previous() alt "Previous Song"
                textbutton "Next" action mr.Next() alt "Next Song"
            null height 20

However, upon testing the template, it seems that your observations are correct: clicking on Next will cause Ren'Py to play the song listed above (or loop back to the bottom of the list). We'll notify PyTom about this bug unless it is intended behavior.


We also apologize if the template is difficult to adjust for 1280p. Have you tried using the Change/Update GUI button on the Launcher?

I have NOT tried update GUI.. I will try that, thanks!

For the music room, I noticed that you have the list in different orders in the code in a few places...
I noticed that by default, the next/prev was using the order you have in the definitions.rpy music init section, which is reversed compared to the buttons on the music room screen and is ALSO the alphabetical order of the filenames which is the (reversed) order they play in.
I don't think it's a Ren'Py bug.
This is why I thought that just renaming the audio files would be the easiest fix.

(+1)

RE: Music Room

You're right on the money with that one; the order that the songs are defined in do affect the way the actual Music Room plays in. We'll be fixing that in the next update!