myk
volveré y seré millones

Posts: 14422
Registered: 04-02 |
Gez said:
How very convenient for you to exclude from the debate the facts that do not go toward your argument.
It's funny because the facts you have mentioned are incorporated in my discourse and have appeared repeatedly, just that I am giving them a different value. Seriously, how am I excluding something that I'm considering a known fact and using on parts of my arguments?
Things that could be done: a Chocolate Boom for testing mods, and an "acid test" wad with a few maps and demos for testing ports. Both would have to be continually maintained to be sure that they illustrate and embody Boom-compatibility as exhaustively as possible.
Pardon the expression, but you're excusing yourself here from the perspective of a source port elitist. Things done hardly depend only on what's done with the source and even include this so-called "raging". Many things that end up in the source are demands by players and mod makers. Hence it's smart for mod makers to use clear and concise terms to say what their WADs work with and not actively encourage vague and inaccurate ways to convey such information, which can occasionally be called off with colorful and fitting epithets.
A "Chocolate Boom" wouldn't be a problem but it's not necessary, with the existence of PrBoom v2.02 for Windows (a plain port of Boom for the most widely used OS) and (the highly portable and maintained) DOSBox to run Boom itself. Keep in mind that, other than critical issues that may cause terminations, PrBoom+ pretty much deals with everything else like Boom if set to the corresponding compatibility level, so you don't normally need to use the older engines for most of the testing. This faithful capability is what prompted the "nah" from Andrey and myself when Quasar proposed that level 33 mnemonics be added as part of BEX in advanced ports, at least for the PrBoom line.
Besides, testing is only part of the deal. If you're not going for Boom compatibility, you call it something else, whatever it really is you're going for: "Boom features in ZDoom and Eternity" or whatever.
These two elements combined make it so that "compatible with Boom" and "compatible with Boom-compatible ports" do not overlap perfectly, neither set being fully included in the other.
And you know what? In one case, Boom is a specific engine with a narrow functionality only a bit more variable than vanilla when it comes to how it behaves. In the other, you're referring to various ports* with a vast range of settings and variations, and you are not even specifying which. You need to replace "Boom compatible ports" with which (sort of) Boom compatible ports, and may need to indicate roughly what features in said ports are used, to give an idea of what is required, perhaps with a general "using Boom features and [insert some other extra stuff if required]."
PS: You're like a guy trying to argue the pointlessness of traffic lights because sometimes some people ignore them.
_______________
* Including any ports independently based on the Boom source code, which may have nothing to do with these "advanced Boom compatible" ports you are thinking of, yet would still be able to refer to Boom in respect to any differences.
|