Edits regarding software renderer

Can you clarify which, if any, particular port(s) you are indicating that this class of problem is for? I ask because we have a policy against documenting bugs that are specific only to certain ports, or certain versions of ports, in the case where mods are playable on many of them (vanilla or Boom mods should not document bugs that only occur in versions of GZDoom, for example). I postponed approval on them earlier and figured somebody else might handle it but evidently not. --Quasar (talk) 20:11, 23 July 2023 (CDT)

The MAP26[1] and MAP28[2] edits both hold true for PrBoom+ which the wad txt claims compatibility for (and it also applies to derivatives like DSDA-Doom). It does not occur in GZDoom, and the MAP06[3] fence oddity I could not produce again on any port. Assuming ports officially recommended by the wad author(s) are a reasonable exception to the policy, I'll ditch the MAP06 edit for now and bring the other two up to a workable standard. Of note for that discussion is also a bug I added (and got approved) for Ancient Aliens MAP23[4] that only happens for old versions of GZDoom (which were contemporary with the wad's release), and for all versions of Zandronum. In my opinion, this is important enough to note even if it flies in the face of policy as you describe it. -Inuk (talk) 05:34, 24 July 2023 (CDT)

What complevel are we talking here? Because PrBoom+ offers different ones, as do many other ports. You should clarify which one you tried it under. --Dynamo128 (talk) 05:38, 24 July 2023 (CDT)

The complevel is the correct one, 11, as specified by the wad txt. I figure this is unnecessary information to include in the edits. -Inuk (talk) 05:45, 24 July 2023 (CDT)

Very well, just making sure. :) --Dynamo128 (talk) 05:50, 24 July 2023 (CDT)