TALP/TALJ reviews will be going up, one per day, to IFDB as I work through them and edit them. They’ll be in alphabetical order. I put Mr Seguin’s Goat up because I had the most thoughts on it, especially with the hint topic, and I wanted to give a trial run to speaking a review into a phone, mixing it with what was on here, and editing for a final product.
Barry Basic and the Witch’s Cave 6/19 12:01 AM GMT
An Eggcellent Preparation 6/20 12:01 AM GMT
First Encounter 6/21 12:01 AM GMT
Interactive Adventurer’s Tutorial Adventure 6/22 12:01 AM GMT
Midsummer’s Eve 6/23 12:01 AM GMT
Mystery of Winchester High 6/24 12:01 AM GMT
Peanut Butter and Jelly Sandwich: The Text Adventure 6/25 12:01 AM GMT
Priceless Vase Adventure 6/26 12:01 AM GMT
Again, I’d like to encourage people to vote for what games they can, especially because TALP/TALJ encourages a lot of in-game tutorials and hints, thus making it less probable you’ll get stuck.
We’re at 75 now. 3 more people voting for every entry in the next 2 weeks would get us to 102, which would 1) be the number of votes from the first jam and 2) be the highest average votes per entry for all the jams.
It’s good to see votes spread out relatively evenly, too! And it’d be neat if we could get 10 votes for all the games. 3 votes on every game would get us there, too.
For the ones currently with minimum votes (7,) Priceless Vase Adventure is not a big game, IATA is very user-friendly and not out to pull one over on the player, and Mr. Seguin’s Goat has a pretty extensive hints topic as noted above.
I think that’s true. You might be able to get it working on an ADL interpreter on another platform, but they’re as rare as hen’s teeth. I think there’s one for the Amiga, but I couldn’t swear to that.
I’m wondering how tricky the Windows would be to run on WINE, on Linux or Mac.
It looks like a Linux binary is here and I always forget what Linux binaries can run on Mac. It’s also 20 years outdated!
The code is here, with a makefile too, for anyone with dexterity with these kinds of things.
I don’t know how far we can/should stretch to get this working, or how useful it would be in the future, but I thought I’d put this out there. ADL doesn’t seem overly complex, so I doubt there are many system dependencies for building. But it isn’t something I’m confident I can do right off the bat, even though I have a Linux VM.
I should have known this, I remember playing around with ADL back in the 90s on a Solaris machine. It was developed on UNIX IIRC so it should be fine.
[ Moments later. ]
ADLrun compiled easily on macOS (I had to mkdir Objs and then run make), but it won’t open the game file:
adl-code (master ✗)]$ ./adlrun/adlrun vase.out
ADL interpreter - Version 4.0 - December 7, 1994
Copyright 1985-1994 by Ross Cunniff
All rights reserved.
vase.out: Not an ADL datafile.
Ugh. Maybe it is a problem with having a Mac carriage return instead of Windows carriage returns? Or a question of byte order?
It doesn’t seem like something you should have to debug!
Note: I’m trying to corrupt a copy of the data file on Windows, and it’s still running okay. I mangled some headers and random body text.
Perhaps adlrun has a debugging switch which could tell us what the offending byte is?
My suspicion is, people create ADL files as a hobby, and those files don’t gain wide exposure. If the author build on Windows and ran their games on Windows, and the developer built on Linux and ran on Linux, and cross-platform stuff would be covered.
The solution to this would be to ask the author for their source code and see what compiled. Or, better yet, have very simple ADL code that we compile on both Windows and Linux. Then we create .out files and see what’s different.
There’s a strong possibility the bug or bugs will get seen easily, but that is no guarantee. Still I hope this is a decent roadmap, and it’s good to know of the pitfalls that are there.
Perhaps if nothing else we could have a unix to windows conversion utility or vice versa.
I tried one of the samples (tiny.adx) and it works properly.
Both files start with the same magic number (0xad10ad1) but vase.out has it in the wrong spot according to where the sourceforge ADLrun expects it. In tiny.adx it’s at about byte 0254 and it’s at byte 0330 in vase.out.
So either the version the author used is different than the sourceforge version or the Windows compiler isn’t respecting the int16/int32 types properly and making the header the wrong size or it’s an Intel vs ARM problem.
I’ll see if I can find a Raspberry pi around the place and compile it under Linux, but I doubt it’d be any different.
Can you try this file and see if it works on Windows (I’d be very surprised): iCloud
Yes, I got a “corrupt file” notification. Perhaps there is a way to convert bytes from one format to the other? That seems like more work than is necessary.
But ugh … potentially having different versions create different file formats is more than a bit of a mess. Back when we had binary formats instead of a standard markup language, though, there wasn’t much choice.
It’s a lot of work to do just to get one game running. I suppose I could download the ADL building toolkit if I wanted, to see what tiny.adx would look like on Windows. If the byte-shifting wasn’t too bad, who knows?
Fixing the header might be straightforward, but it’s probably a symptom of a wider malaise. If you have time, try building tiny.adx yourself and see how much bigger it is. If it’s only ~40 bytes it’s just the header, but any more than that and it’s a bigger problem.
Hello, Aschultz! I just wanted to inform that Adventure Definition Language (ADL) offers Transcription feature. It is built-in! Just tyle SCRIPT command while playing the game. You will then be aksed to enter the file-name. To close transcription, just type Script command again. The script-file will contain both input and output of the game. So - no need to use Tee utilities.
Note: The transcription feature is available with ($spec 8 filename) command, but it is provided within Standard include file as a "Script" command.
Thanks! (And welcome to the board!) I’ll remember this for future games. It’s good to see ADL’s features I wasn’t immediately aware of.
Re transcripting, it seems fair game to put something in any ABOUT commands, or in the introduction, or in a readme? I think a lot of people would be willing to help you out with this if you want feedback.
Hello Stephen,
I compiled ADL compiler and interpreter for Unix based systems and will provide working compilations of my future text-adventure games. Thank you for testing and information.