Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ghosting as xeno does not free up the mob (instantly) for someone else to take. #3635

Closed
2 of 3 tasks
Mammle2 opened this issue Jun 15, 2023 · 2 comments
Closed
2 of 3 tasks
Labels
Bug Admin events aren't bugs

Comments

@Mammle2
Copy link

Mammle2 commented Jun 15, 2023

Testmerges

#3470: 'The nuclear option' by morrowwolf at commit 7700ef2 #3605: 'added camera shake and stun to OB.' by Cthulhu80 at commit 0672a9b #3619: 'Shipside role weight nerf' by morrowwolf at commit a0d172a #3601: 'InfluxDB Metrics Backend' by fira at commit 02b721e #3298: 'Project ARES - Resurrection' by realforest2001 at commit 5844c05 #3633: 'Black Goo Patch' by realforest2001 at commit d01bdfb

Description of the bug

I ghosted as xeno (was a leader vampire lurker) since I was going to be busy and the hive was also going to be attacked in a bit so I decided to ghost so someone could take my lurker and go ham instead.

However when I ghosted and took a glance back a couple of minutes later no one had taken the xeno yet and when I attempted to hit join as xeno myself it just told me there were no xenos available and the runner who woulda taken it (well they said "please free mob") pretty much confirmed that the lurker wasn't freed.

What's the difference with what should have happened?

Ghosting as xeno frees up the mob instantly (and in the case of larva usually just has them burrow), when I ghosted as xeno the mob ended up being "SSD" but it wasn't freed for someone to take when usually it will be free and pretty much everyone and their mother who is dead takes it instantly.

How do we reproduce this bug?

  1. Ghost as xeno. (Dunno if it was being leader or a vampire might've been a problem but I'd doubt)
  2. Try to take the xeno using the join as xeno button.
  3. Realize the mob is still "occupied" and can't be taken.

Issue Bingo

@Mammle2 Mammle2 added the Bug Admin events aren't bugs label Jun 15, 2023
@ihatethisengine
Copy link
Contributor

I was the runner in question and can confirm mob wasn't freed. I even ahelped it, but too late.

@SupernovaXTS
Copy link
Contributor

This is part of a bigger problem, players can reenter their bodies after they ghosted

harryob pushed a commit that referenced this issue Jun 16, 2023
# About the pull request

Fixes bugs and following issues:
#3639
#3635

# Explain why it's good for the game

Bugs bad.

# Testing Photographs and Procedure
<details>
<summary>Screenshots & Videos</summary>

Put screenshots and videos here with an empty line between the
screenshots and the `<details>` tags.

</details>


# Changelog
:cl: TheGamerdk, ihatethisengine
fix: player can no longer come back in their bodies after ghosting 
/:cl:
@harryob harryob closed this as completed Jun 16, 2023
Coolgat3 pushed a commit to Wehland-Yutani/WehYu-Station that referenced this issue Jul 1, 2023
# About the pull request

Fixes bugs and following issues:
cmss13-devs/cmss13#3639
cmss13-devs/cmss13#3635

# Explain why it's good for the game

Bugs bad.

# Testing Photographs and Procedure
<details>
<summary>Screenshots & Videos</summary>

Put screenshots and videos here with an empty line between the
screenshots and the `<details>` tags.

</details>


# Changelog
:cl: TheGamerdk, ihatethisengine
fix: player can no longer come back in their bodies after ghosting 
/:cl:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Admin events aren't bugs
Projects
None yet
Development

No branches or pull requests

4 participants