You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I confirm this issue is not an exploit. (Required)
BYOND Version
515.1630
Issue Description
If you observer observe someone and they get stunned and grabbed, their inventory might stack with the one who grabs them. I am not 100% sure about what is actually happening, however it might be related to: #19169
What did you expect to happen?
For the observed inventory to stay intact
What happened instead?
Cuffs on top of satchel. Satchel in hands while cuffed.
Why is this bad/What are the consequences?
Its hard to figure out who has what.
Steps to reproduce the issue.
Observer observe someone (I observed a vampire).
Open their backpack.
Have the person stunned by a stun baton.
Have the person grabbed.
Have the grabber take off the grabees bag.
When did the problem start happening?
Noticed today 14.09.2024.
Extra information
I only got this once, not sure if these are the correct steps to reproduce the issue.
Relevant log output/runtime error
No response
The text was updated successfully, but these errors were encountered:
This is related to various observer inventory item ghosting issues. Sometimes floating inventory items can remain on screen even when the bag is closed.
Exploit Reports
BYOND Version
515.1630
Issue Description
If you observer observe someone and they get stunned and grabbed, their inventory might stack with the one who grabs them. I am not 100% sure about what is actually happening, however it might be related to: #19169
What did you expect to happen?
For the observed inventory to stay intact
What happened instead?
Cuffs on top of satchel. Satchel in hands while cuffed.
Why is this bad/What are the consequences?
Its hard to figure out who has what.
Steps to reproduce the issue.
When did the problem start happening?
Noticed today 14.09.2024.
Extra information
I only got this once, not sure if these are the correct steps to reproduce the issue.
Relevant log output/runtime error
No response
The text was updated successfully, but these errors were encountered: