Frequently asked questions

Yes. You can export gamebooks in PDF and RTF formats, however they will not have all the features included in the HTML version, for obvious reasons. You cannot have a dynamic content RTF gamebook, although you can write a simple branching path book without using variables and conditions.

You can export your book in a single-file HTML format, just like the one in our demo book. This format lets the writer use dynamic content such as conditions and variables, which can create advanced gameplay mechanics: character attributes, inventory, shops, experience levels, dynamic battles and much more.

HTML books can be read on most modern platforms (all the major operating systems, tablets and most smartphones) and are compatible with most screen reader software. With the Developer Edition you can also export in the HTML Mobile format, optimized for mobile devices, which allows further customization and additional perks.

Yes. Larger pictures are resized to a thumbnail which the reader can select to view full size.

Yes. There is an option to generate a PNG image showing a colour-coded map of all paths and locations in your book.

Yes. It includes a random number generator you can use to skill-test or luck-test the reader. Two examples:

• You are trying to break through a wooden door: you succeed if the sum of your strength attribute and a random value is greater than 15, otherwise you fail.
• You are looking for an elusive creature you need to kill before advancing: each time you visit its lair a random number is rolled, and if it is greater than 10 the creature is there.

No. This is for gamebooks and text adventures only. The graphics you can use are limited to pictures you provide.

Most of what you need is covered by three simple commands: [cond], [op] and [jump].

• [cond] checks whether a condition is true: whether you own a certain item, whether your strength is above a value, whether you killed an enemy, whether you have enough money. If it is true, its associated text is displayed.
• [op] declares and edits variables. If the reader collects money, you use an operation to increase their money value.
• [jump] creates choices and branching paths.

These are used in a bbcode-like fashion, which we find easiest to understand and to use in a text editor:

• [cond=$Strength>10]This text is shown only if your strength is greater than 10[/cond]
• [op]$Money = +50[/op]
• [jump=Page 3]Go to page 3[/jump]

There are many other utility commands for text formatting, reader input and more.

We aim to provide the simplest and most complete tool in the field of gamebooks and text adventures. We have looked through the other software out there, and none of them offers both the ease of use and the full feature set.

Gamebook editors are usually limited and poorly structured: more often than not they lack a dynamic content system (no variables, no conditions, no RNG), they force you to copy-paste pages for every choice, or their internal navigation makes large books impossible to work with.

Our tool includes dynamic content and a tree-view of the book structure, the tracemap, and a jump-detect system that shows every jump from and to a page as buttons you can navigate with. It also has the features of an advanced text editor: keyword highlighting, colour coding, auto-complete and text folding.

Text adventure editors, on the other hand, are complete but complicated. Most require programming knowledge, and those that do not come with 30+ pages of documentation for features you will never use. Our tool requires no programming knowledge, and detailed documentation is provided anyway.

Of course. Go to the upgrade page and follow the instructions.