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
Regalis11 opened this issue
Dec 18, 2024
Discussed in
#15046
· 1 comment
Assignees
Labels
BugSomething isn't workingCodeProgramming taskTicketThe issue has been converted into an issue report.UnstableTickets that are included and being tested in the current Unstable build.
for example, attempting to use this submarine while team2 (seperatist) in either sub v sub or KoTH mode will result in them spawning way in incorrect spots.
as you can see, blue team spawns correctly.
Reproduction steps
use that sub
join seperatist team in sub v sub
go in freecam and debugai, see how weirdly it spawns
Bug prevalence
Happens every time I play
Single player or multiplayer?
Multiplayer hosted using a dedicated server
-
No response
Version
v1.6.19.1 (Unto the Breach Update Hotfix 2)
-
No response
Which operating system did you encounter this bug on?
Windows
Relevant error messages and crash reports
No response
The text was updated successfully, but these errors were encountered:
BugSomething isn't workingCodeProgramming taskTicketThe issue has been converted into an issue report.UnstableTickets that are included and being tested in the current Unstable build.
Discussed in #15046
Originally posted by girlyguppy November 3, 2024
Disclaimers
What happened?
SvS beacon vs beacon.zip
for example, attempting to use this submarine while team2 (seperatist) in either sub v sub or KoTH mode will result in them spawning way in incorrect spots.
as you can see, blue team spawns correctly.
Reproduction steps
Bug prevalence
Happens every time I play
Single player or multiplayer?
Multiplayer hosted using a dedicated server
-
No response
Version
v1.6.19.1 (Unto the Breach Update Hotfix 2)
-
No response
Which operating system did you encounter this bug on?
Windows
Relevant error messages and crash reports
No response
The text was updated successfully, but these errors were encountered: