-
Notifications
You must be signed in to change notification settings - Fork 30
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
FluidStorage support #92
Comments
We've had some discussion about adding support for the Fabric Transfer API with respect to item transport. Unfortunately, the way the Fabric API is set up makes it impossible to port the current generic One awkward aspect of this, as you noted, is that the Fabric If anyone knows a good solution, let me know. |
Never mind I was misunderstanding how type erasure is implemented! This is possible with reflection, but the generic peripheral system currently explicitly disallows targeting parameterized types. I guess we would need to change that. |
Sometimes I hates cc api, especially in this part. I am not defenetly not sure how to do this, because generic api always was a mystery for me( |
You should query instances via FluidStorage.SIDED.find(...) (similar to capabilities on forge) for the fluid API. This will always give a |
Well, I know how to do this :) I am hate generic API design, because it focused on some AST magic and I am don't want to touch it :( I will just implement separate mod for this, if no one will fix this issue before I get to this mod |
if you know how, do not be afraid to PR |
So, Fabric released FluidStorage logic and I want to try to implement it in cc-restitched.
But seems this required total refactoring of generic peripheral logic, because currently, as I understand, it just checks
if this tile can be converted to specific interface
.So, do you have any plans for it?
The text was updated successfully, but these errors were encountered: