[1.20] Soul Binder can void Empty Soul Vial #1037

New issue

Closed

opened 2025-03-25 17:59:57 +00:00 by Blackalf · 2 comments

Blackalf commented

2025-03-25 17:59:57 +00:00

(Migrated from github.com)

Is there an existing issue for this?

I did not find any existing issues.

Current Behavior

The Soul Binder doesn't black/whitelist the Empty Soul Vial from the output slots and doesn't check if both the main item and the Empty Soul Vial can be properly output before stopping the recipe.

This leads to a case where if the first output slot is full, usually happens in passive setups, the main item will be output to the second slot and the Empty Soul Vial won't be output at all.

Further more the push feature of the machine will empty the first slot first which means it will need to export automatically all 64 main item before being able to run back as both slots are occupied by the main item and so the machine finally detects there are not enough room for the Empty Soul Vial.

Expected Behavior

The Soul Binder should check that both items can properly be output, additionally the Empty Soul Vial could be blacklisted from the first output slot and whitelisted from the second one.

How to Test

Fill the first Output Slot of the Soul Binder
Start a recipe
See the result

Local Environment

- **Operating System**: Windows
- **Java version**: Adoptium jre-17.0.9.9-hotspot
- **Minecraft Version**: 1.20.1
- **Version**: 6.2.11
- **Other Mods**: Jade and Functional Storage

Any Additional Information?

https://github.com/user-attachments/assets/46b89e6a-c626-4609-bb39-561c06644d27

### Is there an existing issue for this? - [x] I did not find any existing issues. ### Current Behavior The Soul Binder doesn't black/whitelist the Empty Soul Vial from the output slots and doesn't check if both the main item and the Empty Soul Vial can be properly output before stopping the recipe. This leads to a case where if the first output slot is full, usually happens in passive setups, the main item will be output to the second slot and the Empty Soul Vial won't be output at all. Further more the push feature of the machine will empty the first slot first which means it will need to export automatically all 64 main item before being able to run back as both slots are occupied by the main item and so the machine finally detects there are not enough room for the Empty Soul Vial. ### Expected Behavior The Soul Binder should check that both items can properly be output, additionally the Empty Soul Vial could be blacklisted from the first output slot and whitelisted from the second one. ### How to Test 1. Fill the first Output Slot of the Soul Binder 2. Start a recipe 3. See the result ### Local Environment ```markdown - **Operating System**: Windows - **Java version**: Adoptium jre-17.0.9.9-hotspot - **Minecraft Version**: 1.20.1 - **Version**: 6.2.11 - **Other Mods**: Jade and Functional Storage ``` ### Any Additional Information? https://github.com/user-attachments/assets/46b89e6a-c626-4609-bb39-561c06644d27

Rover656 commented

2025-07-12 21:05:30 +00:00

(Migrated from github.com)

I regret to say that we no longer officially support Minecraft 1.20.1 - as such we will not be officially fixing this issue.

If any community member wishes to submit a pull request to address this issue, feel free to open a PR and we will review and merge it.

I will close outstanding 1.20.1 issues in a little while, to keep the issue list clear.

Thanks again for your report.

I regret to say that we no longer officially support Minecraft 1.20.1 - as such we will not be officially fixing this issue. If any community member wishes to submit a pull request to address this issue, feel free to open a PR and we will review and merge it. I will close outstanding 1.20.1 issues in a little while, to keep the issue list clear. Thanks again for your report.

Rover656 commented

2025-10-04 21:42:51 +00:00

(Migrated from github.com)

Closing as 1.20.1 is no longer being maintained, and this issue is no longer present in 1.21.1.
Please see #1156 for more information.
Thanks!

Closing as 1.20.1 is no longer being maintained, and this issue is no longer present in 1.21.1. Please see #1156 for more information. Thanks!