Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] NDCP2 MAP21 kill trigger bug #2856

Open
1 task done
Player701 opened this issue Dec 10, 2024 · 0 comments
Open
1 task done

[BUG] NDCP2 MAP21 kill trigger bug #2856

Player701 opened this issue Dec 10, 2024 · 0 comments
Labels

Comments

@Player701
Copy link
Contributor

GZDoom version

4.13.2 and g4.14pre-120-gfb660fa3c

Which game are you running with GZDoom?

Doom 2

What Operating System are you using?

Windows 11

Please describe your specific OS version

N/A

Relevant hardware info

N/A

Have you checked that no other similar issue already exists?

  • I have searched and not found similar issues.

A clear and concise description of what the bug is.

While NDCP2 is known to be buggy, there is a certain issue with its MAP21 that appears to be GZDoom-specific. In the first outdoor area, stepping off the floor and into the void will not instantly kill the player like it should - instead, the players simply ends up being stuck in the void, unable to continue. In PrBoom-Plus v2.5.1.4, the player gets instantly gibbed instead, which is correct behavior.

Steps to reproduce the behaviour.

Explain how to reproduce

  1. gzdoom -file ndcp2.wad -iwad doom2 -warp 21 -nomonsters +"warp 1720 -2080"
  2. Step forward into the void
  3. The player is not killed, but becomes stuck instead.

Your configuration

N/A

Provide a Log

N/A

@Player701 Player701 added the bug label Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant