Cutting the code into different modules for ease of access?

[Argeus_the_Paladin]

As at present, my code is approaching the 7000 mark, and it is becoming harder and harder to properly navigate it. For practical reason, I am considering dividing it into different modules and import them into the main module when the game is run. However, I didn't understand the relevant instruction in the documentation.

Could anyone give me a brief run-through of what I need to keep in mind if I want to do this?

[Showsni]

Why not just use different script files? It's got to be easier than trying to make and import modules...

Ren'Py will run any script files it finds in the game folder, so you can just save different parts of your code to different ones and give them names to help you keep things in order.

[Argeus_the_Paladin]

That's exactly what I am looking for, right there.

Is there any pointer on how the program loads codes in different script files? Or any tutorial I could read about this?

[Showsni]

That's exactly what I am looking for, right there.

Is there any pointer on how the program loads codes in different script files? Or any tutorial I could read about this?

I'm not sure of the specifics, but I believe anything in an init block (regardless of file) will run first. You shpuld only have one start label (or you'll get an error) amongst all the files, and the game will start there. And you can jump to or call any label, regardless of which file it's in.

[Argeus_the_Paladin]

So in file 1 we can have:

Code: Select all

init python:
    # part 1 definitions go here

and in file 2, 3, 4, 5,... n we have:

Code: Select all

init python:
    # part 3, 3, 4, 5, ...n definitions go here

The question is, should all of these files end with return? From dissecting the tutorial it seems to be the case, but there is also the thing that each tutorial modules actually concludes with jumping back to the main tutorial game menu.

So what should it be?

[ScottySeng]

http://lemmasoft.renai.us/forums/viewto ... =8&t=14222

I think the middle of this thread may help. It's about splitting Renpy files.

[Alex]

The question is, should all of these files end with return? From dissecting the tutorial it seems to be the case, but there is also the thing that each tutorial modules actually concludes with jumping back to the main tutorial game menu.

No. The structure of tutorial game code is - the menu in start label from which different chapters are called, so at the end of this chapters should be a return command (to put player back to menu).
In your case, no returns are needed. Just split you code to several rpy-files with its own init blocks screens and ATL definitions and so on. When you'll run your game, Ren'py will treat all this rpy-files as one big file and will execute all init blocks first and start label then.
http://www.renpy.org/wiki/renpy/FAQ#How ... e_files.3F

[Argeus_the_Paladin]

So if I understand correctly, splitting the script into different files have virtually no effect on how it is run, but only how it is organized?

That's perfect. Thanks for the pointer, everyone.