avatarbr wrote: Sun Sep 12, 2021 3:11 am
Thanks...that worked.
Another question, probably impossible, but looking at the files I was thinking:
How hard would be to open for other people collaboration? Like, I want to create a encounter for the dojo, and that would play after all the official encounters already happened.
Would be possible to include a .rpy file and the images, if the game had a code for that? or the code need to be specific for a file?
Anyway, I was just thinking about the possibilities.
I never used github and therefore don't know about the possibilities.
As for renpy itself that's basically very easy as file names/ file places and stuff doesn't matter at all. All .rpy files in the game folder go effectivly into one big file when the game is started. The reason I split it up in a bunge of files was only cause I needed orientation when I picked up the project (understand the code and its sections) and then wanted to keep a structure.
So, technically it's not that difficult as long as it should not interact the the main story, which would mean you needed dependencies, flags and things.
Imagine a place where repeatedly and randomly teases show up. Say the dojo (after all dediacted story-relevant teases there are done) everytime you visit.... or the intimate room or the pool.
In a say "new teases.rpy" file (just to keep the file seperate from the others but as I said that doesnt matter at all) someone could write a new tease for the dojo like
label new_dojotease1:
show newpic1 at truecenter with dissolve
....
code
....
return
As for the dojo (if I remember correctly) and some other places like the pool what happens is, it is just calling labels randomly from a list of labels. And renpy works in a way that it actually doesnt matter in which file something is written.
So say currently there would be in the dojo section (simplyfied and not in proper coding) something like "randomly select a label name from ("tease1", "tease2", "tease3") then call that label"
What then is to be done in case a third person had written the "new_dojotease1" in a new (or inside any) file is, the list in the dojo with available teases must be amended. Now being (tease1, tease2, tease3,
new_dojotease1)
Something like that is pretty easy. Would only get more difficult in case you want to make it more sophisticated like "dont pick same tease twice in a row or on same day".
As for pics:
Providing pics (in case you don't want to use pics already used) is necessary but easy. Just make the pic available in a folder (name of the folder doesnt mater) and put the folder into the root/images folder. That's it. The names of the pics must match the names in code.
tl;dr
It is abolutely possible. And - came to my mind - slightly more elegant way than mentioned above: I could build, say in the dojo, a line of code at a "safe place" storywise (i.e. after all story relevant dojo teaes are done) saying
call newdojoteaseselection
In a (preferrably) new file named however you wish there would be:
label newdojoteaseselection:
randomly select from
("newtease1", newtease2",....)
call selected
return
And the third person who wants to contribute writes (preferrably) in this file (but could be any) his tease with a name. Like
label newtease9:
...
return
And adds "newtease9" to the list of available teases in the above shown list so that it is then ("newtease1", newtease2",
newtease9") As you notice the file names dont matter only the label names matter and are called.
That's it.
Name of pics must match the code but no overly complex folder structure necessary. Name of folder also doesnt matter just put them in /root/game/images/YOURFOLDERNAME/
For collaboration one could also think of making a "collaboration folder" and put all new pics in there.
... and experimented with coding for how to build vids in.