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.1633
Issue Description
Reagent scanners and advanced reagent scanners cannot tell the difference between vox blood and not-vox blood.
What did you expect to happen?
For the scanners to be able to identify vox blood, like how it can identify slime blood.
What happened instead?
Vox blood is just called "blood"
Why is this bad/What are the consequences?
Putting vox blood into someone that isn't a vox would be bad. (This is very unlikely since it's almost always going to be in a labelled IV bag, but stuff happens).
Not IDing chemical correctly is bad.
Steps to reproduce the issue.
Have any container.
Use (advanced) reagent scanner or examine with (advanced) reagent vision.
See "blood" instead of vox blood.
When did the problem start happening?
Probably since forever ago.
Extra information
No response
Relevant log output/runtime error
No response
The text was updated successfully, but these errors were encountered:
Exploit Reports
BYOND Version
515.1633
Issue Description
Reagent scanners and advanced reagent scanners cannot tell the difference between vox blood and not-vox blood.
What did you expect to happen?
For the scanners to be able to identify vox blood, like how it can identify slime blood.
What happened instead?
Vox blood is just called "blood"
Why is this bad/What are the consequences?
Putting vox blood into someone that isn't a vox would be bad. (This is very unlikely since it's almost always going to be in a labelled IV bag, but stuff happens).
Not IDing chemical correctly is bad.
Steps to reproduce the issue.
Have any container.
Use (advanced) reagent scanner or examine with (advanced) reagent vision.
See "blood" instead of vox blood.
When did the problem start happening?
Probably since forever ago.
Extra information
No response
Relevant log output/runtime error
No response
The text was updated successfully, but these errors were encountered: