ThaumaticAugmentation makes error during JourneyMap render
jonassm opened this issue · 5 comments
Forge: 14.23.5
ThaumAug: 2.0.12
Minecraft: 1.12.2
When i try to automap with JourneyMap, it does not work, and looking at the logs, ThaumAug is causing this error during automap:
[13:03:25] [JM-task-4/ERROR] [journeymap]: Unexpected error during RunnableTask: java.lang.UnsupportedOperationException: Can't deserialize non-API implementation (or non-server implementations)
at thecodex6824.thaumicaugmentation.init.CapabilityHandler$6.readNBT(CapabilityHandler.java:213)
at thecodex6824.thaumicaugmentation.init.CapabilityHandler$6.readNBT(CapabilityHandler.java:208)
at net.minecraftforge.common.capabilities.Capability.readNBT(Capability.java:102)
at thecodex6824.thaumicaugmentation.common.capability.provider.SimpleCapabilityProvider.deserializeNBT(SimpleCapabilityProvider.java:43)
at thecodex6824.thaumicaugmentation.common.capability.provider.SimpleCapabilityProvider.deserializeNBT(SimpleCapabilityProvider.java:31)
at net.minecraftforge.common.capabilities.CapabilityDispatcher.deserializeNBT(CapabilityDispatcher.java:135)
at net.minecraft.world.chunk.storage.AnvilChunkLoader.func_75823_a(AnvilChunkLoader.java:472)
at net.minecraft.world.chunk.storage.AnvilChunkLoader.checkedReadChunkFromNBT__Async(AnvilChunkLoader.java:129)
at net.minecraft.world.chunk.storage.AnvilChunkLoader.loadChunk__Async(AnvilChunkLoader.java:93)
at net.minecraft.world.chunk.storage.AnvilChunkLoader.func_75815_a(AnvilChunkLoader.java:61)
at journeymap.client.io.nbt.ChunkLoader.getChunkMD(ChunkLoader.java:39)
at journeymap.client.task.multi.MapRegionTask.performTask(MapRegionTask.java:105)
at journeymap.client.thread.RunnableTask$Inner.run(RunnableTask.java:78)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
OS: Windows 10
Java: version 1.8.0_51, vendor Oracle Corporation
JVM: Java HotSpot(TM) 64-Bit Server VM (25.51-b03, mixed mode)
Minecraft: 1.12.2 (latest for 1.12)
Minecraft Launcher: 2.2.2529
forge-14.23.5.2854 (latest is forge-14.23.5.2855)
[email protected]
Modpack: MC Eternal 1.4.4 (latest)
ThaumicAugmentation-1.12.2-2.0.13 from Dec 25, 2020 (latest)
journeymap-1.12.2-5.7.1 from Mar 29, 2020 (latest for 1.12.2)
Exception (The same as above):
[11:20:44] [Client thread/INFO]: [CHAT] §eJourneyMap:§f Press [§bJ§f]
[11:20:44] [Client thread/INFO]: JourneyMap: Press [J]
[11:20:48] [Server thread/INFO]: Saving and pausing game...
[11:20:48] [Server thread/INFO]: Saving chunks for level 'New World'/overworld
[11:20:54] [Server thread/INFO]: Saving and pausing game...
[11:20:54] [Server thread/INFO]: Saving chunks for level 'New World'/overworld
[11:21:00] [Client thread/INFO]: Loaded 0 waypoints from ...\journeymap\data\sp\New World\waypoints
[11:21:02] [Server thread/INFO]: Saving and pausing game...
[11:21:02] [Server thread/INFO]: Saving chunks for level 'New World'/overworld
[00:32:37] [JM-task-7/ERROR]: Unexpected error during RunnableTask: java.lang.UnsupportedOperationException: Can't deserialize non-API implementation (or non-server implementations)
at thecodex6824.thaumicaugmentation.init.CapabilityHandler$6.readNBT(CapabilityHandler.java:213)
at thecodex6824.thaumicaugmentation.init.CapabilityHandler$6.readNBT(CapabilityHandler.java:208)
at net.minecraftforge.common.capabilities.Capability.readNBT(Capability.java:102)
at thecodex6824.thaumicaugmentation.common.capability.provider.SimpleCapabilityProvider.deserializeNBT(SimpleCapabilityProvider.java:43)
at thecodex6824.thaumicaugmentation.common.capability.provider.SimpleCapabilityProvider.deserializeNBT(SimpleCapabilityProvider.java:31)
at net.minecraftforge.common.capabilities.CapabilityDispatcher.deserializeNBT(CapabilityDispatcher.java:135)
at net.minecraft.world.chunk.storage.AnvilChunkLoader.func_75823_a(AnvilChunkLoader.java:472)
at net.minecraft.world.chunk.storage.AnvilChunkLoader.checkedReadChunkFromNBT__Async(AnvilChunkLoader.java:129)
at net.minecraft.world.chunk.storage.AnvilChunkLoader.loadChunk__Async(AnvilChunkLoader.java:93)
at net.minecraft.world.chunk.storage.AnvilChunkLoader.func_75815_a(AnvilChunkLoader.java:61)
at journeymap.client.io.nbt.ChunkLoader.getChunkMD(ChunkLoader.java:39)
at journeymap.client.task.multi.MapRegionTask.performTask(MapRegionTask.java:105)
at journeymap.client.thread.RunnableTask$Inner.run(RunnableTask.java:78)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
[11:21:16] [Client thread/INFO]: [CHAT] §eJourneyMap:§f Auto-mapping surface (100%).
[11:21:16] [Client thread/INFO]: JourneyMap: Auto-mapping surface (100%).
[11:21:17] [Client thread/INFO]: [CHAT] §eJourneyMap:§f Auto-mapping of surface has stopped.
[11:21:17] [Client thread/INFO]: JourneyMap: Auto-mapping of surface has stopped.
[11:22:09] [Server thread/INFO]: Saving and pausing game...
[11:22:09] [Server thread/INFO]: Saving chunks for level 'New World'/overworld
Just recreated with a brand new server and custom modpack only containing:
journeymap-1.12.2-5.7.1.jar
Thaumcraft-1.12.2-6.1.BETA26.jar
ThaumicAugmentation-1.12.2-2.0.13.jar
Only modpack load errors I saw near the beginning are texture errors in domains minecraft and thaumcraft.
I don't see current release or tag. Found commit 0c2f201 where 2.0.13 was updated in gradle.properties.
Saw some changes on the experimental branch. Tried compiling myself.
Used commit 47d6235a318b0073d37eb57b0f9d4dbce375c60b from May 26 2021.
Produced ThaumicAugmentation-1.12.2-2.1.0 and Journeymap seems to complete its auto-mapping successfully now!
I see log messages like this, where some did not appear before:
[15:10:44] [JM-task-4/INFO]: Potential chunks to map in RegionCoord [1,-1]: 24 of 1024
[15:10:44] [JM-task-4/INFO]: Actual chunks mapped in RegionCoord [1,-1]: 24
[15:10:44] [JM-task-4/INFO]: Memory usage at 8%
[15:10:44] [Client thread/INFO]: [CHAT] §eJourneyMap:§f Auto-mapping surface (90.9%).
[15:10:44] [Client thread/INFO]: JourneyMap: Auto-mapping surface (90.9%).
[15:10:45] [JM-task-4/INFO]: Potential chunks to map in RegionCoord [1,1]: 1 of 1024
[15:10:45] [JM-task-4/INFO]: Actual chunks mapped in RegionCoord [1,1]: 1
[15:10:45] [JM-task-4/INFO]: Memory usage at 8%
[15:10:45] [Client thread/INFO]: [CHAT] §eJourneyMap:§f Auto-mapping surface (100%).
[15:10:45] [Client thread/INFO]: JourneyMap: Auto-mapping surface (100%).
[15:10:46] [Client thread/INFO]: [CHAT] §eJourneyMap:§f Auto-mapping of surface has stopped.
[15:10:46] [Client thread/INFO]: JourneyMap: Auto-mapping of surface has stopped.
Had some build troubles and didn't see any instructions in the README. Used a command from a post like this one: env GRADLE_OPTS="-Dfile.encoding=utf-8" ./gradlew build.
The errors mentioned unmappable character for encoding Cp1252 and unterminated string literals, probably because of that earlier error, concerning the file src/main/java/thecodex6824/thaumicaugmentation/common/util/maze/Maze.java which was 1 of the 5 apart from the 100s of files in the project already set to UTF-8 encoding. I wonder if my Atom editor did that automatically when earlier viewing the file..
All the others dealing with the properties or gradle file were not working, but this one did.
I forgot to tag this issue in the commit but building should now work better for you - I removed the problematic characters from the maze file and tried to specify the encoding as explicitly UTF-8.
