You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hiya struggling to get the Apiary to work with the Neutronium bee tried all the combination for it that is included in the JEI - and from my own understanding.
It is also not locked by the energy since I am using 2 16A UV energy hatches, multiblock has formed perfectly fine as well. I thought the problem could have been shared input/output hatches but even using a completely isolated Apiary doesn't make a difference.
latest.log
No response
Developer reports
No response
The text was updated successfully, but these errors were encountered:
I cannot replicate this on a fresh install of ATM9 v0.3.5, perhaps something went awry with an update?
There may be several ways to rectify this, but what I would do is try deleting and then copying over a fresh install's kubejs, config, defaultconfigs, and packmenu folders into your current instance. You could also try copying over the old instance's /saves/ folder into a new install of ATM9.
If all else fails, you could try using a nametag to name the bees specifically to "Not a Neutronium Bee"
Possible Fixes
Yes
Modpack Version
Latest
What happened?
Hiya struggling to get the Apiary to work with the Neutronium bee tried all the combination for it that is included in the JEI - and from my own understanding.
It is also not locked by the energy since I am using 2 16A UV energy hatches, multiblock has formed perfectly fine as well. I thought the problem could have been shared input/output hatches but even using a completely isolated Apiary doesn't make a difference.
latest.log
No response
Developer reports
No response
The text was updated successfully, but these errors were encountered: