I don't think MSPaintR0cks honestly knew that Doom has such a dubious history with executables. Even I keep forgetting.Rachael wrote:No one gave you or Scuba Steve trouble because everything just worked. You didn't *have* to run someone else's executable - which you don't know the source, you don't know what's compiled into it, etc. This is a community that is very paranoid of executables that come from any random source - and you have to understand, that is with VERY good reason. The Doom community as a whole is no stranger to malware - even from sources we thought we could trust, there have been past examples where people, even from official sources, have distributed executables that deleted doom2.wad, DDoS'd ZDaemon servers, etc. I'm not saying that the author here would do that - I would say, you just can't be too careful in this setting.
You just assume everyone knows everything about this community, and sometimes we're not in the know.
I want to state the only thing different about the zdoom.exe executable is the fact the icon changed. I know because I created it using a resource editor. If I knew it was gonna cause that much trouble I'd have told MSPaintR0cks to use my custom executables as the source code is readily available on my GitHub repo. Which in hindsight is what should have been done. I could have even forked to use a different icon and the works.
As for it running in GZDoom 3.1.0, I tested it with the latest dev build and it seems to work, albiet with some warnings and some path follower objects not working on E1M4. I'm gonna consult with MSPaintR0cks and work on a fix.
For what it's worth, I do believe security is important, and I get being paranoid is a product of that. However it can scare people too much if they lose their marbles.