Might be a case of this, however, the explanation in that thread doesn't seem applicable.
I'm not sure if this is a bug or an oversight. I tested in 4.8.0, 4.8.2 and I remember seeing this behavior earlier as well.
A_FireProjectile returns null when a projectile is fired into a wall or an enemy at a point-blank range, even if the projectile is NOT actually destroyed but instead enters a Death/Crash/XDeath state sequence. This makes no sense to me, since projectiles may still exhibit complex behavior at that point (for example, I need to dynamically set a spawned projectile's sprite and damage from the weapon when it's fired).
A_FireProjectile returns null at point-blank range
Moderator: GZDoom Developers
Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.
-
Jekyll Grim Payne
- Global Moderator
- Posts: 1117
- Joined: Mon Jul 21, 2008 4:08 am
- Preferred Pronouns: He/Him
- Graphics Processor: nVidia (Modern GZDoom)
- Contact:
-
Graf Zahl
- Lead GZDoom+Raze Developer
- Posts: 49225
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
Re: A_FireProjectile returns null at point-blank range
Obviously this cannot be changed because it would alter the semantics of this function.
So now the function will pass through the second return value of SpawnPlayerMissile which contains what you need.
So now the function will pass through the second return value of SpawnPlayerMissile which contains what you need.