You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
There's no way to ensure A_SpawnItem/A_SpawnItemEx succeeds, even if the actor being spawned has NOCLIP flag, the function ignores it and still refuses to spawn it in some situations.
Describe the solution you'd like
I consider this aspect of its behavior a bug, but of course it has to be maintained, thus a new flag like SXF_NOCHECKPOSITION is needed, but one that would allow spawning in walls/floor/ceiling, at least if they have NOCLIP flag set.
Describe alternatives you've considered
I'm not sure whether it should check for NOCLIP flag or not. If it does, SXF_RESPECTNOCLIP might be a fitting name. If it doesn't, SXF_ALWAYSSPAWN might do.
Add any other context or screenshots about the feature request here.
No response
The text was updated successfully, but these errors were encountered:
GZDoom version
No response
Which game are you running with GZDoom?
None
What Operating System are you using?
None
If Other OS, please describe
No response
Relevant hardware info
No response
Is your feature request related to a problem? Please describe.
There's no way to ensure A_SpawnItem/A_SpawnItemEx succeeds, even if the actor being spawned has NOCLIP flag, the function ignores it and still refuses to spawn it in some situations.
Describe the solution you'd like
I consider this aspect of its behavior a bug, but of course it has to be maintained, thus a new flag like SXF_NOCHECKPOSITION is needed, but one that would allow spawning in walls/floor/ceiling, at least if they have NOCLIP flag set.
Describe alternatives you've considered
I'm not sure whether it should check for NOCLIP flag or not. If it does, SXF_RESPECTNOCLIP might be a fitting name. If it doesn't, SXF_ALWAYSSPAWN might do.
Add any other context or screenshots about the feature request here.
No response
The text was updated successfully, but these errors were encountered: