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
Describe the bug
When setting the blockType in the generator to a block from Oraxena, an error is displayed in the console:
java.util.ConcurrentModificationException: null
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:1013) ~[?:?]
at java.util.ArrayList$Itr.next(ArrayList.java:967) ~[?:?]
at xyz.arcadiadevs.gensplus.tasks.CleanupTask.run(:29) ~[GensPlus.jar:?]
at org.bukkit.craftbukkit.v1_20_R1.scheduler.CraftTask.run(CraftTask.java:101) ~[purpur-1.20.1.jar:git-Purpur-2062]
at org.bukkit.craftbukkit.v1_20_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:57) ~[purpur-1.20.1.jar:git-Purpur-2062]
at com.destroystokyo.paper.ServerSchedulerReportingWrapper.run(ServerSchedulerReportingWrapper.java:22) ~[purpur-1.20.1.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
at java.lang.Thread.run(Thread.java:840) ~[?:?]
and the generator does not work and is not included in the number of generators after place it.
Screenshots
It looks normal in the gui.
In inventory, the only thing that changes is the type from the oraxen config to the name "oraxen:NAME"
And when placed, it behaves like a regular oraxen block, not like a generator.
Additional info:
Spigot Version: Purpur-2062
Using ViaVersion/ProtocolSupport: no
Your MC version: 1.20.1
The text was updated successfully, but these errors were encountered:
Describe the bug
When setting the blockType in the generator to a block from Oraxena, an error is displayed in the console:
and the generator does not work and is not included in the number of generators after place it.
Generator config:
Screenshots
It looks normal in the gui.
In inventory, the only thing that changes is the type from the oraxen config to the name "oraxen:NAME"
And when placed, it behaves like a regular oraxen block, not like a generator.
Additional info:
The text was updated successfully, but these errors were encountered: