No longer active

[sil3nt600]

No longer active

[Kato]

You can archive information to stop people copying your files (though if they really want in, they'll get in regardless what you do).

Copied from RenPy.org

Ren'Py supports combining files into a simple archive format. While not very secure, this protects files from casual copying.

By default, all files classified into the "archive" file list will be placed in an archive.rpa archive, which is included in the all file list.

By calling build.archive, it's possible to declare a new archives and the file lists they will be included in. (It's rare to use anything but the all file list, however.) To use an archive, classify files into a list with its name.

For example, the following code will archive images in images.rpa, and game scripts into scripts.rpa:

Code: Select all

# Declare two archives.
build.archive("scripts", "all")
build.archive("images", "all")

# Put script files into the scripts archive.
renpy.classify("game/**.rpy", "scripts")
renpy.classify("game/**.rpyc", "scripts")

# Put images into the images archive.
renpy.classify("game/**.jpg", "images")
renpy.classify("game/**.png", "images")

If an archive file is empty, it will not be built.

Please think twice about archiving your game. Keeping files open will help others run your game on future platforms - platforms that may not exist until after you're gone.

Hope this helps!

[pwisaguacate]

[deleted] Kato beat me there. Also, users would be able to grab screenshots (or record audio etc.) off the game itself anyways.

Don't forget to include some sort of note that your works are not to be modified/distributed in any form.

[sil3nt600]

No longer active

[pwisaguacate]

Clarification

You If you haven't yet, click on "Build Distributions" and hit yes when it asks you if you would like to add build information to the end of options.rpy. Then add whatever lines needed at the bottom of options.rpy:

Code: Select all

    ## Classify files as None to exclude them from the built distributions.

    build.classify('**.rpy', None)
    build.classify('**~', None)
    build.classify('**.bak', None)
    build.classify('**/.**', None)
    build.classify('**/#**', None)
    build.classify('**/thumbs.db', None)
    
    ## To archive files, classify them as 'archive'.
    
    build.classify('game/**.png', 'archive')
    build.classify('game/**.jpg', 'archive')
    build.classify('game/**.ogg', 'archive')

The exact above code will exclude .rpy files from the built distributions, and archive.rpa will be built with all .png .jpg .ogg files in your game folder stored in it.

* http://lemmasoft.renai.us/forums/viewto ... 64#p266495

So yes, it's located at the bottom of options.rpy.

[sil3nt600]

No longer active

[pwisaguacate]

But I want the Yes option to to apply to other labels as well.

It's not very clear what you're asking, but it looks like a routing thing. Use variables, for example:

Code: Select all

menu:
    "Accept invitation.":
    jump accept

    "Decline invitation.":
    jump decline

label accept:
    $ accept = True
    ...

label decline:
    $ accept = False
    ...

label chapter2
    ...
    if accept:
        Do something.
    else:
        Do something else.
    ...

This will allow you to stay on the main storyline with variables set to certain values depending on the player choices.