I’m overhauling my blorbtools package (forked from the old perlblorb and scanblorb scripts by Graham) to support executables other than Z-code and Glulx. Looking at the Blorb specs at https://www.eblong.com/zarf/blorb/blorb.html, I’m very puzzled at how to handle AGT executables. I understand that an AGT game’s data is spread across several files with wildly varying extensions. I also understand that there’s a package format called AGX used to pack all these files up into a single file for play on the AGT interpreter AGiliTy.
Back to the Blorb format: it allows zero or one executable chunks in a Blorb file. How does this work with AGT? I don’t see much of a point to adding an AGX file to a Blorb given that AGX appears to provide exactly the same functionality of a Blorb except just for AGiliTy (and I’m aware of no other terps but this and the originals).
My concluding question: Does AGT support belong in the Blorb spec?