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

oozeling stowaway shenanigans #4136

Open
MonkestationIssueBot opened this issue Nov 7, 2024 · 1 comment
Open

oozeling stowaway shenanigans #4136

MonkestationIssueBot opened this issue Nov 7, 2024 · 1 comment
Labels
bug Something isn't working Major

Comments

@MonkestationIssueBot
Copy link

MonkestationIssueBot commented Nov 7, 2024

Reporting client info: Client Information:
BYOND:515.1645
Key:breadmond

Round ID:

7726

Testmerges:

Reproduction:

if you are an oozeling and a stowaway, when you are revived, you are sent to a random place where you could have spawned when first arriving at the station, despite already being at the station, and if you also have family heirloom, you get another family heirloom when you are revived. it is rather odd

@MissClassyPineapple
Copy link
Contributor

Successfully reproduced. When dying as an Oozeling you are technically assigned an item to control, that item being your core. As such, your body is deleted and a new one is spawned when you are revived. All characters are spawned initially without quirks and the quirks assigned immediately after. With the quirks "stowaway" and "family heirloom" getting the quirk assigned teleports you to an eligible container and spawns your family heirloom in your inventory respectively.
Ooze revival goes approx. from what I can see: Plasma poured on core -> Body spawned -> Quirks assigned -> Quirks take effect -> Player placed in control of body.
The interaction of the quirks being assigned is likely what creates the stowaway shenanigans.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Major
Projects
None yet
Development

No branches or pull requests

3 participants