Right-clicking with a fluid conduit in a block of an already placed fluid conduit bug 1.20.1 #986
Labels
No labels
Area-Assets
Area-Backend
Area-Conduits
Area-Datapacks
Area-Lang
Area-Mod Compat
Area-Parity
Area-Rendering
Good first issue
MC-1.19.2
MC-1.20.1
MC-1.20.4
MC-1.20.6
MC-1.21
MC-1.21.1
Modtoberfest
P-0-High
P-1-Medium
P-2-Low
Status-Awaiting Response
Status-Behind-Flag
Status-Blocked
Status-Cannot Reproduce
Status-Duplicate
Status-Help Wanted
Status-Incomplete Report
Status-Invalid
Status-Needs LTS Backport
Status-Needs Updating
Status-Stale
Status-To Implement
Status-Triage
Status-Wontfix
Status-Wontmerge
Type-Backport
Type-Bug
Type-Documentation
Type-Enhancement
Type-Question
Type-RFC
Type-Suggestion
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Team-EnderIO/EnderIO#986
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Is there an existing issue for this?
Current Behavior
Attempting to place a fluid conduit of in the block of a different fluid conduit either voids the conduit of your current conduit or voids the item from your hand (upgrades without returning or just doesn't do anything and uses the item)
Expected Behavior
The lower tier conduit would be returned or nothing would happen (doesn't get voided when tested with me conduits)
How to Test
Local Environment
Any Additional Information?
No response
Any workaround?
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.
the same happen on 1.21.1
It might be addressed in the latest v8 preview in our Discord - my plan for when I go back and close 1.20.1 issues is that I'll re-test them using
dev/1.21.1, if the problems persist I will leave the issues open and make sure they are still addressed :)