MehVahdJukaar / sleep_tight

Other
1 stars 9 forks source link

cannot lie on beds #45

Open An-thracene opened 10 months ago

An-thracene commented 10 months ago

latest.log The only few things I know are:

1、 This bug is caused by a mod conflict, and one of them is Sleep Tight. Removing it can completely solve this problem.

2、 This bug is triggered randomly, which makes it difficult to troubleshoot.

3、 It seems that the game thinks the player is already on the bed, while the player actually not

The video is here to provide more information Minecraft_ 1.20.1 2023-10-25 22-31-57.zip

MehVahdJukaar commented 10 months ago

only way to fix this for me is if the culprit mod is found. Even then im not sure if much can be done

MehVahdJukaar commented 10 months ago

weir dthat it resets itself after some tries. its related to the occupied blockstate property of beds. that usually is only set and reset when laying down and waking up

An-thracene commented 10 months ago

only way to fix this for me is if the culprit mod is found. Even then im not sure if much can be done

But as I said, it's difficult to troubleshoot because the bug is triggered randomly. More strangely, the fewer mods I add, the less frequently bug occurs. You can see the log when I add fewer mods:

latest.log

Obviously, the times "[Render thread/WARN]: Received passengers for unknown entity" appears is fewer, with a lower frequency as well

SettingDust commented 10 months ago

What cloud be the reason of this issue? I'm running into this. It's not randomly. But is conflicting with random mod. When right click bed, player will lie on bed about 1 tick. The player is on bed on server. I can't interact doors out of range. And when I switch mode to spectator or rejoin world, I will be "tp" to the bed.

EDIT: Seems conflicting with my mod https://modrinth.com/mod/respawn-complex I don't quite know the reason. M

EDIT1: And I can't import sleep tight for testing in dev env

java.lang.RuntimeException: Could not execute entrypoint stage 'client' due to errors, provided by 'moonlight'!
    at net.fabricmc.loader.impl.entrypoint.EntrypointUtils.lambda$invoke0$0(EntrypointUtils.java:51)
    at net.fabricmc.loader.impl.util.ExceptionUtil.gatherExceptions(ExceptionUtil.java:33)
    at net.fabricmc.loader.impl.entrypoint.EntrypointUtils.invoke0(EntrypointUtils.java:49)
    at net.fabricmc.loader.impl.entrypoint.EntrypointUtils.invoke(EntrypointUtils.java:35)
    at net.fabricmc.loader.impl.game.minecraft.Hooks.startClient(Hooks.java:53)
    at net.minecraft.client.Minecraft.<init>(Minecraft.java:458)
    at net.minecraft.client.main.Main.main(Main.java:211)
    at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:468)
    at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:74)
    at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)
    at net.fabricmc.devlaunchinjector.Main.main(Main.java:86)
    at dev.architectury.transformer.TransformerRuntime.main(TransformerRuntime.java:219)
Caused by: java.lang.AssertionError: Method has to be called during mod initialization phase
    at net.mehvahdjukaar.moonlight.core.Moonlight.assertInitPhase(Moonlight.java:101)
    at net.mehvahdjukaar.moonlight.api.platform.fabric.ClientHelperImpl.addModelLayerRegistration(ClientHelperImpl.java:162)
    at net.mehvahdjukaar.moonlight.api.platform.ClientHelper.addModelLayerRegistration(ClientHelper.java)
    at net.mehvahdjukaar.sleep_tight.SleepTightClient.init(SleepTightClient.java:40)
    at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
    at net.mehvahdjukaar.moonlight.fabric.MoonlightFabricClient.onInitializeClient(MoonlightFabricClient.java:14)
    at net.fabricmc.loader.impl.entrypoint.EntrypointUtils.invoke0(EntrypointUtils.java:47)
    ... 9 more