search

cmss13-devs / cmss13

Contains the code for CM-SS13
https://cm-ss13.com
GNU Affero General Public License v3.0
101 stars 563 forks source link

Strange location in ares bioscan - LV-624 #5882

Open gitbirb opened 8 months ago

gitbirb commented 8 months ago

Testmerges

5774: 'Updated XM43E1 for Sniper Spec' by Kaga-404 at commit 2bd532a406 #5829: 'Event borers' by realforest2001 at commit bac22e8282 #5007: 'Project ARES TM Holder (v4)' by realforest2001 at commit ea22a09adb #5401: 'M540-A Armored Recon Carrier' by Zonespace27 at commit 9be4807644

Round ID

21177

Description of the bug

image

Last xeno in . is not a descriptive location

What's the difference with what should have happened?

Should show an area name

How do we reproduce this bug?

Apparently it's a problem with the xeno dying right as bioscan happens according to Antixenobuff

  1. Have a bioscan occur at the exact moment the last xeno dies ?

Issue Bingo

Antixenobuff commented 8 months ago

This was a bug with the xeno and not with the ARES. I was observing that round. The defender died in the exact moment the ARES bioscan was taking place. So not actually a bug, but neither a feature. Just bad timing.

HaultyAnonie commented 8 months ago

This was a bug with the xeno and not with the ARES. I was observing that round. The defender died in the exact moment the ARES bioscan was taking place. So not actually a bug, but neither a feature. Just bad timing.

Happened before, many times, rare but happens.

Huffie56 commented 8 months ago

@gitbirb hello please update your issue with the above comment. thanks