You won’t be able to meaningfully decompile Inform 7 code, but you can extract the texts. If you used a lot of text substitutions even they will be hard to make use of though.
We get this question a lot, and it’s just given me an idea: Inform should include a copy of the source code in the blorb for debug builds. A slightly larger file for the possibility to recover many people’s projects.
Glulx-strings is a quick tool for dumping strings from Glulx and Z-code files (including zblorb). This is probably easier than using txd, since the strings are the main things you’d be able to retrieve anyway.
If you want to use txd, you may need to extract the z-code from the zblorb archive (it’s been awhile since I used txd, not sure). You can find some tools for working with blorb archives here.
Yeah, this idea has come up before. I’m not sure “debug builds” is the right criterion, though. If you find a playable blorb file and wish you had the source, it’s probably a release build, not a debug build.
I’d like an “Release along with embedded source” option. I can’t argue that this should be the default, but it should be available for people to use.
(Then there’s the question of how much source… include all the extensions? When I’m putting an Inform game into source control, I always include all the extensions.)