Code Editor Guide - The Results Page - Score

Hello Tales Wordsmiths! Whether you are brand-spankin’ new or just need a refresher, I hope you find these guides helpful. Everything is interconnected, so if you don’t find what you’re looking for here, check out the other guides coming soon!

This guide is for those that are using the Code Editor option, and for those that are using variables in their story.

The Results Page

Every time a player comes to the end of an episode, the app will take them to the results page, where they are always given the option to continue to the next episode and view any comments made on that story. There are a few more things you can add to your results page to give your reader a more game-like experience.

Score

A Score keeps track of variables given during gameplay.

(Note: (location: BLACKOUT) is not needed.)

All you need for a Score is the header, and you need to give the player some variables during the episode:

  | Score | LIE 1, TRUE 1

  NARRATOR
  Will you lie or tell the truth?
  * <#act> Lie -> lie

  * <#act> Truth -> true

  :lie

  [give: LIE]

  You lied, and now nobody trusts you.

  (end)

  :true

  [give: TRUE]

  You told the truth, now everybody trusts you.

  (end)

(Note: The example above uses the jump - > label : method of branching. If you want to learn more about it, keep a lookout for the Branching Methods guide. This example also uses <#act> in the choice lines, which will also be explained in the Branching Methods guide.)

  | Score | LIE 1, TRUE 1

First is Score, which cannot be customized, then the variables (in all caps) that you are giving in the episode that you want the player to collect, followed by a number, which should be the maximum amount of that variable that the player can get within that episode. The variables are separated by commas.

In the example above, the player can only get one LIE or one TRUE variable.

(Note: There is a bug in the TC where it doesn’t show your actual score on the results page, but it does show up correctly on the app. Hopefully that’ll get fixed too, and I’ll be able to put up an accurate picture.)

This is how the score is displayed on the results page. In this example, the player chose to lie. The variable name is shown, the percentage of players that received that same score, and on the far right is the actual score, 1 out of 1, or 1/1. True has 0/1, because the player did not collect that variable. (Sorry again that the picture is not accurate.)

Please note that scores are episode specific, meaning that it will only show variables collected during that episode only. For example, in episode 1, the player collects 1 LIE. In episode 2, the player does not collect another LIE variable. If, in episode 2, you have the score header just like in episode 1, it will not show that the player has Lie 1/1, it will show Lie 0/1, because the player did not collect that variable within that specific episode.

So, score amounts should be customized for each episode. Another example is if in episode 1 the player collects 1 LIE, and in episode 2 can collect 3 LIE, the score would look like this:

  | Score | LIE 3

And it will show how the player did, ⅓, ⅔ or 3/3.

Generally, you should not have a score for every variable you give to your player. Just the ones that are important to the story, that the player can collect throughout gameplay, or that you want the player to know about.

You can have a score for as many variables as you like, they will all show up on the results page as far as I know.

That’s all for the Score guide, if you have any questions or comments, feel free to post below!

3 Likes