First of all if there is a thread for this sorry for making a new one but I could not find it. Secondly I have already looked at the tutorial provided by the choice of games website and could not find anything helpful to what I am trying to do.
Okay now on to what I am trying to do. I have come across this in multiple WIPs and actual games. They would have a section in the stats screen where one could find the definitions and generally more info on the events and/or terms used throughout the book. I was wondering if anyone knew the code necessary to do that is and if so could you please share it with me?
Okay so all I have to do is include that in the choicescript stat file? What i am trying to figure out is how do I make a glossary in choice stats. I already know there is no such command
*label terms Terms
*choice #MANT drive
The term [b]MANT[/b} stands for Magnetically Accelorated Nuclear Tranlight. It is a special type of reactor designed specifically to enable ships to travel at between thirty - fourty times the speed of light. Every ship built by the MC’s people has at least two of these drives built in with the option to add more if the designer feels that it is nessacary.
I literally (and I mean literally—I’m still in bed) just woke up, but I think a *gosub_scene would be more appropriate for a codex, no? Correct me if I’m wrong, but that should allow you to keep your codex on a totally separate file so you don’t clog up your stat file. It would still be available via the stats screen but, I dunno, I think having a codex be a separate file is easier, especially if you know it’s going to be pretty big.
Actually, you would even be able to link it in choices if necessary, especially during a tutorial scene (if applicable).
Okay thanks. I had no idea I could do that. I am literally a noob when it comes to coding and I like to double and sometimes even triple verify things to make sure I did not mess them up
It depends if you want the glossary list to be a giant list on one page or if you want to allow the reader to select which term they want to be defined. This is what it would look like if you want all your terms on one giant page.
*label navigation_menu
*fake_choice
#Return to main stat screen.
*goto main_screen
#Go to codex.
*goto codex
#View character relationships.
*goto character_relationships
*label codex
[b]Codex[/b]
Word: definition.
Word: definition.
Word: definition.
*fake_choice
#Return to main stat screen.
*goto main_screen
#Go to codex.
*goto codex
#View character relationships.
*goto character_relationships
No, when it’s just a *goto or a *gosub, they have to be within the same text file. Whenever you finish playing through what is written in a *gosub, it will automatically take the reader back to where they came from, while a *goto will keep going unless there’s another *goto to return to the original label.
*gosub_scene works like *gosub, where once the player is finished with that particular scene/section, the game springs back to where they came from.
I think I left some specifics out, but let me hop on my computer before I correct myself. mobile is hard y’all
Oh no! It’s no hassle! I was just too lazy to boot up my computer, lol.
Anyway, it’s worth suggesting that you take a look through the ChoiceScript wiki which is an amazing resource when you’re just starting out. It defines all the commands clearly and concisely, and even includes sample code to study.
Okay, looks like the only thing I need to clarify is that both gosubs requires the *return command to spring back to where it came from, it isn’t automatic.
Just wanted to state it even if it’s obvious, but to create a glossary/codex, simply write down the terms and definitions manually like you would normal text.