ZDoom

im been playin with this mod, and i realy like it, idk if you still taking feedback, but what about a keybind for vacumm mode (i dont know if its already a thing in the mod but in cant see anithing about that, its that possible? It already existed, you should found the option in the "mod stuff" sub ...

I think that's the normal behavior of the original game, no other way to "forced on one mode" as far I know.
(Maybe I could be wrong but I remember most of Build engine games did that.)
Don't know if the devs plan to change this...

The download page on zdoom.org still shows 4.13.2.
https://i.imgur.com/zf9jdMv.png
EDIT: I see right now only Windows build exists...so it make sense if waits until later when other builds to be complied.

[4.12/4.12.1] Weird crash to desktop on start a new game, on True color SW with some settings. Tested on 4.12 and 4.12.1, g4.13pre-15 and 17. 4.10 and 4.11 is fine. Set following setting to reproduce: API: OpenGL Fullscreen: Yes Render: True Color SW Renderer Resize Textures: On (this one not sure ...

The Raze one seems the same behavior of GZDooM, which not existed in original.

In Eduke32, that was the same as original Build engine/Duke3D behavior as far as I know and I think you can't change that.

Imgur still fine to me, but you still need account to upload images, viewing seems still account-less.

Well, I know it maybe bad idea about using latest GZDooM dev build to play the mod as it still labeled as 4.7.1...since I saw the mod did still updated recently in Github so I guessed the mod would still based on latest versions of GZDooM...And most of the mod seems still working fine after I play ...

Not sure if this info useful or not, I tried run this mod with latest dev build g4.11pre-76(or even the earliest one I can download, g4.11pre-24), when screen melt finished/near finish after choose new game and difficulty, I got GZDoom.exe went frozen with Windows' crash report message(In OpenGL ...

That's because those hacks are exploiting flaws in how their client software works, and shouldn't be thought of as being the same as what we're seeing here. Thanks for tell me about that, good to know. I'm glad I only use web version of Discord(as I know web version is safe from those exploits but ...

Valherran wrote: ↑Wed Jan 18, 2023 9:59 pm Well damn, I guess 2FA is the only way to really combat that.

I just remembered Discord's hacks can even skip 2FA by click a server invite link and the user got hacked. Well, that's more like Discord's site problems but just saying.

Since I cannot remember 20+ characters of passwords after some weeks and months(even the password is something that only myself can know...I still can forgot it totally), I let Firefox's password manager(not really trust those passwords storage websites) helped me to deal with that...at worse, just ...

Don't have problem if I just load GC 3.888b or NC 3.4 in standalone. It maybe something in your autoload directory caused that, you could try finger that out by taking one of them out and see if problem gone or not.

I'm glad I missed the April fool joke on the forum...(lazy to open the forum yesterday)

Never fan of that kind of website designs sadly...

You can say Powerslave Exhumed is a port to original Console version(built with KEX engine, plus mixing things from Build engine(DOS) version), so Raze won't run "the port" at all, nor the original Slavedriver engine like wildweasel said. The console version(Saturn, not PS1/PSX) of Duke3D was used ...

Since this mod needed at least GZDoom 4.2.4 and questzdoom's LZDoom 3.83a/GZDoom g3.3mgw branch was much older, out-dated versions, so I think it's not possible without update the engine version, I'm sure it'll be more break-age beside that error, since the mod should using more latest GZDoom things ...