7 November 2013
So Quest is itself now almost as old as I was when I started writing it. But what got me started on it in the first place?
You’re probably expecting me to say something like this… I’d been interested in text adventure games since their heyday in the 1980s. On my family’s home computer, I got hooked by classic games like Zork, Hitchhiker’s Guide To The Galaxy and Planetfall. Such wonderful worlds of the imagination! Such crafty puzzles! I would spend hours drawing maps on squared paper and looking out for grues and giving myself eye strain and…
Well, no. That’s not how it happened. I never played any of those. In fact, I was never really into text adventures at all.
But then, they were before my time. I was just a bit too young. I first dabbled with a computer in, oh, about 1990 or so. We had an Acorn Electron in our house. We did have a couple of text adventures for that - we had a copy of Acornsoft’s Sphinx Adventure (never really played it, couldn’t get anywhere, found it boring) and my dad had typed in the listing of a game called Necromancer from Electron User magazine. Which never quite worked properly, as something had been mis-typed somewhere along the line.
So I was just never that interested in text adventures. I was more into playing whatever shareware games had found their way onto my PC - Commander Keen, Wolfenstein, Doom and so on. But what I was much more interested in was creating my own. I probably spent more time in front of QBasic than any game. And that is where it all begins, really.
Schoolboy Humour
In 1994, at the age of 12 I started secondary school. The IT lab there was open at lunchtime for anybody to use. So instead of running around getting exercise, or loitering somewhere else, me and my friends played around with the computers. They were probably 486s, running MS-DOS 6 and Windows 3.1. They were connected to some kind of network but there was no internet access - we’d barely heard of this internet thing anyway back then. There wasn’t a whole lot to do other than write silly little programs using QBasic (or Visual Basic 3.0, which was also installed) so that’s what we did.
After my schoolfriend Martyn moved house and went to a different school, we kept in touch by writing letters to each other - this being a time before either of us had an email address. We would enclose 3.5” floppy disks to share our latest programming efforts. It was in fact in Martyn’s first letter, around January 1995, that he sent me a game he’d written called “Sid Snibble and the Curse of the Curry Stain”.
I still have a copy, in a heavily nested folder full of archives of archives, and I can still run it today using QB64. It looks like this:
It was a text adventure, but even this had a graphical element to it - you didn’t walk around the game by typing NORTH, SOUTH etc., you moved an ASCII face around with the arrow keys. When you entered a location, you could look at things, speak to characters, pick up items and so on - all in an attempt to solve the mystery of what happened the night before, and why you woke up in the middle of the road in a strange town with a large curry stain down your shirt.
This looked fun. I could write something like this. It would be hilarious! And so I set to work, doing what I’d always done - copying Martyn’s ideas, but doing them a lot worse.
So, in April 1995 I wrote my first text adventure game.
It was called… well, there’s no easy way to put this. I don’t want to rewrite history or tell a lie. I was young and the game was only for me and my friends. It was called ”Where’s My Nob?!”
How I wish that weren’t true. How I wish I could sit here and tell you the story of how I poured my soul into a creative work of genius, a work of art, a literary masterpiece. With a title like that, maybe I could claim that it was an earnest work exploring gender issues. But it wasn’t. I was 12. The game was an excuse for a load of the kind of sophisticated humour that 12 year olds are known for. Featuring locations such as Dracula’s castle, a teacher’s house, a corner shop, a dairy, a Skoda dealer and Potato World.
So, a throwaway game that should be played by nobody. But for me, a 12 year old boy who didn’t do any kind of creative writing, it was a fun thing to do that got some kind of creative juices flowing.
[Aside: Although it’s not a work that I would ever want anybody to see - indeed, I would be absolutely horrified - I think what it represents is something that still persists as I develop Quest today. Specifically, although I want Quest to be a useful tool for building very high quality works of interactive fiction, there is still a need for something that allows people to create their own Sid Snibbles (and, er, to find their own Nob? I think deep down my sense of humour remains the same). To give people a way to express themselves, to allow them to develop their artistic sense, to allow them to get started, and then to improve their craft. It’s easy to be snobbish about this kind of thing, and to moan about low-quality games, but if we didn’t have bad text adventures, it’s unlikely we would have very many good ones either.]
Anyway, back to my, er, game. I sent it to Martyn on a floppy disk together with a second one called “Make Mrs Booth Friendly!”, a game about my French teacher. Also on that disk, I included a terrible chatbot, “Dr Mad!” who would diagnose your illness, and a fortune teller called “Sadistic Smeg”.
Over the following months I wrote some more text adventure games, always full of in-jokes about school, only ever written for my friends, and never to be seen by anybody else ever, certainly not now. “It’s Mad!”, “Fantasy Land!”, “Park Parade Adventure!” and “The Town of Terror”. It seems the running theme was titles with exclamation marks.
Making Text Adventures for Windows 95
Fast forward a few years to 1998, when I’d started dabbling with Visual Basic 5.0 - which meant I was no longer stuck writing programs for DOS, I could create programs for Windows instead, featuring buttons and menus and message boxes and pictures and everything. I was rather stuck for ideas though. I’d spent some time working on a virtual pet, which were all the rage back then, but wanted to try something a bit meatier. I’d just finished my GCSE exams and was looking for something to keep me occupied over the summer break before I started sixth form. I thought back to the text adventures I’d written, and wondered - what would a text adventure game for Windows look like?
I decided to write myself a little engine before writing a game, so I wouldn’t have to hard-code everything like I’d done in QBasic. I started coding something that would take in a simple text file which would define all aspects of the game, and handle things such as allowing players to save their progress.
It turned out that I was actually far more interested in creating the engine than I was in writing a game anyway, and I was interested to see what other people might come up with if they used my system. At the time, I was fairly ignorant of any pre-existing systems which would do a similar thing to mine, until somebody suggested I take a look at the rec.arts.int-fiction newsgroup. I started checking out the competition, and reading about Inform and TADS. It was clear to me that they were difficult for newcomers to use (this was before Inform had a natural language syntax - the syntax of Inform 6 still looks bizarre to me), so it looked like I should be able to get people interested in what I was doing.
I released Quest 1.0, and it looked like this:
(Those two globes were animated and bounced back and forth between the edges of the screen. For some reason.)
Quest 1.0 loaded text files which were in a simple format I’d devised, called ASL - Adventure Scripting Language. The syntax was simple, designed to be coded by hand using Notepad or similar - there was no visual editor yet (“QDK” appeared the following year).
Here’s the Quest 1.0 Readme file and ASL Reference if you’re interested in some historical detail. You would create games by using Notepad to edit the included template.asl file, which looked like this:
' Quest ASL Template
' All sections must exist in the game, though the text sections may be empty
' if desired.
define game <Enter name of game here...>
asl-version <100>
game version <1.0>
game author <You>
game copyright <© 1998...>
game info <Enter game info here...>
start <Enter name of place here...>
possitems <Enter items separated by commas here...>
startitems <Enter start items here...>
end define
define room <Enter name of place here...>
look <Enter description here...>
end define
define text <intro>
Enter intro text here...
end define
define text <win>
Enter win text here...
end define
define text <lose>
Enter lose text here...
end define
This file format lasted a long time. It was used right up until Quest 4.x, the last version of which was released in 2011 - albeit heavily extended and changed in various ways over the years.
The empty template looks like this when loaded in Quest 1.0:
The user interface is still very similar to what Quest offers now - in fact, after it was rearranged in Quest 2.1 it has effectively remained an identical layout. There is the game text of course, a command box, a space to show what items you’re carrying, and a list of things you can see in the current location (which would show “Look at” and “Take” buttons if something was selected). There are also the compass buttons for easier navigation.
Quest 1.0 supported rooms, characters, objects, things you could pick up (“items”), quantities of things (“collectables”), string variables and some basic script commands. It could play WAV files, show images and display pop-up menus. It supported text formatting, and let you set up your own custom commands using a syntax like “eat #object#” - the same format that is still used in Quest 5 today.
There was a small sample game distributed with Quest 1.0, “A day in the life of a salesman”. It is of a very similar standard to my QBasic efforts - which is to say stupid, crude and borderline offensive in places. So no, you can’t have a copy, but yes, it does still run in Quest 5.4!
What happened next? We’ll pick up the story in the next blog post, where I’ll talk about how Quest grew, changed and even shrunk over the years to become what it is today.
CONTINUED IN NEXT POST
26 November 2013
This is part 2 of a look back at 15 years of Quest - part 1 is here.
Immediately after releasing Quest 1.0, in November 1998, I got started working on Quest 2.0 - the first alpha version was released only a month later, in December 1998. This version incorporated the early feedback I’d received from v1.0 - making room descriptions more customisable, adding functions, numeric variables and “for” loops, improving the in-game debugging information, and fixing various bugs.
It seems surprising to me now that I didn’t ever do a bug-fix release of v1.0 - I guess that so few people were actively using it, and there were so many rough edges anyway, it must have made more sense just to plough on and pour everything into v2.0. And this was before I’d ever heard of source control anyway - in fact, I doubt I’d have even had any kind of backup copy of the Quest code at the time. (It was a time when I was constantly running out of hard disk space, when floppy disks were too small, before I had a CD writer, and before any significant amount of online storage space was easily available).
Over the following months I added more features - more text formatting options, allowing objects to moved and hidden, and libraries to allow Quest functions to be re-used between games.
It was all a nice break from working on my A-levels and filling in my UCAS form.
Quest 2.0 was released in August 1999, and for the first time included a beta version of a new visual Quest game editor called “QDK” - meaning finally you no longer had to code games using a text editor. (I would have called the editor “QED” but there was already a Quake editor of that name).
The script editor was very basic:
The main player interface for Quest 2.0 still looked pretty much exactly the same as v1.0 - which is to say, hideous. This was finally rectified in November 1999 with the release of Quest 2.1, which has a layout which is awfully similar even to the current version of Quest:
Quest 2.0 is the first version for which at least one actual game was made - and it’s still on textadventures.co.uk, and it still works today, whether you download it or use the web-based player - The Adventures of Koww the Magician.
There are a total of 28 games on textadventures.co.uk which were written for Quest 2.x - see if you can find them… (the column to the right of the game listing will tell you the version of Quest used to build the game).
The “libraries” feature got some early use, with Alan Bampton creating a “Standard” library to add some features, including containers - which Quest was still years away from supporting natively. This library was included with Quest itself as of v2.11. (10 years later, when redesigning Quest for v5.0, libraries became the way to add all functionality to Quest - without its Core library, Quest 5 does very little at all).
By early 2000 my thoughts were turning to Quest 3.0, which would be a huge update - I was getting lots of suggestions from users, and there were various aspects of Quest I wanted to tidy up - things which didn’t make sense to me at all any more, such as: why was “an object in a room” a separate concept to “an item you can carry”? It was time for the first of many overhauls of Quest. In the mean-time I carried on releasing bug-fixed versions of v2.1 up until Quest 2.19, which was released in January 2001.
Next time I’ll carry on with a look back at version 3.0 and beyond. If you want to peruse some archive material, the forums from 1998-2000 are still online.
27 November 2013
This is part 3 of a look back at 15 years of Quest. Here are links to the previous posts: part 1, part 2.
The first alpha build Quest 3.0 was released in March 2000, and fixed one of the weird design flaws of previous versions by unifying “items” and “objects”. Objects now had to have unique names, but they could have aliases, which would be displayed to the player instead of the code name. This version also introduced a disambiguation menu to allow the player to distinguishing between different objects which had same the alias. This is fundamentally the same approach to object handling that Quest still uses today.
That first alpha of Quest 3.0 also added timers. The second alpha in July 2000 added support for a truly experimental feature that never quite took off - online multi-player play. This allowed Quest to connect to a new bit of software I was working on, which started out with the name “QX3” and was later renamed “QuestNet Server”.
The idea was that the game ran entirely on the server, and players would connect to it using the Quest software. This would allow multiple players to connect to the same game world, where they would each have their own inventories and be able to interact with other players.
You can get some idea of how it worked by looking at some screenshots for the basic “Arena” demo. Multiple players would appear in the same room, and they could pick up objects, give them to each other, and even hit each other. For example, here’s what Bob might see if he joins Alex in the room:
And here’s what Alex sees while this is happening:
I thought this was rather nifty, myself, and although it got a reasonable amount of interest from Quest users, it ultimately failed to really get anywhere. I’ve come across a forum post from 2002 by MaDbRiT which sums it up:
Questnet is a good idea that is kind of struggling to get off the ground. There are no games because there are no players and no one wants to spend aged writing a game if there are no players. What came first, the Chicken or the Egg? The technical demands of hosting a QuestNet game are out of realistic reach of most of us too - even if I wrote a QuestNet game, I couldn't "serve" it - I just don't have the facilities.
In the days when most of us were still using dial-up, the idea of running a server on your home internet connection just didn’t make a whole lot of sense.
QuestNet Server would hang around for a while, never getting much use or ever seeing its full potential. I still think there’s something in the idea of multi-player interactive fiction, and maybe it’s something to revisit some day. Watch this space!
The second alpha of Quest 3.0 also got rid of the separate concept of “characters” - they were now just objects too. It added support for arrays, and arbitrary object properties allowing any kind of data to be attached to an object (although these were separate to the built-in properties or “tags”, which meant that you couldn’t easily read or update data like an object’s “look” description - this flaw was resolved when Quest was rewritten for v5.0, when all object data was finally stored as properties).
A third alpha build followed in September 2000, which added object types - allowing object properties to be inherited. This also added support for creating rooms on-the-fly via script.
In October 2000, I moved to London and started university, so progress with Quest slowed down quite a bit.
In March 2001, Quest 3.0 reached its first beta release. This added support for dynamically creating objects and exits, and added script properties (“actions”). The second beta followed in April, featuring various minor tweaks to get it closer to a releasable version. Quest 3.0 was finally released in September 2001, and QDK was updated at the same time to get a cleaner interface and to support all the new Quest features. It also gained a new script editor.
The new-look start screen allowed you to load a game file, or connect to a multi-player network game:
The main player interface was relatively unchanged from Quest 2.1, although you could now toggle the panes off:
QDK was still looking rather plain:
The Room and Object editors were now grouped into tabs:
The new Script Editor presented a plain English way of editing scripts. It’s not dissimilar to Quest 5’s script editor, although it did involve opening a pop-up window every time you wanted to edit any individual command, which some people found a bit tiring:
A few bug-fix releases followed very shortly afterwards, and then I started working on v3.1. This added support for MOD music files - something I was into creating myself, but a feature I think was never actually used by anybody. There were various other tweaks, including improvements to the parser. Libraries gained the ability to add panes to QDK (here again is an example of a feature that was added which is now a core part of how Quest works - as of v5.0, all panes in Quest’s editor are defined by libraries). Quest 3.1 was released in June 2002.
The next update was version 3.5, released in December 2003, featuring the ability to translate the player interface (although not on a per-game basis - it was a player setting), plus support for text-to-speech and opening ZIP files. Following slightly later in January 2004 was the first non-beta release of QuestNet Server - although, as it would turn out, it would never get another significant release after that, simply keeping pace with features as they were added to the single-player version Quest.
The pace of change was clearly slowing down, as I was keeping busy with my Physics degree. It got even worse after I graduated in 2004, and started working - I didn’t really touch Quest for almost two years. But when I finally came back to it, I dived into it in a big way. More on that next time!
Ignore this last section (NOTE FROM K.V.).
I had to add this text to edit this post without running into "Sorry, you can't post that here."
I’ve been building Quest and working on textadventures.co.uk full-time for a couple of years now, on and off. Despite my best efforts to turn this into my living, I can no longer continue to work on this basis. As of January, I’ll be moving on to work on something else, with interactive fiction becoming a side project once again.
We applied to Emerge, a new startup accelerator focusing on education, with our aim of building up ActiveLit. I’m told about 80 companies applied, and we were one of the 20 selected for interview.
Unfortunately we are not one of the 7 or 8 that have been selected to join the programme.
We would like to thank you for taking the time to apply to and interview for Emerge Education '14.Places are limited and the applications were excellent. It was difficult to select participants from such a strong group. Unfortunately on this occasion, we are not in a position to offer you a place in Emerge Education '14. We hope you will apply to our future programs.
We include below a brief summary of how we arrived at this decision and hope this is helpful to you:
- Your product was more developed and had more traction than that of any other applicant to Emerge Education and we were impressed by the user demand it has received;
- The selection committee's main concern was a lack of clarity around whether your team had the strategic intent to take ActiveLit from an (already) successful product to a high-growth business;
- In addition, applicants that did better in the selection process tended to have more business experience as part of the co-founding team.
I find it difficult to understand the logic here, and in fact this email makes less sense every time I re-read it. The highest traction product of all applicants, but a question mark over our “strategic intent”?
Whatever. You can’t expect too much from rejection emails. Any “reasons” given are always post-hoc justifications of the decision made. I expect the most typical would be “your product is not sufficiently developed”, so at least it’s novel to be turned down because our product is too developed.
It would only require one reason to say yes - “we think there’s a good chance of making money if we invest in you”. At least in this way it’s a more straightforward and honest process than awarding grants - it’s refreshingly simple compared to working out why, say, a government body won’t award funding. Any rejection from an accelerator is fundamentally because they couldn’t find this reason to say “yes”, rather than any reasons that may be given for saying “no”.
This is the feedback we’ve been waiting for, then - the simple yes/no answer to the question “Can we convince people that know about money and business and stuff that what we’ve been working on is viable?”
And the results are in, and the answer, at least from Emerge (and also Wayra), is “no”. And that’s fine.
They say that it takes grit to succeed, but what if you never give up on an idea that is fundamentally never going to work? Maybe it simply makes more sense for Quest, textadventures.co.uk and ActiveLit to be run as side projects. I’ve sunk a lot of time into these now - 2 years of full-time effort. I’d be much richer now if I hadn’t done this.
Of course, I’d be unhappy. I’m really pleased with what I’ve achieved. I used to sit at work, seething in frustration, because there were things I wanted to do with interactive fiction that I didn’t get time for. That’s changed now - I’ve built a lot of software, explored a lot of angles and spoken to a lot of people, trying to work out how an interactive fiction business might succeed.
And what I’ve discovered is, I can’t make it work. Not right now anyway. Maybe it just needs to live and grow organically for a while. Maybe something external will change, as more and more people discover interactive fiction, or as more teachers use Quest and text adventures in the classroom. I’ve got nothing left to “push” from my side, and I’ve run out of money anyway.
And even if nothing external changes, and it never grows beyond what it currently is, it will still have been worthwhile. I don’t regret anything. I’ve built what I wanted to build. I’ve scratched the itch. I’ve created software that is being used by all kinds of people for all kinds of things. Children are learning programming, being engaged with reading and writing. More and more people are playing and creating games on the site. I’ve met some great, interesting people. It’s been a lot of fun. It’s been totally worth it.
But I can’t do this for a living, so it will have to become my hobby again. There are plenty of other things I can do - there are loads of opportunities for software developers at the moment, and there are some great companies out there doing interesting things which I can contribute to. It’s an exciting time, and I’ve now got some great experience that will hopefully prove useful in whatever I move onto next.
28 May 2014
This talk was given at the London Educational Games Meetup on 28th May 2014.
Link to view on YouTube:
29 September 2015
So that’s what I did – I decided to build some awesome stuff. In 2010 I quit my job and threw myself head-first into building the things that I wanted to build.
I’d been spending much of my spare time working on my open source project Quest, a system that lets non-programmers write text adventure games, and I knew that teachers were starting to use it in their classrooms, so I thought there might be some opportunity there to make some money out of it.
To be honest, quitting my job to focus on building a text adventure engine did seem kind of silly – but the iPad had just been released, and I was wondering if interactive ebooks might become a thing. If so then maybe I would find myself in the right place at the right time. All the best ideas are kind of hard to distinguish from ridiculous ones, and there was only one way to find out on which side of that dividing line this fell.
And that was really the extent of my “business plan” – I didn’t think it through in more detail than that. It was more a case of “what’s the worst that could happen?” And the worst case scenario didn’t seem too bad – I’d quit my job working as a VB6 developer, but if I wanted another crappy developer job then it wouldn’t be that difficult to find one. What I wanted was a good job, and the best way to find one was to increase my skills.
Being quite a frugal person I happened to have enough money saved up that, even if I didn’t have any income for a year or so, it wouldn’t be a big problem.
So I spent most of the next four years doing various things with Quest and interactive fiction:
I made small amounts of money here and there, with a larger amount of money from a few months of contract .NET developer work to top up my finances. Ultimately though, my money ran out.
I had failed to build a successful business, but I had spent years doing work that I enjoyed, and I now had a vastly increased set of skills and a much more interesting CV. I had built some awesome stuff – now I just needed to follow the cycle around, to tell people about it and try to get an awesome job. That’s what I’ll be talking about in part 2 of this post.
Just in case you think the only way to build awesome stuff is to quit your job and spend four years trying to build an entire business – you don’t have to be as batshit insane as me. You can build stuff in your spare time – I still do, it just takes a little bit longer. Build something you’re interested in building, something you can be proud of, and ship it. It’s the best way to learn, and it’s the best way to upgrade your CV.
7 December 2016
I have been developing Quest and textadventures.co.uk for a long time. It started off as a summer coding project when I was a teenager and wanted to send stupid text adventure games to a friend. Over the last couple of decades it has turned into something far bigger than I could have imagined.
It has alternated between hobby and full-time job, and tinkering with it all these years has taught me huge amounts about writing software, helping turn me into the developer that I am today.
I’m proud of what I’ve built - various open source projects that have enabled hundreds of thousands of people to build games for the first time, and a website that has become the top hit on Google for “text adventures” and attracts 3,500 users per day, a number which continues to increase.
The software and community around it are in great shape, and I think they have a great future. But the time has come for somebody else to take charge - I want to focus my energy on new projects, and hand over what I’ve built to somebody else who has the passion to drive things forward.
I am looking for people interested in taking this on. There are quite a lot of different bits, and these wouldn’t all necessarily need to go to the same person or company - things could be split up if that looks like the best option. I am open to all suggestions and proposals - my main concern above all else is finding the best home (or homes) for the long-term future for these projects. I am not looking for money and I’m happy to do everything I can to ensure a smooth handover.
If you’re interested, please email me at link removed.
I really hope that people from the interactive fiction community will want to see Quest and textadventures.co.uk continue, so if you can possibly help then please get in touch. Do you want to keep textadventures.co.uk alive for the community that loves it? Could you take it forward to bigger and better things?
If no suitable new owners come forward by 28th February 2017, then sadly I will have to start the process of shutting down the website and forums. Initially they will become read-only, and I will look to export the data elsewhere (the IF Archive or the Internet Archive) before closing the sites completely.
Quest and Squiffy will remain accessible on GitHub but there will be no further updates. The software will still be able to be downloaded for offline use, but the online web-based versions would no longer be available. The GitHub repositories themselves would probably be transferred to the IFTF.
textadventures.co.uk according to Google Analytics:
Users:
Games:
Social Media:
Income and Expenses:
AdSense earns about £50/month for the limited advertising which is currently on the site.
The main costs are for Azure at ~£70/month, and the VPS (hosted by OVH) which runs the Quest online player and editor at £13.59/month ex VAT.
(On Azure, I’ve been getting a £65/month free credit, so the actual amount billed averages only about £5. This means the total cost for running the site has been about £20/month, which has been entirely offset from the Adsense income.)
12 December 2016
This is a follow up to Looking for a new owner for textadventures.co.uk and Quest.
Thanks to all of you who have got in touch so far. A lot of people have asked about what would be involved in taking over and running textadventures.co.uk and/or Quest, so this post is to go into a bit more detail about how things are set up and how the work might be split up across different people.
For a smooth transition, I need to find people to fill these four roles:
Of course any of these roles can be combined – after all, they’ve all been done by me up until now.
textadventures.co.uk and ActiveLit run on the Azure App Service (formerly known as Azure Websites). Data is stored in Azure SQL and in Azure blob and table storage.
The web-accessible blobs (for game downloads, cover art etc.) are behind a Cloudflare CDN.
The code uses C# and ASP.NET MVC. The front-end uses Bootstrap, JQuery and a little bit of React.
ActiveLit runs alongside textadventures.co.uk on the same Azure infrastructure and talks to the same database.
There are two parts to Quest – the Player and the Editor. There are also two ways of using Quest – via the web, and via a downloadable Windows desktop application.
The current version is Quest 5, and I also made a start on Quest 6 which is architected quite differently. The new version rewrites the Player back-end to use JavaScript, which means the web version requires no server component (making it much faster, infinitely scalable, distributable on any website, and an end to time-outs while playing), and the desktop version will be cross-platform for the first time (packaged using Electron for Windows, Mac and Linux).
To take on Quest 6, I’m looking for a developer who has experience using the modern JavaScript ecosystem (npm, TypeScript, gulp, webpack and all of that kind of thing). I will work with this person to help get Quest 6 shipped. (It doesn’t make sense for me to continue working on this project without somebody to hand it over to, because it will of course need to be maintained after it is shipped). Quest 6 lives in the v6 branch on GitHub.
After Quest 6 is shipped, rewriting the Editor to use JavaScript would also be really useful. That would be a project for the new Quest 6 maintainer, or maybe even someone else. If Quest could be taken to the point where both the Player and the Editor were shipping as 100% JavaScript applications, that would be a massive simplification of the Quest architecture.
Quest’s long-term future lies with Quest 6, but it would be good if we can find somebody to maintain Quest 5 for the time being, not least because even if/when Quest 6 ships, it will still be using the same .NET-based Editor that Quest 5 uses.
I’ve updated the Developers documentation page on the Quest docs site to describe how the various projects that make up Quest 5 together. It is not an easy thing to pick up – there’s a lot of code there, and a mixture of languages and technologies reflecting my changing tastes and experience over time. It’s stable though, and it shouldn’t require big changes because if the Player and Editor both get rewritten using JavaScript then all of it will become obsolete.
If you’re interested in taking on one or more of these roles, please email me at link removed.
To reiterate, I am not looking for money. I want to hand these over to somebody (or a group of people) with a passion for IF and a vision for where these products could go in the future. That vision doesn’t necessarily have to agree with my vision (that’s what stepping back is about) – this is a massive opportunity for somebody to take over running a popular website and IF development system. textadventures.co.uk is the place people come when they search for text adventures on the web, so it’s a big gateway to the world of interactive fiction. Taking on the website doesn’t have to be about taking on Quest.
I’ve only got Alexa rankings to prove it (so take them with a pinch of salt) but the site appears to be bigger than other IF sites like IFDB, intfiction.org and Choice of Games. It’s how a lot of people start out making text adventures – in fact, it’s introduced a lot of people to programming in the first place. It’s used by schools to get children into coding and creative writing.
Thanks again for responses so far. If you can’t help out yourself, please help spread the word to somebody who might be able to take this on and ensure it has a future.
11 January 2017
I announced last month that I was handing over textadventures.co.uk and Quest. Many thanks to everybody who got in touch to volunteer to help. I was really pleased that so many people want to see these projects continue into the future. I am now happy to announce that we have a new team in place!
Luis Felipe Morales will be taking over the textadventures.co.uk and ActiveLit websites, and also Squiffy. A programmer since the 1980s, Luis has been involved with the Spanish interactive fiction community since he was young. He has maintained and created several internet portals and now works as a freelancer.
Jay Nabonne and Andy a.k.a The Pixie will be taking over development of Quest. Both have been very active members of the forums for a long time. Jay is a lifelong programmer and game player who is interested in not only creating games but helping others to do the same. A California native, he now lives with his wife in the UK. Andy has been playing and creating text adventure games since the Eighties, has been using Quest for over five years and has written various guides and libraries for the system.
Greg Fenton and Nathan Clive Gerard will each be running servers for Quest’s WebPlayer and WebEditor. Greg is a developer who wrote his first text adventure in dBase III on an IBM PC back in the very late 1980s shortly after leaving high school. Nathan is a regular player of text adventures from the UK (currently living in the USA), who spends his days setting up and looking after web servers in the cloud.
I’ll be working with each of them over the coming months to ensure a smooth transition. Please welcome them aboard!
by The Pixie, from the documentation
When I took over Quest, I was intrigued to see its history. Alex did some retrospectives in some blog posts, allowing a timeline to be constructed.
The roots of Quest, up to Quest 1.0, from Alex's first game when he was 11 to the first Quest.
https://blog.textadventures.co.uk/2013/11/07/quest-is-15/
From Quest 1.0 to 3.0, seeing the introduction of a GUI for writing games.
https://blog.textadventures.co.uk/2013/11/07/quest-is-15/
From Quest 3.0 to 3.5, via multi-player.
https://blog.textadventures.co.uk/2013/11/27/15-years-of-quest-part-3-2000-2004-experimenting-with-multi-player/
Part 3 indicated that he intended to write more, but I have not been able to find it. His next blog post indicates he got a proper job, so perhaps he never got around to it.
Quest versions 1 to 4 were a development of the same system. Quest 1 consisted of a player and a file format - a format quite unlike the XML format of Quest 5, but one that would be developed across the first four version.
With Quest 2, we got an editor and an update to the player. The player even at this time looked like the modern interface.
07/Nov/98 Quest 1.0 released
??/Aug/99 Quest 2.0 released, with beta version of the QDK editor
??/Nov/99 Quest 2.1 released, with play screen laid out as we know it today
??/Jan/01 Quest 2.19 released
??/Sep/01 Quest 3.0 released (with a short-lived multiplayer option)
??/Jun/02 Quest 3.1 released
29/Jun/03 First forum post (or first I could find anyway)
??/Dec/03 Quest 3.5 released
??/Jan/04 QuestNet Server first and only version released
17/Jan/07 Quest 4.0 released
02/Feb/07 Quest web player goes beta. Previously players could only download games to play, now they could play them in the browser.
Quest 5 was a big change. I get the impression the code was entirely written, now using C#. The file format was entirely different, using XML. The new interface was HTML. Another big change was that Quest went open source, and was now free to both edit and play.
https://blog.textadventures.co.uk/2011/08/30/quest-5-0-is-out-now/
I joined the Quest community in the Summer of 2011, when the beta release of Quest 5 was out.
17/Jul/11 Quest 5 tutorial released (Bob and the defibrillator featured in the tutorial for earlier versions by the way).
01/Aug/11 My first forum post!
30/Aug/11 Quest 5.0 released
11/Jan/12 Quest 5.1 released
12/May/12 Quest 5.2 released (a web version of the editor)
14/Jan/13 Quest 5.3 released (updated interface using Chrome, web fonts, map, changeable POV, light/dark)
28/Mar/13 Quest 5.4 released (text processor, code view for scripts, JS object; some XML attribute names changed - which can cause problems if opening games from earlier versions)
05/May/13 Quest 5.4.1 released (exits with scripts need an attribute set to make the script run)
01/Mar/14 Quest 5.5 released (customisable UI, the Features tab and a contribution from me)
03/Aug/14 Quest 5.5.1 released
??/Feb/15 Quest 5.6 released (no blog post for some reason, so hard to find what got added, but a forum post indicated it was mostly a bug fix)
19/Sep/16 Quest 5.6.3 released (Alex's last release)
11/Jan/17 Alex officially leaves Quest and textadventures.co.uk
19/Jul/17 Quest 5.7.1 released (there was no official 5.7.0!)
02/Feb/18 Quest 5.7.2 released
https://blog.textadventures.co.uk/2018/09/03/quest-5-8-is-out/
https://textadventures.co.uk/forum/questkit/topic/t9k4lvtfuuksmwbjpzvm9g/the-future-of-quest
Follow us on Facebook
Follow @TextAdv on Twitter