-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
You cannot put items into toolboxes without first picking up the toolbox #27876
Comments
Are you sure you tried to put an item in the toolbox on help intent? If the intent is not help, you will be unable to put items in storages that are not on you(backpack, as an example) |
here, that PR tweaked that #21946 |
Yes, this was when I was doing testing for my Theta PR (I did a full run as part of it), no reason to even touch intents before starting to clear out science. I just noticed this when I was using the old blue toolbox. |
Can I ask what item it was? Having tested this on and off tables. I can add to the contents of the toolbox just fine. |
This is also affecting first-aid kits. Tried to add a health scanner to one that was on the floor just now in a test server. |
i re-tested it, it works as intended Can you possibly record your game while doing that? |
Exploit Reports
BYOND Version
N/A
Issue Description
You used to be able to put items into toolboxes that were next to you, without picking them up.
You can't do that anymore.
What did you expect to happen?
To put an item into the toolbox on the table next to me.
What happened instead?
It refused to accept the item until I had it in my hand.
Why is this bad/What are the consequences?
This is annoying, as it turns out that putting stuff into a toolbox I'm not using is a thing I do more often than I thought I would.
Steps to reproduce the issue.
Have toolbox next to you.
Try to put item inside.
When did the problem start happening?
Noticed today.
Extra information
This is probably an attack chain migration thing.
Relevant log output/runtime error
The text was updated successfully, but these errors were encountered: