cmss13-devs / cmss13-pve Goto Github PK

Flaky tests were detected in this test run. This means that there was a failure that was cleared when the tests were simply restarted.
Failures:

Testmerges

There were a few but I do not recall which besides Rock's new game mode being one of them

Round ID

No response

Description of the bug

Bug discovered in on-going rounds where the carrier AI has been utilized (although they are rare). Clicking on the carrier as a observer allows you to take control of a human facehugger. I noticed this in an on-going round on Rock's new map and was in fact able to take over as a facehugger in an on-going PVE round, though I made sure to die immediately as it is unintended.

What's the difference with what should have happened?

We don't want human xenos unless it's a pre-planned GM thing, obviously.

How do we reproduce this bug?

1. Observe in an on-going round
2. Sprite click on a carrier
3. Accept to become a player controlled hugger
4. You are now gaming harder than intended

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)

Flaky tests were detected in this test run. This means that there was a failure that was cleared when the tests were simply restarted.
Failures:

Flaky tests were detected in this test run. This means that there was a failure that was cleared when the tests were simply restarted.
Failures:

Testmerges

Doubt those are relevant

Round ID

Ditto

Description of the bug

Sune said he couldn't hear anything around him when he played as a cat and got scooped up
Probably because held mobs get put in a holder item that then gets put in the mob
Locker code has a proc that could be used here, but I don't quite know how to replicate this bug by myself on a local host to try and fix it so I'll leave this here as a reminder

What's the difference with what should have happened?

Should be able to hear

How do we reproduce this bug?

1. get picked up
2. ???
3. Hearing loss

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)

Testmerges

i forgor

Round ID

i forgor

Description of the bug

It won't play anything

What's the difference with what should have happened?

it shouldve played music

How do we reproduce this bug?

1.buy walkman
2.insert caset
3.yes
...

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)

          In the sickbay, there's sleepers with body scanner consoles, so as a result, they don't work for either purpose.

Originally posted by @Mark9013100 in #180 (comment)

yeah.

Testmerges

N/A

Round ID

No response

Description of the bug

When an AI-controlled xeno is unable to reach its target it consumes a very large chunk of server performance.

What's the difference with what should have happened?

Three AI xenos should not consume an outsized amount of server performance.

How do we reproduce this bug?

1. Place a target in an isolated, unreachable location.
2. Place an AI xeno such that it cannot reach the target, but has a large area to pathfind in.
3. Observe performance impact.

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)

Testmerges

#64: 'Hotfix canmove' by morrowwolf at commit 84db018ff2
#72: 'Projectile smooth movement' by Doubleumc at commit 52c021137b

Round ID

229 on red

Description of the bug

What's the difference with what should have happened?

they shouldn't be there

How do we reproduce this bug?

1. get radio backpack
2. go to marine section
3. look
   ...

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)

Testmerges

bf56402

Round ID

1583

Description of the bug

Maintenance jack has no click cooldown when it comes to resin walls allowing them to instantly destroy them
https://youtu.be/7vlosS-8KJc

What's the difference with what should have happened?

I should not be able to destroy a wall in 2 seconds

How do we reproduce this bug?

1. Grab a maintenance jack
   2.attack a resin wall fast

...

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)

Flaky tests were detected in this test run. This means that there was a failure that was cleared when the tests were simply restarted.
Failures:

check_runtimes: [12:44:04]RUNTIME: Cannot execute null.handle speak(). - handset.dm@51 at code/modules/unit_tests/check_runtimes.dm:10