Welcome to the Doom Cross Port Compatibility Issue tracker. This is a tracker dedicated to issues pertaining to modding and mapping feature set compatibility across Doom source ports, primarily derived from the Boom source port's lineage of features.
As part of the collaborative efforts towards standardizing behavior across various Doom ports, this repository aims to gather information on how features behave differently for players and mappers/modders on any port that aims to adhere to common cross-port specification standards.
For over 20 years, the Doom community has relied on poor methods of documentation for the features adopted over various ports, such as user feature requests, word of mouth and plain copy-pasting of source code. During early Doom history, this may have been enough at some point, but with the advent of formal feature set specifications such as MBF21 and UMAPINFO marking a watershed moment in the history of port development, where now, ports had a proper description for what behavior is expected, where port developers no longer needed to rely solely on indirect source for cross-compatibility bugs, and instead can work together to determine exactly what is and isn't considered expected.
When filing an issue consider writing the following points:
- Describe the feature in question and its expected behavior.
- List which ports you've tested on, on their respective latest stable version releases.
- Explain how the expected behavior differs across ports, preferably providing an example testing WAD, with the conditions needed to reproduce the bug.
The clearer and more straight-forward the descriptions are the faster that port developers can understand and identify the underlying problem and the faster that proper consistent behavior can be defined.
Do not be afraid to report any compatibility issue, no matter how seemingly small -- a benign report is better than an unreported bug.