The bug as described here - "doom.fandom.com/wiki/Hub_4:_Gibbet" - is occurring in the GOG version of Hexen. The mentioned site states the bug was corrected in version 1.1 of the Hexen WAD, so it shouldn't be am issue for the GOG version (1.1). Unfortunately, the described bug locked me in the room with no possibility of further progress. I did have a saved game and this allowed me to progress, after following the work around. For gaming pleasure the bug should be rectified.

PS my first post, so I am prevented from including links, you will need to cut and paste the link. Thanks.

This is very odd, as the CRC32 checksums for the pak0.pak and pak1.pak files in the GOG version are correct.

pak0.pak : 9B25FC97
pak1.pak : 65C5E6F4

To be honest, I'm not entirely sure that this bug was ever fixed. I think that the information about it being fixed may be incorrect, but I would have to do some proper research on it.

Thanks for the input from all contributors. In summary: the game bug appears to have not been fixed in any version, so use the work around to ensure success in this room.

This is why you should use the [url=https://doomwiki.org/wiki/Hub_4:_Gibbet#Bugs]primary wiki.[/url]
I wonder if there is a wad floating around that changes the scripts. A cursory web search only reveals how to make one's own.

For Hexen: Beyond Heretic, I recommend using sourceports, like Chocolate Hexen or GZDoom to play that game:

https://www.chocolate-doom.org/wiki/index.php/Downloads

https://zdoom.org/downloads

IIRC, that bug is addressed in the above sourceports.

If it's fixed in chocolate, that's an issue.

is this bug consistent or just random?

Can confirm it affects Chocolate Doom (although I am using the Steam version WAD)

get-filehash -alg md5 .\HEXEN.WAD
Algorithm Hash
--------- ----
MD5 ABB033CAF81E26F12A2103E1FA25453F

I can confirm this is NOT fixed in GZDoom.

It's script logic design flaw. So it would be naive to expect this bug too be fixed with just an engine replacement.

I totally agree. I was just replying to TheBigCore's post and his "that bug is addressed in the above sourceports" comment. Obviously (and understandably) it is not.

This stupid bug is NOT fixed, all digital versions have it unfixed...

https://github.com/coelckers/gzdoom/issues is the place to report it.

Same for https://github.com/chocolate-doom/chocolate-doom/issues