Do you know what happens to knights who dare oppose me? They’re soundly beaten, torn to shreds, reduced to mere ashes, utterly and completely obliterated. No one can defeat the great and mighty (and—dare I say—quite handsome) Knarr'ator. I’m the best, most awesomest dragon there ever is, was, and will be. And yet here you stand, just a character in my story, challenging me like the fool you are. If you think you stand a chance against me, you’ve got another think coming.

But by all means, go ahead and try.

It seems you’ve found yourself within
The troublesome affair
Of trekking through the timberland
To slay the dragon there.

They claim it a ferocious fiend;
However will you fare?

My entry for the December 2016 Ballad Contest.

Illustration: Der Kampf mit dem Drachen by Ludwig Richter

___ ___ ____ ___ ____ _____ _______. _____ ___ ____ ___ ____ _____ ____ _ ____ _________ ____ ___ _____. _ ____ ______ ____ _ ___ __ _______, ___ ___'_ ___ ___ ___ ____ __ ___ ______ ______ _____! ___ __? _____? __, _____ ____.. _____ ____, ____ ____ ___ ____!

French dragons.

Lorem ipsum dolor sit amet, iudico mucius praesent eu vim. Cu has indoctum maiestatis referrentur. Vix eu omnes explicari, unum tacimates has et. Mei cu recteque hendrerit, an esse voluptua nam.

Te per impedit percipit consetetur, mel cu quaeque convenire. Liber utinam probatus cu eam. Id vulputate voluptatum sed. Mentitum adipisci postulant no mel. Esse omnis quaestio et eos.

Vides meam barbam, et amas eam!

Image by Acrid.

Dvořák? Check.

Dragon? ...Check.

Kobold? Chick.

Test Test Test Test Test Test Test Test Test Test Test Test Test

The only thing I want is the last thing I need.

You can use "

IF %VAR = 1 THEN $PAGETEXT := ""Name,"

Pretty simple fix. You're using the element itself instead of its value.

const astring64 = document.getElementById('pbForm').elements.SS.value;

I'd also say consider using alternatives to document.write (it has some weird behaviors). In this case, you can write the string to the inspect element console with console.log()

Yeah, all the info is stored in the one story state input. The system will interpret a lot of variable names as valid, so that's the safest portion to modify. Even if they're too long or oddly named they'll still persist over page changes; however, if it's got a weird name don't expect it to work in a CYS script.

Oh yeah. The old method of one letter per variable would not have cut it there lol.

It's possible! The story's state is always present on the page in a hidden input, document.getElementById("pbForm").elements.SS

Its value is a base64-encoded string. If you decode it with atob() you'll see it's got five pipe-separated groups of values:

1. The story id and the current page id
2. A history of every page id visited ordered from most to least recent
3. Key/value pair of link id and # of times clicked
4. Key/value pair of item id and # of times used
5. Key/value pair of variable name and value

The first two are comma separated, but for the last three, the pairs are separated by semicolons and the key and value themselves are separated with commas.

If you're storing an integer, it's as easy as parsing that string, changing the variable, reincoding with btoa(), and updating the input's value.

If you're trying to save noninteger values, it's more involved but doable. Internally, variable's names are not strictly enforced, so you can actually store data in a variable's name (just remember to still give it a dummy value). You could for instance include the key/value pair JS:eyJ4IjozMiwieSI6MCwieiI6MTZ9,0 and that would persist a stringified JSON object of xyz coordinates.

I don't have time to provide a bigger snippet of code right now, so I hope this information is usable! I do have a simple example of it being used here (the long variables page, not the multi-variables one).

I'm the first to discover Gay Dragon Husband so I've won as far as I'm concerned.

You can make up a variable on the fly. It will default to zero and any value it's given will persist like any other variable.

Gryphon and Mizal are right about nesting. AND, OR, and NOT work with = and !=, but there's a bug that breaks them when less/greater thans are involved.

I don't believe you.