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

[EMI compat] EMI doesn't detect lubricant in the cutting machine #816

Open
jonatjano opened this issue Aug 3, 2024 · 4 comments
Open

[EMI compat] EMI doesn't detect lubricant in the cutting machine #816

jonatjano opened this issue Aug 3, 2024 · 4 comments

Comments

@jonatjano
Copy link

issue

When using the EMI crafting tree, it gives fast access to shortcuts to fill the machine slots,

but it doesn't work for the cutting machine because I can't have a millibucket of lubricant in my inventory and EMI doesn't detect the lubricant slot of the machine.

As can be seen on the following screenshot, I have the bronze rod and some lubricant in the machine but EMI says that I can't craft any bronze bolt

image

expected result

EMI should detect the lubricant in the machine and allows me to craft the bolts

versions

NeoForge : 21.0.116-beta
Modern Industrialization : 2.2.14-beta
EMI : 1.1.10+1.21+neoforge

@Technici4n
Copy link
Contributor

EMI handles all the work of moving items, and unfortunately it doesn't look like it has any built-in handling of fluids.

@jonatjano
Copy link
Author

should I open an issue on EMI's side ?

@Technici4n
Copy link
Contributor

Yes that is a good idea.

@jonatjano
Copy link
Author

Back here, EMI's dev answered to the issue saying that the issue is on your side :

MI is not exposing their input slots as part of their inventory, as is necessary for EMI to assume you have lubricant and assume this is craftable.

meanwhile I also found that the issue is present in the mixer, and, I suppose, any machine with fluid inputs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants