Character Creation

Some text adventures leave the protagonist an empty slate, with no background or even a specific gender. In others, the protagonist is a certain person, and for the course of the game the player assumes the role of someone devised by the author. The third option is to let the player choose - afterall, that is the nature of the genre.

To do that in Quest involves setting up a start script on the game object and asking the player a series of questions.

We will look at various ways of doing that, starting with the most basic.

Just A Couple of Questions

Go to the “Script” tab of the “game” object. The start script is at the top. Set the script to print a message prompting the player, then select “Get input” from the “Output” options. Set it up like this:

In code view it will look like this:

    <start type="script">
      msg ("Let's generate a character...")
      msg ("First, what is your name?")
      get input {
        player.alias = result
        msg ("Hi, " + player.alias)
      }
    </start>

The important part is the “get input” command, which grabs the next thing the player types and puts it into the string variable “result”. This is then used to set the player alias.

The game has to wait for the player to do something, and to ensure it does all subsequent code goes into its own block (that is, the indented part between the curly braces).

If you want to ask several questions, you need blocks with blocks within blocks. This is perfectly possible in the GUI view, but starts to get a bit messy, so seriously consider doing this in code view.

In code view it will look like this:

    <start type="script">
      msg ("Let's generate a character...")
      msg ("First, what is your name?")
      get input  {
        player.alias = result
        msg ("Hi, " + player.alias)
        show menu ("Your gender?", Split ("Male;Female", ";"), false) {
          player.gender = result
          show menu ("Your character class?", Split ("Warrior;Wizard;Priest;Thief", ";"), false) {
            player.class = result
            msg (" ")
            msg (player.alias + " was a " + LCase (player.gender) + " " + LCase (player.class) + ".")
            msg (" ")
            msg ("Now press a key to begin...")
            wait {
              ClearScreen
            }
          }
        }
      }
    </start>

I am using the “show menu” command this time, to limit the player’s choices, in the first instance to either “Male” or “Female”. A menu needs a string list containing the options, and Split gives a quick way to create one:

  Split ("Male;Female", ";")

The “set menu” function also takes a string, the prompt for the menu, and a Boolean signaling if the player is allowed to click cancel (which we do not want in this case). As before, the result goes into a string variable called “result”.

After also asking for the character class, the screen is cleared. The “wait” command waits until the player presses a key before running its block.

Many Questions

If you want to ask a series of questions, you are better off breaking the process up into functions, one question per function.

As an example, we will ask the same three questions. I suggest naming each function “CharacterCreation” followed by the question name, so we start with “CharacterCreationName”. No parameters or return type.

msg ("Let's generate a character...")
msg ("First, what is your name?")
get input  {
  player.alias = result
  CharacterCreationGender
}

Then “CharacterCreationGender” - note that the next question depends on the answer given here:

msg ("Hi, " + player.alias)
show menu ("Your gender?", Split ("Male;Female", ";"), false) {
  player.gender = result
  if (result = "Female") {
    CharacterCreationClassFemale
  }
  else {
    CharacterCreationClassMale
  }
}

Then “CharacterCreationClassFemale”. We can use the result to set attributes of the player (which would all be zero by default) and give some clothing too:

show menu ("Your character class?", Split ("Amazon;Witch;Priestess;Thief", ";"), false) {
  player.class = result
  switch (result) {
    case ("Amazon") {
      player.strength = 3
      player.agility = 1
      fur_bikini.parent = player
    }
    case ("Witch") {
      player.magic = 4
      black_robes.parent = player
    }
    case ("Priestess") {
      player.magic = 2
      player.agility = 2
      white_robes.parent = player
    }
    case ("Thief") {
      player.agility = 4
      black_catsuit.parent = player
    }
  }
  CharacterCreationBackground
}

Then “CharacterCreationClassMale”:

show menu ("Your character class?", Split ("Barbarian;Wizard;Priest;Thief", ";"), false) {
  player.class = result
  switch (result) {
    case ("Barbarian") {
      player.strength = 4
      fur_thong.parent = player
    }
    case ("Wizard") {
      player.magic = 4
      black_robes.parent = player
    }
    case ("Priest") {
      player.magic = 2
      player.strength = 2
      brown_robes.parent = player
    }
    case ("Thief") {
      player.agility = 4
      black_catsuit.parent = player
    }
  }
  CharacterCreationBackground
}

You can easily add further questions in the same manner. Or indeed to insert a new question between two existing one. Just make the previous one point to the new, and have the new one point to the next.

You should consider carefully if you want the player to know what bonuses she will get for each choice. If you decide to do so, she is likely to pick choices that maximise one attribute. On the other hand, if you choose not, she may end up with a mediocre character that is not good at anything.

A Creation Room

A useful trick is to start the player in a blank room, with no exits, description or objects. This will prevent the player doing anything until the character creation is over and nothing will be displayed in the panes on the right.

At the end of the creation process, move the player to the start room. This will conveniently trigger the description for that room, setting the scene.

A Note About Random Stats

You may be tempted to generate stats randomly. This is more in keeping with traditional tabletop RPGs, though I think most are moving away from that nowadays, and in any case they still offered a way to reject the worst values or to assign then to attributes as you choose.

There are two big problem with random stats. The first is the player may end up with a terrible character who dies at the first encounter, barely able to swing a sword. The second is the player may end up with an incredible character, able to sweep past any hurdle without breaking a sweat. Then there is the very real temptation for a player to keep generating new characters until she gets one that is great at everything.

---