Burrower Can Burrow Across Map

[Steelpoint]

Testmerges

#5914: 'Ports stripping menu from TG' by ihatethisengine at commit cf954c3 #5401: 'M540-B Armored Recon Carrier' by Zonespace27 at commit 8e87180 #6103: 'Med Vendor Rebalance' by Drulikar at commit bfdc7f3 #5957: 'OT CAS rocket' by iloveloopers at commit d9da5fe #6039: 'Project ARES TM Holder (v5)' by realforest2001 at commit e46cc87 #6114: 'dehardcodes client version warnings' by harryob at commit 653037e #6062: 'Stabilized metallic foam, a gimmick new flamer fuel' by iloveloopers at commit 60f39dd

Round ID

21749

Description of the bug

Burrowers can burrow across the entire map via exploiting the ability to view any other xenomorph via the 'view hive list' function and then burrow to them while they can view them. It can take up to five minutes for a burrower to actually burrow across the map due to the extreme distances.

What's the difference with what should have happened?

Burrowers should only be able to burrow within vision range.

How do we reproduce this bug?

1. You need to be able to view hive status, so a Queen must be alive.
2. As a Burrower, burrow into the ground as normal.
3. Once burrowed you can go to hive status to view any other Xenomorph.
4. If you do this the game kicks you out of the view and back to viewing yourself.
5. In order to start a tunnel you need to spam click the tunnel button on a tile on the other xenomorph you are viewing in the <1 second you are able to view the xenomorph before you are kicked back to viewing yourself
   ...
   This is fairly difficult to achieve as most of the time the game will refuse to allow you to tunnel. I found best success by minimizing the hive status window to get the "view" button of a xenomorph as close to the centre of my screen so I could quickly spam click the target xeno and the view button as quickly as I could before it kicks you out.

I have been able to replicate this several times during the same round.

I tried testing this on a offline server but I was unable to replicate the result (though this could just be bad luck due to how hard it is to pull off the bug), I was only able to do this on the live server.

Issue Bingo

• Issue could be reproduced at least once
• Issue happened in a recent (less than 7 days ago) round
• Couldn't find an existing issue about this (https://github.com/cmss13-devs/cmss13/issues)