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
Describe the bug
As per the title. We have been trying to fix this by slightly increasing hitboxes of various units, and we have come a long way. Though it does seem like there is something else going on, that we currently do not understand.
To Reproduce
Launch a sandbox game with cheats enabled.
Enable the NoDamage console command.
Spawn in a Wagner or a similar unit. Quick units with smaller hitboxes are affected the most.
Spawn in 30 Seraphim Tech 2 PDs in a circle
Have the PDs attack the unit and move it in circles.
The bug does not occur when you spawn the PDs first instead of the Wagner.
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
For further context and replays, see #5768 and #6227.
The text was updated successfully, but these errors were encountered:
A recent example of this can be observed in 22732109. At 15:20, a Seraphim destroyer can be seen missing Auroras, even though Auroras should have sufficient SizeZ at 1.1. The cause of this appears to be the fact that the Auroras were built before the destroyer was.
Basilisk3
changed the title
Beam weapons can miss units that already existed before they were constructed
Beams can miss units that already existed before the beam weapon was constructed
Jun 22, 2024
Describe the bug
As per the title. We have been trying to fix this by slightly increasing hitboxes of various units, and we have come a long way. Though it does seem like there is something else going on, that we currently do not understand.
To Reproduce
NoDamage
console command.The bug does not occur when you spawn the PDs first instead of the Wagner.
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
For further context and replays, see #5768 and #6227.
The text was updated successfully, but these errors were encountered: