-
Notifications
You must be signed in to change notification settings - Fork 46
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]: Experience bees XP fluid (just dire things) unable to export from ME system #1166
Comments
You can export it into a tank from the Mobs Grinding Utils mod, attach XP Taps, and that's it. |
I just tried that exact setup and the exporters still export nothing |
When I use the me importer on a heated centrifuge the terminal shows it as belonging to just dire things and it's a darker green. I tried using pipez too, it works without a filter, but if you whitelist all the xp fluid variants (including the just dire things xp fluid, I think there are 5 now?) then it stops working too. If I use a fluid tank (ender io) to convert bottle o enchanting to xp juice, then that imports, stores and exports fine using filters. |
someone posted similar issue on reddit: |
The thing I don't understand is why the XP we get is different. I mean, mine comes from mob grinding, and yours from "just dire thing," but that's not normal. We should have the same. Do you have the latest version of the modpack? |
My setup is the same as yours, productive bees, omega upgrades, heated centrifuge The heated centrifuge fluid bar shows it as "XP Fluid" without the mod name, if I use mekanism mechanical pipes then it shows the same dark green "XP Fluid" without a mod name, I only see "Just dire things" once its in the me system. Maybe the 2 fluids are currently flagged the same somehow and the result is randomised? I presume the just dire things xp fluid is wrong someway since the filters do not work for that. |
I’m using laser nodes to transfer items and fluids to an importer or a ME Interface, I’m not sure which one. Maybe the way I’m using the laser nodes changes something, but I’m not sure. |
Alright, got it. I can’t check right now, but I’ll look into it later. Maybe when I farmed XP, it was still on the version where XP came from the Mob Grinding Utils mod, and after an update, everything changed. That’s really not cool. |
So, the thing is, I didn’t update to the latest version because the latest one is 1.22, and I’m still on 1.20 with NeoForge on the CurseForge launcher. |
I just tried using curseforge instead with v1.20 and it is still shows as being just dire things. So the launcher is probably a red herring. For me, JEI shows no way of creating reliquary reincarnations experience, only that it can be used by the various botting machines. |
Alright, I got it. I tested in single-player, and there, the XP comes from Just Dire Things. But when I’m on my server, the XP is from Reliquary Reincarnation. So, I think the developers forgot to either update the server files or adjust the modpack locally to make them match. I don’t think it’s normal for the single-player and multiplayer versions to be different. |
I've been getting JDT xp from the xp bee all along. (I think maybe it was bottle enchanting in the very first couple alpha builds) I put a storage bus on the JDT xp holder so ae2 sticks it straight in there, its worked from right back when the pack was in very early days.. so maybe try that. |
Possible Fixes
Yes
Modpack Version
1.20
What happened?
A heated Centrifuge converts Experience Comb Blocks into xp fluid (just dire things). This can be piped out of the centrifuge and into an experience holder directly (just dire things).
If you import the xp fluid into an ae2 me system then it will fill up a fluid cell, but there is no way to export it. I have tried the various exporters, I have also tried moving the fluid cell into a me chest, but the xp fluid will not leave that either.
I can however use a bucket or a fluid tank to manually export from the me system by using the container on the stack of xp fluid in one of the crafting interfaces.
latest.log
No response
Developer reports
No response
The text was updated successfully, but these errors were encountered: