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
In versus when switching to the survivor team while riding a survivor as a Jockey, the survivor you'll switch into will teleport and get stuck out of bounds.
When switching to the Infected team while ridden the survivor can also rarely lose their primary weapon slot resulting in a T pose.
What should happen is that my jockey should either be AI controlled or die/get shoved of the survivor while i drop into a free player slot on the other team while remaining on the spot the bot was on.
Reproduction steps
Start as the Infected
Switch to the survivor team while riding a survivor as the jockey
You'll notice that you got teleported out of bounds.
This happned often in vanilla when testing in private servers with friends.
This happens on any map. I dont if this has already been covered or what happens in the code but it is a bug that impact gameplay that is really easy to reproduce. Hopefully this could at the very least spread awareness of it.
The text was updated successfully, but these errors were encountered:
Description
In versus when switching to the survivor team while riding a survivor as a Jockey, the survivor you'll switch into will teleport and get stuck out of bounds.
When switching to the Infected team while ridden the survivor can also rarely lose their primary weapon slot resulting in a T pose.
What should happen is that my jockey should either be AI controlled or die/get shoved of the survivor while i drop into a free player slot on the other team while remaining on the spot the bot was on.
Reproduction steps
This happned often in vanilla when testing in private servers with friends.
Additional files
On the first map of The Parish:
https://steamcommunity.com/profiles/76561198271919148/screenshot/2304221278416442335/
Second map of Crash Course:
https://steamcommunity.com/profiles/76561198271919148/screenshot/2304221278416552550/
This happens on any map. I dont if this has already been covered or what happens in the code but it is a bug that impact gameplay that is really easy to reproduce. Hopefully this could at the very least spread awareness of it.
The text was updated successfully, but these errors were encountered: