There are certain compatibility issues between c2me and carpet
TheWhiteDog9487 opened this issue ยท 1 comments
Describe the bug
When I use c2me-fabric-mc1.20.4-0.2.0+alpha.11.52 or higher, I found that the fake player summoned by the carpet mod (using the /player ID spawn ) is not rendered and cannot be interacted with, but It can be selected by the target selector of the command, and the player list opened by the Tab key also shows the existence of this summoned fake player.
To Reproduce
- Install Minecraft 1.20.4 + Fabric Loader 0.15.7
- Install fabric-carpet-1.20.3-1.4.128+v231205
- Install c2me-fabric-mc1.20.4-0.2.0+alpha.11.52
- Create and enter a world
- Use
/player Alex spawn
Expected behavior
Like the 11.50 version of c2me, fake players are rendered and can interact
Screenshots
Runtime info (please complete the following information):
- OS: Microsoft Windows 11 Pro for Workstation
- Minecraft version: 1.20.4
- Mod version: 1.20.4-0.2.0+alpha.11.58
- Mod branch: (fill this if you are not using the default
ver
branches)
Crash reports / logs
- Not a crash, but I found that c2me threw an exception when the problem occurred
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: java.util.ConcurrentModificationException: Async entity load
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: at net.minecraft.class_3898.handler$zzp000$c2me-fixes-general-threading-issues$preventAsyncEntityLoad(class_3898.java:4407)
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: at net.minecraft.class_3898.method_18701(class_3898.java)
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: at net.minecraft.class_3215.method_18755(class_3215.java:481)
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: at net.minecraft.class_3218$class_5526.method_31436(class_3218.java:1585)
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: at net.minecraft.class_3218$class_5526.method_31798(class_3218.java:1563)
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: at net.minecraft.class_5579.method_31847(class_5579.java:216)
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: at net.minecraft.class_5579.method_31820(class_5579.java:186)
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: at net.minecraft.class_5579.method_31818(class_5579.java:167)
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: at net.minecraft.class_3218.method_18771(class_3218.java:924)
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: at net.minecraft.class_3218.method_18213(class_3218.java:910)
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: at net.minecraft.class_3324.method_14570(class_3324.java:238)
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: at carpet.patches.EntityPlayerMPFake.lambda$createFake$2(EntityPlayerMPFake.java:76)
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: at java.base/java.util.concurrent.CompletableFuture$UniAccept.tryFire(CompletableFuture.java:718)
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: at java.base/java.util.concurrent.CompletableFuture.postFire(CompletableFuture.java:614)
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:653)
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: at java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:483)
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373)
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182)
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655)
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622)
[17:47:17] [Worker-Main-1/INFO]: [STDERR]: at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165)
Other mods
fabric-carpet-1.20.3-1.4.128+v231205
there is none left
Checklist
- I am using the official version of the mod.
- I tried the latest development version but the issue persists.
- I searched for similar open issues and could not find an existing bug report on this.
Additional context
Duplicate of #272