Choose one: [ begin | open | find | free | go ]

+

Choose one: [ end | out | new ]

+

Choose one: [ system | parent | child | terminal | window | menu | home ]

OR

Choose one: [ begin | open | find | free | go ]

+

Choose one: [ system | parent | child | terminal | window | menu | home | end | out | new ]

> This is the longest chapter in the story by far, so if you feel lost or would prefer to read it, enter "full text" to see all of the chapter's inputs and outputs. It will take some time for the full text to load due to the chapter's complexity, so give it a moment.

> Each stage you progress in the chapter...

>> <-- ...will show more of these arrows.

> If there are fewer arrows for an input than you expect, enter the same input again. It will catch up. I want you to see everything.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Chapter 6 Manual (read carefully because there are differences from the Chapter 5 manual)

> Inputs in the command line must be 2- or 3-word combinations that you've pulled from the prompt for the chapter, shown above (with verbs highlighted in bold; every valid input combination will start with one of those verbs).

> Every input should look like this: verb second_word [optional_third_word]

> For example, if your initial prompt is the set of conditions shown above, valid inputs could be "begin end terminal," "open out system," "find new home," "find end child," "begin system," "free parent," "go menu," "go new," or "find terminal," among many others (different 2-to-3-word combinations of words from that initial prompt).

> Note the differences in valid combinations shown in the prompt above. Valid 2-word combinations do not need the words "end," "out," or "new." However, valid 3-word combinations need one of those three words as the second word.

> Inputs with too many or too few words or words that are not from the prompt are invalid, and the terminal will tell you that there is nothing that it can do with the input.

> When you enter a valid input, it will generate an output that will subtly help guide you toward the correct input. That correct input will move you to the next stage within the chapter.

> Your inputs will always have a ->~ icon in front of them by default (but don't type that icon yourself), and the terminal's outputs will always have a > icon in front of them, like this:

->~ input

> output

> When you enter a correct input, you'll know that you've reached the next stage because you'll see an extra > icon in front of the terminal's outputs in that stage, like this:

>> Output in Stage 2.

or

>>> Output in Stage 3.

*****

> When you enter a correct input, the verb you entered as the first word will be locked. You will no longer need to use that verb to progress to the next stage.

> Here's an example. Assume this is your prompt:

> enter whatever word you choose

> If your input is:

->~ choose whatever you

>> And it turns out to be the correct input, as the two >> icons to the left of the output demonstrate, you will no longer need to enter an input with the verb choose to get to the next stage, and every time you enter a valid input that begins with choose, it will simply generate its output from the previous stage(s).

> The goal is not to overwhelm you with duplicate inputs and to make it a little easier for you to choose the correct input as the chapters get more complex.

*****

> An input might generate fewer > icons in the output than you expect.

> Read the output you receive--to help you follow the story--then enter the same input again, and re-enter that input until the number of > icons in the output catches up to your current stage.

> That inconsistency between stage number and the number of > icons simply means that you never entered a particular input on a previous stage.

> Keep in mind that each stage in a chapter generally stands on its own, and an output from an earlier stage usually won't help guide you to the correct input of a later stage.

> But every output is there to help tell Tera's story.

*****

> Type "clear" to clear the output history from the screen.

> Type "full text" if you get lost or prefer to read the chapter as a story. It will show you all of the chapter's inputs and outputs. It might take some time for the full text to load due to the complexity or length.