-
Notifications
You must be signed in to change notification settings - Fork 14
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
[Bug] Bound entangled blocks can no longer be placed without resetting them #71
Labels
bug
Something isn't working
Comments
Lapis256
added a commit
to Lapis256/Entangled
that referenced
this issue
Mar 14, 2024
SuperMartijn642
pushed a commit
that referenced
this issue
Apr 19, 2024
SuperMartijn642
pushed a commit
that referenced
this issue
Apr 19, 2024
SuperMartijn642
pushed a commit
that referenced
this issue
Apr 19, 2024
SuperMartijn642
pushed a commit
that referenced
this issue
Apr 19, 2024
SuperMartijn642
pushed a commit
that referenced
this issue
Apr 19, 2024
SuperMartijn642
pushed a commit
that referenced
this issue
Apr 19, 2024
SuperMartijn642
pushed a commit
that referenced
this issue
Apr 19, 2024
SuperMartijn642
pushed a commit
that referenced
this issue
Apr 19, 2024
SuperMartijn642
pushed a commit
that referenced
this issue
Apr 19, 2024
SuperMartijn642
pushed a commit
that referenced
this issue
Apr 19, 2024
SuperMartijn642
pushed a commit
that referenced
this issue
Apr 19, 2024
SuperMartijn642
pushed a commit
that referenced
this issue
Apr 19, 2024
SuperMartijn642
pushed a commit
that referenced
this issue
Apr 19, 2024
SuperMartijn642
pushed a commit
that referenced
this issue
Apr 19, 2024
SuperMartijn642
pushed a commit
that referenced
this issue
Apr 19, 2024
Fixed now in version 1.3.18. |
Blacklists for Applied Energistics and Refined Storage have also been removed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version Info
Description of the Bug
Since the blacklist was implemented (#27) bound entangled blocks may no longer be placed. Attempting to place one results in the following message.
Binder is bound to unknown dimension 'minecraft:'
The block may only be placed again if it is cleared by re-crafting it.
Steps to Reproduce
Screenshots
Video: https://streamable.com/5m9e33
As a side note, I think the blacklist is a great tool, but the default of blocking all of ae2/rs across the board feels like too broad a stroke. Entangled blocks have worked fine for years to insert into Interfaces and provide power to Controllers; all the things a reasonable player would expect them to work with. I have worlds where P2P inputs are entangled, allowing me to input into them further away. Pattern interfaces are entangled, allowing me to send the result of a craft back to it to trigger the next. I feel this default blacklist breaks more of the good functionality than it truly fixes.
Rather, it seems to me that a simple copypasta explaining why they cannot work with networking would serve you better and help people understand how these are meant to work. Not everyone understands what the capability system does, and trust me we've fielded a lot of questions in our discord from players who don't understand how they work. A brief explanation has been enough to set them straight though. Will you get questions about it still? Absolutely. But you can just point people at the copypasta and leave it at that.
EnigmaticaModpacks/Enigmatica9#883
The text was updated successfully, but these errors were encountered: