This wasn't strictly speaking a bug in that Doomsday expected that there would only be one instance of -def and/or -defs on the command line. Snowberry however assumed that any number of these may be specified. As such, I've opted to change how these command line options are handled in Doomsday:
The command line options -def and -defs are now treated identically, each can be used to specify one or more DED on the command line (e.g., "-def "}defs/jdoom/file1.ded" "}defs/jdoom/file2.ded") and Doomsday now accepts multiple instances of either option (e.g., "-def "}defs/jdoom/file1.ded" -def "}defs/jdoom/file2.ded"").
Added by danij almost 16 years ago
Added by
Fixed: "Failing to read more than one loose ded" see here (http://sourceforge.net/tracker2/?func=detail&aid=2646623&group_id=74815&atid=542099).
This wasn't strictly speaking a bug in that Doomsday expected that there would only be one instance of -def and/or -defs on the command line. Snowberry however assumed that any number of these may be specified. As such, I've opted to change how these command line options are handled in Doomsday:
The command line options -def and -defs are now treated identically, each can be used to specify one or more DED on the command line (e.g., "-def "}defs/jdoom/file1.ded" "}defs/jdoom/file2.ded") and Doomsday now accepts multiple instances of either option (e.g., "-def "}defs/jdoom/file1.ded" -def "}defs/jdoom/file2.ded"").