Updating from 6.99.14 to 7.1.3?

Discuss how to use the Ren'Py engine to create visual novels and story-based games. New releases are announced in this section.
Forum rules
This is the right place for Ren'Py help. Please ask one question per thread, use a descriptive subject like 'NotFound error in option.rpy' , and include all the relevant information - especially any relevant code and traceback messages. Use the code tag to format scripts.
Post Reply
Message
Author
User avatar
arty
Regular
Posts: 120
Joined: Sat Jan 06, 2018 11:55 am
Completed: White Monday
Projects: HATE is a 4 Letter Word
Organization: KATHARSIS ART
itch: artys-games
Contact:

Updating from 6.99.14 to 7.1.3?

#1 Post by arty »

Hey guys,

I recently released my first game. I was still using 6.99 to make it, since I started it a year ago and never bothered updating Ren'Py.
Now I want to update it, but I'm worried that if I then make updates for my game, I may break things.

I'm aware that there is a list with incompatibility changes, but I simply don't understand some of them. Or rather.... none of them, basically. ;_;
Can someone explain like I'm five years old?

The ones I'm talking about:
  1. The Dissolve(), ImageDissolve(), and AlphaDissolve() transitions now default to using the alpha channel of the source displayables, as if alpha=True was given.
  2. Ren'Py now defines automatic images at init 0, rather than at a very late init level. To revert to the prior behavior, add to your game
  3. When an image is not being show, say-with-attributes now resolves a side image, rather than just using the attributes given.
  4. Ren'Py's window auto function will now determine if dialogue or a caption is associated with a menu statement, and will attempt to hide or show the dialogue window as appropriate.
The same goes for the general changes:
  1. The new SetLocalVariable() and ToggleLocalVariable() actions make it possible to set variables inside used screens. (What is a used screen?)
  2. Ren'Py can now automatically save the game upon quit, in a reliable fashion. (As compared to the previous autosave, which could fail or be cycled out.) This is controlled by the _quit_slot variable. (How do I use this?)
Sorry for so many "questions" at once. I just don't wanna mess up a perfectly functional game.

Cheers, and thanks!

User avatar
trooper6
Lemma-Class Veteran
Posts: 3712
Joined: Sat Jul 09, 2011 10:33 pm
Projects: A Close Shave
Location: Medford, MA
Contact:

Re: Updating from 6.99.14 to 7.1.3?

#2 Post by trooper6 »

My advice would be to make a copy of your game, give it a new name (Like Game2), build a new project, put your old files in the new project, and see what happens. The only big thing you’ll have to do is deal with translating your GUI stuff over to the new system.

But just try it and experiment at bit.
A Close Shave:
*Last Thing Done (Aug 17): Finished coding emotions and camera for 4/10 main labels.
*Currently Doing: Coding of emotions and camera for the labels--On 5/10
*First Next thing to do: Code in all CG and special animation stuff
*Next Next thing to do: Set up film animation
*Other Thing to Do: Do SFX and Score (maybe think about eye blinks?)
Check out My Clock Cookbook Recipe: http://lemmasoft.renai.us/forums/viewto ... 51&t=21978

User avatar
arty
Regular
Posts: 120
Joined: Sat Jan 06, 2018 11:55 am
Completed: White Monday
Projects: HATE is a 4 Letter Word
Organization: KATHARSIS ART
itch: artys-games
Contact:

Re: Updating from 6.99.14 to 7.1.3?

#3 Post by arty »

Hmm that's probably the best idea, yeah... Thanks for the tip.

Post Reply

Who is online

Users browsing this forum: Semrush [Bot]