I decided a while back to quit playing Quest games on account of the fact that a) they were awful and b) they were awful. Even the ones regarded as masterpieces in the Quest community tended to be, at best, decidedly average. While I'm sure it’s possible for a decent game to be written with Quest, none of the ones written to date showed any indication of this and I’d reached the stage where I was playing new Quest games expecting them to be bad and actively sitting there waiting for some terrible bug to throw itself upon me. Hardly the state of mind you should be in when playing a new game. But…

But I gave this one a go. There were less games in this year’s comp than the previous one and as I immediately decided against playing several of them due to one reason or another, I figured I had enough time to at least give this one a shot and see if someone had finally achieved the seemingly impossible and written a Quest game that was actually worth playing.

And that was how I found myself pleasantly surprised.

While a long way from perfect, indeed it has more rough edges than you can shake a stick at, Gathered In Darkness is a solidly entertaining piece of IF. And I don’t just mean it’s a decent game by Quest standards (which, to be honest, isn't saying much), but a decent game full stop. Turn off the side panels, enlarge the text entry line and smarten up the interface a little, and you could easily be forgiven for thinking you were playing a TADS or Inform game.

Given its numerous shortcomings, I'm still not entirely convinced that it’s possible to write a truly great game in Quest, but this one comes the closest to being truly great that I've played so far. At the very least it shows that, while Quest may never produce a masterpiece, it is capable of producing above average games. I've gone over Quest’s problems (at least as I see them) in the past so I won’t reiterate them in any great detail here, but suffice to say the Quest player leaves quite a lot to be desired. The text entry line is still miniscule and, when played on my Vista PC, the new rounded START button has a tendency to obscure some of the already-too-small text I'm typing. Unfortunately, Gargoyle doesn’t seem to work with Quest, at least as far as I could tell, so the Quest player it has to be.

The player carries with him a journal in which important bits of information are contained. In theory anyway. Only the first time I was told it had been updated, there was nothing in it when I tried to read it. Seems I’d turned off the godawful side panels that Quest favours and the relevant information was contained there. A pity no one writing games with Quest ever seems to realise that some of the people playing them might do this sort of thing. Might it not be a good idea to warn people when turning them off or to at least display the information in the game window when the side panels aren't active?

There were a few annoyances with room descriptions. The first time I saw my room, there was a nice long description of it, afterwards there were just a few lines. LOOK did nothing more than reprint these few lines, not the full description. Several key items I had seen before were now hidden and I ended up having to scroll back up the screen in order to refresh my memory as to what they were. On a few occasions, I missed required items because of this and only discovered them after much scrolling up to reread the room descriptions.

Bug-wise, this seemed a little better than the average Quest game in that for the most part I didn’t encounter any real problems. However, in one location I tried to open a door and was told that the only doors I needed to worry about were locked ones. So I tried unlocking it and was told I couldn’t see a door here. Hmmm…

Guess the verb rears its head a time or two and is further complicated by an unhelpful parser:

> GET BATTERIES
I CAN'T SEE THAT HERE.

> REMOVE BATTERIES
THERE ARE NO BATTERIES IN THE FLASHLIGHT AT THIS TIME.

Why did it assume I meant the flashlight? Also there are definitely batteries present.

> REMOVE BATTERIES FROM RADIO
I CAN'T SEE THAT HERE.

> GET BATTERIES FROM RADIO
YOU OPEN UP THE BATTERY COMPARTMENT IN THE BACK AND FIND TWO D CELL BATTERIES. THINKING THAT THEY MIGHT COME IN HANDY, YOU PUT THEM IN YOUR POCKET.

Why does GET BATTERIES FROM RADIO work yet REMOVE BATTERIES FROM RADIO doesn’t? And why does Quest not realise the radio is there when REMOVE is used, yet has no problems with the radio when GET is used? I generally don’t get too heated up over parser debates, but when one produces misleading error messages like those quoted above, it’s hard to stay cool about them.

For the most part, I liked the style of writing used here, over the top though it was. However, on a few occasions, it was *so* over the top in trying to convey a sense of horror, that it actually came across as quite comical:

A SCREAM RISES FROM DEEP WITHIN YOU BUT IT IS MURDERED BY YOUR FEAR AND DIES LONG BEFORE IT CAN ESCAPE YOUR LIPS

A scream being murdered by your fear…? That sort of thing reminds me of the slasher films you tend to get these days that throw buckets of blood and dismembered corpses all over the place because it’s so much easier than doing something genuinely scary.

Gathered In Darkness is a fairly sizeable game to be completed within the IFComp’s 2 hour deadline. And this is the cut down version as well, trimmed from a weighty 9 chapters to a more manageable 3. Even so, getting through it in 2 hours will be a struggle due to the sheer amount of text to wade through. If the other chapters are anything like as lengthy as this one, there's probably a good 6 or more hours of gameplay in the full version. The puzzles are fairly easy and straightforward, though as indicated above are often complicated by guess the verb and parser problems, not to mention the constant scrolling back up to read things that are only listed once in the room description.

Starting the game seemed to take an unusual amount of time for an IF game. Whereas normally they start almost instantly, or a few seconds at the most, here I was waiting almost a minute for it starting up. Someone else mentioned in a review that loading and saving caused lengthy delays but I never experienced these myself; however he managed to get the game to start up without any noticeable delay. Whether the slowness is a computer-related problem or a problem with Quest itself I couldn’t say, but if the final version of this game is three times as large as this, I don’t much fancy the delays it is likely to bring with it.

One final point which I liked is the game’s clever way of getting around one of Quest’s worst flaws: the lack of an UNDO command in the event of player death. Here, a scripted event triggers and takes the player back one move, thus removing the need to restart the game every time you die. Nice idea. Other Quest writers should take note of it.

6 out of 10

Wow...thanks David W.

I'm still looking into what is happening with the "look" command for repeating the long descriptions. In the full version of the game (all nine chapters) I am not running into this problem. For the If Comp I created a new file and copied only the information from chapters one through three into it and I wonder if somehow something became amiss. I had a three hour margin for error on entering it and I had already told myself (after missing last year) that I was going to enter it regardless.

So I did... and maybe I should have waited another year, but I am glad I took part in this years comp. I have decided to hold off a couple of months before releasing the full game and do some spell-checking and fix some of the parser issues that David and others have mentioned.

As for the references to B-movie slasher films... you are absolutely right. When you see eyeballs floating like clipper ships in the sack it is not a time for the writing to scare you. It's time to grin. I wanted a horror game, but I also wanted it to be fun and not heavy with deep serious themes.

I'm going to finish the cleaning up (I'm still not sure of the best way to do this... I've been copying text into a word processor and running spell and grammar check and then repasting into the game) and then I will release it complete. I have been very happy that most people have enjoyed the story and only complained about my spelling and grammar. Those things can be fixed... but a boring story can never be fixed, only changed.

I really enjoyed working in IF and in Quest and I will continue to do so in the future. (Though I plan to test out some other programs as well). Maybe in the future I will really be able to make something xtra-badass. This was my first game after all.

Thanks to Alex and all the Quest folks for your support,

Dr. Froth

(Can you believe that I misspelled the first word in my game: Prolog.
Oh yeah... cheese grader has caused quite a riot as well.

But...15th place. Right in the middle. Not bad for Quest. In fact, I have the highest scoring Quest game ever.... but as David says, that is not saying much at all.)

15th is still quite 'respectable' Froth!

I'd love to see how you've done the undo command.

I did start thinking about how this could be done, and couldn't think of any real way to get through it (short of backing up EVERYTHING in the game every 5 moves or so).

I'd think that would be the only able way to do it - have Quest back everything up after every move and revert back when the user inputs 'undo'.

15th is still quite 'respectable' Froth!

I'd love to see how you've done the undo command.

I did start thinking about how this could be done, and couldn't think of any real way to get through it (short of backing up EVERYTHING in the game every 5 moves or so).

I'd think that would be the only able way to do it - have Quest back everything up after every move and revert back when the user inputs 'undo'.

Good luck Froth

I spent a lot of time trying to figure out a way to create an undo command. My reasons for doing this were because I had created a custom suicide for almost every room in the game. Some of these are so great that I did not want the player having to save and reload just to read about what happens if they belt sand their face off. (Interestingly, I don't think anybody realized about the suicide bit).

All I did was create a procedure called UNDO. Whenever, the player dies, instead of scripting the "end game" command I would make Quest run the UNDO procedure instead.

This procedure was simply a menu with two choices. If they did not want to go back in time one move than I ran the "end game" script. If they did, then I just cleared the screen and forced a "look at room" command.

There were a couple of instances where I had to make a special procedure to move the player to another room (in the case of instant death rooms). But for 90% of deaths this worked great.

Of course I figured this out toward the end of development, and as I was trying to find everywhere I had killed the player to make the switch to the UNDO procedure I, of course, missed a couple of spots.

I don't know if anyone cares or not, but I did this whole game in QDK. I can't do a lick of ASL coding.

Oh yeah... I just figured out how to make "VERBOSE" vs "SHORT" commands that can be used by the player at any time during the game to force long or short descriptions. I am adding this to the post comp release and fix-up. If anyone wants to know how to do that, just let me know.

I hate to necromance this thread but can someone tell me why this was never put into textadventues online??

Is it too big?

Do you guys hate it that much...lol.???

Anyway...I was just wondering.

Was it ever even submitted to the old games archive or textadventures.co.uk...?

Hmmm...I could have sworn that I did...but, to be fair I might be mistaken.

Oh...well. Years later I have almost completed the whole nine chapter thing (all composed and coded, now just bug checking and spell checking). Probably only a few months left.

We can just put that one on textadventures.

Thanks for looking into it for me Alex.

Excellent, look forward to seeing it!