error-message
success-message
saving-message
warning-message
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
Abandon All Hope, All Ye Who Enter Here
This is a project dump of my unreleased, unfinished ZZT titles.
I was making those when I was 11-12 years old, and as such - beware of the
impressively low levels of maturity and high levels of fixation on specific
topics, fandoms or genres. You have been warned.
The files here are listed in order of playability/completion/quality.
They have been preserved mostly unedited.
* AKAASTWO.ZZT - The unfinished sequel to "A Knife and a Stick". Likely to
be the most playable entry in the archive, as this build was made
for "streaming" or whatever 12-year-old me meant by that anyway.
* OBBIP.ZZT - "One Bon Bon is Poison", the unfinished part 1 of what I assume
was meant to be a multi-part epic that was way beyond the capabilities of
then-me.
* DOWNFALL.ZZT - "Downfall ZZT", the first three boards of a planned game
about, well, the downfall of z2 and related communities. Made just a little
bit early for that.
* DEFINEZ.ZZT - "Define ZZT", a title screen and a menu. As a bonus, I have
included GreaseMonkey's original music code in an extra board, as it is
slightly longer than what was used in the menu. I do not have the DNL_*
files used by the menu's "Help" option - they may well have never existed.
* DEVNULL.ZZT - "/dev/null", once again only a title screen and menu ever came
out of that. I guess I liked menu engines.
* COLLAB08.ZZT - An unfinished submission for nupanick's "Collabyrinth".
The Floating Board, which is unfinished in this version, was left empty
in the official release.
* PUZZLING.ZZT - Your guess is as good as mine.
For preserving history in spite of the shame (also, it's only fair),
asie, 29/08/2018
This section tracks other objects or external resources.
The external resources, such as tarballs or Git repositories, are then available as part of the object. Their files can be considered local to the object and usable in scripts or as part of a build process.
For resources that are only to be used as part of the build or runtime of the object, it is best to describe those local to those sections.
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
Confirm message?