Feyster
Formerly 'Pitey'
- Oct 7, 2017
- 19
- 21
Deleted
- Thread starter Feyster
- Start date
You can do it in many ways, you could have a tree diagram for each choice... That is assuming you know how your story starts and how it ends.
If you are writing and making stuff up as you go, it is a risky and unpredictable process, could go either way.
If you are writing and making stuff up as you go, it is a risky and unpredictable process, could go either way.
No, my way of doing things is having a start and an ending (or endings), at least when it comes to the story itself.
Having a starting and ending point allows me to plan choices and know exactly where they will go.
The way I would approach it if I was to make a VN, is this.
1. I start with the basic idea. Where it starts, the middle, and the end. These aren't very in-depth. They're just enough information to give me some references.
2. I then answer the 5 W's, Who, What, Where, When, Why and How. This is repeated for the middle and end sections.
3. I further break down the start, middle, and end into chapters. This allows me to concentrate on specific parts of the story without being overwhelmed by the overall story. Of course I'll occasionally check back to make sure the story is still coherent.
4. Make sure that my writing doesn't complicate the transition process over to whatever game engine I'm using. What I mean by this is, writing a story doesn't necessarily translate correctly into code. So not to make extra work, I write my stories in a way that takes the least amount of effort to transition into the appropriate game engine.
A quick example is, instead of writing "John wasn't fully aware that he took someone's undergarment" I would do this
*Image: John holding an undergarment*
John: You wanted to talk to me about something.
Suzy: You didn't have to steal those. I would of kindly handed them over to you.
*Image: John turns around, bring undergarment down, hands them over.*
John: Definitely didn't steal them.
In this way, when I take a break or whatever and come back to my writing I understand the structure of my story.
5. The coding phase. This is where I start implementing my variables and such. This goes back to #4. By reading my writing, I can easily determine if I need to do extra stuff or not, if not, I can pretty much just do a Copy/Paste where appropriate.
Mind you this is broad overview of my workflow. Don't take this at face value as there's many ways to approach this and the structure is different depending on the game engine used. The main takeaway is understand where your story starts, where the middle is and how it's going to end. From there it should give you a basic ideal of how you want to structure your story so that you can write it while maintaining a balance transition into the game engine of choice.
1. I start with the basic idea. Where it starts, the middle, and the end. These aren't very in-depth. They're just enough information to give me some references.
2. I then answer the 5 W's, Who, What, Where, When, Why and How. This is repeated for the middle and end sections.
3. I further break down the start, middle, and end into chapters. This allows me to concentrate on specific parts of the story without being overwhelmed by the overall story. Of course I'll occasionally check back to make sure the story is still coherent.
4. Make sure that my writing doesn't complicate the transition process over to whatever game engine I'm using. What I mean by this is, writing a story doesn't necessarily translate correctly into code. So not to make extra work, I write my stories in a way that takes the least amount of effort to transition into the appropriate game engine.
A quick example is, instead of writing "John wasn't fully aware that he took someone's undergarment" I would do this
*Image: John holding an undergarment*
John: You wanted to talk to me about something.
Suzy: You didn't have to steal those. I would of kindly handed them over to you.
*Image: John turns around, bring undergarment down, hands them over.*
John: Definitely didn't steal them.
In this way, when I take a break or whatever and come back to my writing I understand the structure of my story.
5. The coding phase. This is where I start implementing my variables and such. This goes back to #4. By reading my writing, I can easily determine if I need to do extra stuff or not, if not, I can pretty much just do a Copy/Paste where appropriate.
Mind you this is broad overview of my workflow. Don't take this at face value as there's many ways to approach this and the structure is different depending on the game engine used. The main takeaway is understand where your story starts, where the middle is and how it's going to end. From there it should give you a basic ideal of how you want to structure your story so that you can write it while maintaining a balance transition into the game engine of choice.
You will end up making half of it up as you go along, there is no getting around that, we all do it, the trick is to make variables wherever you can. If you have written in a script somewhere that John goes to the beach, but when you get to that bit the story as flowed differently and he goes to the shop instead. You should make a variable $ john_shop = True just in case you ever want to reference that situation in the future.
To elaborate a bit more, at the start you should have default variables set for things you know/plan, but don't be afraid to not use them and add more as needed.
To elaborate a bit more, at the start you should have default variables set for things you know/plan, but don't be afraid to not use them and add more as needed.
What do you mean make variables? Are you talking about the design phase? Because eventually you'll have to make variables in Ren'py.
moskyx
Forum Fanatic
- Jun 17, 2019
- 4,448
- 15,017
Sure, you just create a menu choice, then jump to the story. Variables are not really needed
Python:
label start:
"This is John. Where's he going to go today?"
menu:
"He's going to the beach":
jump JohnBeach
"He's going to the Mall"
jump JohnMall
label JohnBeach:
"John arrives at the beach."
"His story..."
return
label JohnMall:
"John arrives at the Mall."
"His story..."
return
One thing you should absolutely do is set up rpy files for every main-route you're planning to create, so you can have individual tabs for each of them in your editor. Do not plaster your entire script into the main script file, that'll be a nightmare to navigate later.