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.
Viewing post in Version 2.6 Release! comments
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.