No Command Line

It is perfectly possible to create a game without a command prompt. Instead, the player can either control the game via the side panel, or though links in the text itself.

To turn off the command prompt, put this line in your settings.js file:

settings.textInput = false

To have the side pane display, set settings.panes to either "Left" or "Right". More options are discussed on the Settings page.

For links in the text, use the "cmd" text processor command. The way these work is that clicking on the link has the same effect as if the player typed in the command. Here are two examples:

{cmd:get boots}
{cmd:drop hat:drop the hat}

Clicking the first will have the same effect as if the player had typed GET BOOTS.

Compared to Twine, etc.

There are several systems out there already for creating games where the player navigates by clicking a link. Twine is probably the most well-known, and I had used it much myself. Why use Quest 6 instead of Twine?

In my opinion it comes down to how you approach the story.

Twine is best for a time-based game. Navigating from one node to another is best understood as progressing from one point in time to the next, and as the player goes through the game time flows from start to end.

Quest is best for a spatially-orientated game, where navigating from one node to another is the player moving from one location to another.