Skip to content
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

[API Request] More by-type-registered handlers for better optional compatibility #4702

Open
XFactHD opened this issue Apr 27, 2023 · 0 comments
Labels
area: api Issue or PR is related to API status: fixed in next release Issue will be fixed in the next release

Comments

@XFactHD
Copy link

XFactHD commented Apr 27, 2023

At the moment, a lot of systems which mods may want to use for improved compatibility are exclusively usable by implementing interfaces on blocks or blockentities. This is a major problem for mods that cannot make Create a hard dependency. I would like to request that at least some of these interfaces get complementing handlers that can be registered for a type like is already the case for MovingInteractionBehaviour, BlockMovementChecks and a few others, which can be registered behind appropriate guards to avoid making Create a required dependency.
The cases I am running into specifically are ITransformableBlock and ITransformableTE for improved rotation support as well as ISpecialBlockEntityItemRequirement and IPartialSafeNBT for improved Schematicannon support in FramedBlocks.

@IThundxr IThundxr added area: compatibility Issue only happens when other mods are present status: confirmed Issue's details are known, it is consistently reproducible, and it needs a fix labels Mar 14, 2024
@IThundxr IThundxr added area: api Issue or PR is related to API and removed area: compatibility Issue only happens when other mods are present labels Nov 17, 2024
@IThundxr IThundxr self-assigned this Dec 13, 2024
@IThundxr IThundxr added status: fixed in next release Issue will be fixed in the next release status: confirmed Issue's details are known, it is consistently reproducible, and it needs a fix and removed status: confirmed Issue's details are known, it is consistently reproducible, and it needs a fix status: fixed in next release Issue will be fixed in the next release labels Dec 17, 2024
@IThundxr IThundxr removed their assignment Dec 19, 2024
@IThundxr IThundxr closed this as completed Jan 6, 2025
@IThundxr IThundxr reopened this Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: api Issue or PR is related to API status: fixed in next release Issue will be fixed in the next release
Projects
None yet
Development

No branches or pull requests

2 participants