Entire script file in one tab? [Solved]

[yon]

I've been wondering about this and it's held me up from actually working on coding the final product of YDSP to some extent. Does the entire game need to be in the same, single script file? By the end, it'll be absolutely enormous if I incorporate every single event and permeation.

Essentially, the way I have it set up is major events, minor events, and extra events.
Minor events happen the same way every playthrough. Major events are your routes, and extra events are connected to said route but less intensive.

After the 4th event on each route, it then breaks up into different types, best, good and bad. Essentially, if your affection points is, for example, X>50, you'd get best. 30<X<50 is good, and X<30 is bad.

What I was wondering is, would it be possible to include the route events themselves in other files and simply call them when they're triggered in the game? YDSP is a little simple in that your only interaction is choosing menus when they're presented to you, and events happen on specific days and specific times. Character X's rank 5 event is always on the fifth Tuesday of the game, for example.

I worry that including every single thing in the same script file would make it run terribly and result in more than a few errors. So, I reiterate:

Do I need to put it all into one file, or can it be separated into tabs and called when it's time for said event to play out?

What I think might work is to have the minor events in the script, since they're the same each time, then each character's route as its own file, and each character's extra events as their own files. Would that work? If not, why not?

[thebackup]

Does the entire game need to be in the same, single script file? By the end, it'll be absolutely enormous if I incorporate every single event and permeation.

To put simply, no, you can split the game across scripts. You could have for example:

script.rpy

Code: Select all

label start:

    "blah blah!"

    if affection >= 50:
        call bestRoute
    elif (affection >= 30) or (affection < 50):
        call goodRoute
    elif affection < 30:
        call badRoute

    "should return here after the calls"

bestRoute.rpy

Code: Select all

label bestRoute:

    "the best ending!"

You might want to look at this:
http://www.renpy.org/doc/html/label.html

I hope this is what you're looking for!

[champignonkinoko]

@thebackup

Thanks! That helped!

[Kate]

Right! It's handy to put separate events or routes in different files! Make sure you add at the end a

Code: Select all

"best ending!"

return

That will make sure your game returns back to where you "called" from and then you'll be back in the original file.

[Tayruu]

I'm not sure if you necessarily have to put in a return in this sort of situation, but I try to make a habit of ending things with it as a mental indicator.

IIRC a 'called' label you can use return to jump back a label, however using 'jump' will mean using return goes back to the title screen, as it resets the stack of labels. (... actually the documentation thebackup linked mentions this, so there you go.)

[yon]

Ah, thank you! I'm familiar with labels, but I wasn't aware you could put them in other tabs. I appreciate all the replies.