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
Player can ragdoll themselves while holding sword and then be killed by it, if the sword is moving fast enough.
Maybe this doesn't have to be fixed and encourage not playing with swords haphazardly - but I think it's probably not the best experience. Maybe should discuss before deciding to fix.
To Reproduce
Grab sword, jump while running and press F to ragdoll. Position / speed will impact repro, video attached to help see how.
Expected Behavior
Player probably shouldn't be allowed to be killed by sword in this way, but I'm not sure if we want to say they can't ever be killed by a sword they threw either
Like if some mechanic bounces the sword back, or it bounces of sproinger and they run into it - probably should die). Maybe some sort of timer or something to fix this - need to think about it.
Additional Context
own_sword_death.mov
Log Messages
No response
The text was updated successfully, but these errors were encountered:
Description
Player can ragdoll themselves while holding sword and then be killed by it, if the sword is moving fast enough.
Maybe this doesn't have to be fixed and encourage not playing with swords haphazardly - but I think it's probably not the best experience. Maybe should discuss before deciding to fix.
To Reproduce
Grab sword, jump while running and press F to ragdoll. Position / speed will impact repro, video attached to help see how.
Expected Behavior
Player probably shouldn't be allowed to be killed by sword in this way, but I'm not sure if we want to say they can't ever be killed by a sword they threw either
Like if some mechanic bounces the sword back, or it bounces of sproinger and they run into it - probably should die). Maybe some sort of timer or something to fix this - need to think about it.
Additional Context
own_sword_death.mov
Log Messages
No response
The text was updated successfully, but these errors were encountered: