We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
515.1647
Borg mining satchel is not picking up ores automatically when equipped as expected, you have to hit the ore with the satchel to collect it.
Video here (wont upload to GitHub for some reason): https://files.catbox.moe/hxnpbx.mp4
I expected to pick up the ore automatically as is what happened with it in the past and with any other mining satchel
I didn't pick up the ore as expected.
Borgs satchels should work the same as a normal mining satchels and has worked in the past, so this is likely a bug.
Become a mining borg, equip mining satchel, try and go over ores
I have not played mining Borg in a while but I know it worked before.
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Exploit Reports
BYOND Version
515.1647
Issue Description
Borg mining satchel is not picking up ores automatically when equipped as expected, you have to hit the ore with the satchel to collect it.
Video here (wont upload to GitHub for some reason): https://files.catbox.moe/hxnpbx.mp4
What did you expect to happen?
I expected to pick up the ore automatically as is what happened with it in the past and with any other mining satchel
What happened instead?
I didn't pick up the ore as expected.
Why is this bad/What are the consequences?
Borgs satchels should work the same as a normal mining satchels and has worked in the past, so this is likely a bug.
Steps to reproduce the issue.
Become a mining borg, equip mining satchel, try and go over ores
When did the problem start happening?
I have not played mining Borg in a while but I know it worked before.
Extra information
No response
Relevant log output/runtime error
The text was updated successfully, but these errors were encountered: