by Blzut3 » Fri Mar 18, 2016 1:23
There's a fundamental difference in the concept of a "mod" in the Wolf3D community. Since they edit the source code to Wolf4SDL directly there are infinitely more things that can be done compared to an ECWolf mod. However, if they were to edit the source code to ECWolf they would be empowered even more so. (I don't necessarily discourage people from doing that, but I ask that any source mod of ECWolf not be called an "ECWolf mod.")
To put another way, Wolf4SDL doesn't itself (the version you get from Ripper's website) support many of things OE:L does either. Their engine deriving from Wolf4SDL does.
The argument about parallax skies is because Ripper provides in the source code some code that can be enabled for that feature with relative ease. It still exists in ECWolf's source code, so in a way it supports parallax skies just as much as Wolf4SDL does.
(That said, it would need some changes to work. Not difficult, but I have another way I want to handle skies.)
There's a fundamental difference in the concept of a "mod" in the Wolf3D community. Since they edit the source code to Wolf4SDL directly there are infinitely more things that can be done compared to an ECWolf mod. However, if they were to edit the source code to ECWolf they would be empowered even more so. (I don't necessarily discourage people from doing that, but I ask that any source mod of ECWolf not be called an "ECWolf mod.")
To put another way, Wolf4SDL doesn't itself (the version you get from Ripper's website) support many of things OE:L does either. Their engine deriving from Wolf4SDL does.
The argument about parallax skies is because Ripper provides in the source code some code that can be enabled for that feature with relative ease. It still exists in ECWolf's source code, so in a way it supports parallax skies just as much as Wolf4SDL does. :P (That said, it would need some changes to work. Not difficult, but I have another way I want to handle skies.)