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
I've been working on a modpack for me and my friends to play with and recently added REI. Ever since I added it I've been having issues because REI can't fully initialize and gets stuck at Step 5/6 (76%). Does anyone know what may be causing it to get stuck?
What mod loaders are you seeing the problem on?
Forge
What do you think this bug is of?
Visual
Recipe Lookup
Cheat Mode
Plugin Integration / JEI Plugin Compatibility
Others
Relevant log output
[17:55:43] [REI-ReloadPlugins/ERROR] [REI] DefaultClientPluginImpl of DefaultClientPluginImpl [roughlyenoughitems] plugin failed to reloadable-plugin/DisplayRegistryImpl/!
java.lang.NullPointerException: Cannot invoke "net.minecraft.world.item.crafting.Ingredient.m_43947_()" because "ingredient" is null
at TRANSFORMER/roughlyenoughitems@8.4.723/me.shedaniel.rei.api.common.util.EntryIngredients.ofIngredient(EntryIngredients.java:111)
at TRANSFORMER/roughlyenoughitems@8.4.723/me.shedaniel.rei.plugin.client.DefaultClientPlugin.registerDisplays(DefaultClientPlugin.java:368)
at TRANSFORMER/roughlyenoughitems@8.4.723/me.shedaniel.rei.impl.client.registry.display.DisplayRegistryImpl.acceptPlugin(DisplayRegistryImpl.java:64)
at TRANSFORMER/roughlyenoughitems@8.4.723/me.shedaniel.rei.impl.client.registry.display.DisplayRegistryImpl.acceptPlugin(DisplayRegistryImpl.java:50)
at TRANSFORMER/roughlyenoughitems@8.4.723/me.shedaniel.rei.api.common.registry.Reloadable.acceptPlugin(Reloadable.java:78)
at TRANSFORMER/roughlyenoughitems@8.4.723/me.shedaniel.rei.impl.common.plugins.PluginManagerImpl.lambda$startReload$9(PluginManagerImpl.java:417)
at TRANSFORMER/roughlyenoughitems@8.4.723/me.shedaniel.rei.impl.common.plugins.PluginManagerImpl.lambda$pluginSection$4(PluginManagerImpl.java:199)
at TRANSFORMER/roughlyenoughitems@8.4.723/me.shedaniel.rei.impl.common.plugins.PluginManagerImpl.lambda$startReload$10(PluginManagerImpl.java:407)
at TRANSFORMER/roughlyenoughitems@8.4.723/me.shedaniel.rei.impl.common.plugins.PluginManagerImpl.pluginSection(PluginManagerImpl.java:197)
at TRANSFORMER/roughlyenoughitems@8.4.723/me.shedaniel.rei.impl.common.plugins.PluginManagerImpl.startReload(PluginManagerImpl.java:405)
at TRANSFORMER/roughlyenoughitems@8.4.723/me.shedaniel.rei.RoughlyEnoughItemsCore._reloadPlugins(RoughlyEnoughItemsCore.java:162)
at TRANSFORMER/roughlyenoughitems@8.4.723/me.shedaniel.rei.RoughlyEnoughItemsCoreClient.lambda$reloadPlugins$24(RoughlyEnoughItemsCoreClient.java:488)
at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)
What happened?
I've been working on a modpack for me and my friends to play with and recently added REI. Ever since I added it I've been having issues because REI can't fully initialize and gets stuck at Step 5/6 (76%). Does anyone know what may be causing it to get stuck?
What mod loaders are you seeing the problem on?
Forge
What do you think this bug is of?
Relevant log output
Anything else?
https://legacy.curseforge.com/minecraft/modpacks/burtbobs-more-minecraft
This is the modpack. It has a full list of mods being used in the description.
By submitting this issue, I have included the necessary logs by pasting the contents into the correct location or attaching the file as an upload.
By submitting this issue, I have confirmed my REI and REI's dependencies are up to date.
The text was updated successfully, but these errors were encountered: