Jump to content

[net.minecraft.server.network.ServerLoginPacketListenerImpl/]: Couldn't place player in world


Recommended Posts

Posted

I own a server which I use to host modded minecraft servers on, and for about a year, I've had no issues whatsoever, but about a week ago, whenever I try to join any server I load, the logs say that they can't find anywhere to place someone in the world and..Well, I don't know, the server itself runs perfectly from what I know, but no one can log in. I can't find anything about this issue, which is most definitely fault. We primarily play on 1.18.2 forge, with a bunch of mods

This is the..at least what I think is the relevant part of the log..

 

```
[17Nov2023 21:14:06.020] [Server thread/INFO] [net.minecraftforge.common.AdvancementLoadFix/]: Using new advancement loading for net.minecraft.server.PlayerAdvancements@4d1d2643
[17Nov2023 21:14:06.042] [Server thread/INFO] [net.minecraft.server.players.PlayerList/]: StefanVenkov12[/*************] logged in with entity id 407 at (204.5, 63.0, -266.5)
[17Nov2023 21:14:06.132] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer/]: StefanVenkov12 joined the game
[17Nov2023 21:14:06.302] [Netty Server IO #1/INFO] [immersiveengineering/]: Recipes for potions: alexsmobs:soulsteal, minecraft:strong_healing, alexsmobs:long_clinging, minecraft:strength, minecraft:harming, alexsmobs:long_lava_vision, minecraft:strong_slowness, minecraft:slow_falling, epicfight:blooming, apotheosis:long_absorption, apotheosis:strong_resistance, apotheosis:long_wither, apotheosis:strong_wither, alexsmobs:bug_pheromones, minecraft:long_swiftness, apotheosis:long_haste, minecraft:strong_regeneration, minecraft:long_water_breathing, apotheosis:wither, minecraft:long_invisibility, apotheosis:strong_sundering, minecraft:strong_harming, minecraft:water_breathing, minecraft:poison, minecraft:strong_poison, alexsmobs:long_poison_resistance, alexsmobs:knockback_resistance, alexsmobs:speed_iii, minecraft:slowness, minecraft:healing, minecraft:turtle_master, minecraft:long_poison, alexsmobs:long_bug_pheromones, apotheosis:long_resistance, apotheosis:long_fatigue, minecraft:fire_resistance, minecraft:long_regeneration, apotheosis:strong_absorption, minecraft:water, apotheosis:fatigue, apotheosis:resistance, minecraft:swiftness, apotheosis:long_knowledge, alexsmobs:lava_vision, apotheosis:long_sundering, minecraft:strong_turtle_master, alexsmobs:long_knockback_resistance, apotheosis:strong_fatigue, alexsmobs:clinging, alexsmobs:long_soulsteal, minecraft:long_turtle_master, minecraft:regeneration, minecraft:weakness, minecraft:long_slow_falling, minecraft:long_leaping, minecraft:invisibility, minecraft:long_slowness, minecraft:long_fire_resistance, apotheosis:sundering, alexsmobs:poison_resistance, minecraft:awkward, minecraft:strong_leaping, alexsmobs:strong_soulsteal, minecraft:strong_strength, apotheosis:strong_knowledge, minecraft:luck, minecraft:long_weakness, minecraft:leaping, minecraft:long_strength, minecraft:night_vision, apotheosis:absorption, apotheosis:haste, minecraft:long_night_vision, apotheosis:strong_haste, minecraft:strong_swiftness, apotheosis:knowledge, alexsmobs:strong_knockback_resistance
[17Nov2023 21:14:06.430] [Server thread/INFO] [Waila/]: Syncing config to StefanVenkov12 (6ce4e6ab-cf81-4815-977a-3fbdde27270c)
[17Nov2023 21:14:06.538] [Server thread/ERROR] [net.minecraft.server.network.ServerLoginPacketListenerImpl/]: Couldn't place player in world
java.lang.ClassCastException: class yesman.epicfight.data.loot.function.SetSkillFunction cannot be cast to class net.minecraft.world.level.storage.loot.functions.SetNbtFunction (yesman.epicfight.data.loot.function.SetSkillFunction is in module epicfight@18.5.17 of loader 'TRANSFORMER' @22a4ca4a; net.minecraft.world.level.storage.loot.functions.SetNbtFunction is in module minecraft@1.18.2 of loader 'TRANSFORMER' @22a4ca4a)
    at net.minecraft.world.level.storage.loot.functions.SetNbtFunction$Serializer.m_6170_(SetNbtFunction.java:42) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at net.minecraft.world.level.storage.loot.GsonAdapterFactory$JsonAdapter.serialize(GsonAdapterFactory.java:125) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at com.google.gson.internal.bind.TreeTypeAdapter.write(TreeTypeAdapter.java:81) ~[gson-2.8.9.jar%2321!/:?]
    at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:69) ~[gson-2.8.9.jar%2321!/:?]
    at com.google.gson.internal.bind.ArrayTypeAdapter.write(ArrayTypeAdapter.java:95) ~[gson-2.8.9.jar%2321!/:?]
    at com.google.gson.Gson.toJson(Gson.java:735) ~[gson-2.8.9.jar%2321!/:?]
    at com.google.gson.Gson.toJsonTree(Gson.java:628) ~[gson-2.8.9.jar%2321!/:?]
    at com.google.gson.Gson.toJsonTree(Gson.java:607) ~[gson-2.8.9.jar%2321!/:?]
    at com.google.gson.internal.bind.TreeTypeAdapter$GsonContextImpl.serialize(TreeTypeAdapter.java:155) ~[gson-2.8.9.jar%2321!/:?]
    at net.minecraft.world.level.storage.loot.entries.LootPoolSingletonContainer$Serializer.m_7219_(LootPoolSingletonContainer.java:141) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at net.minecraft.world.level.storage.loot.entries.LootItem$Serializer.m_7219_(LootItem.java:43) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at net.minecraft.world.level.storage.loot.entries.LootItem$Serializer.m_7219_(LootItem.java:40) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at net.minecraft.world.level.storage.loot.entries.LootPoolEntryContainer$Serializer.m_6170_(LootPoolEntryContainer.java:80) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at net.minecraft.world.level.storage.loot.entries.LootPoolEntryContainer$Serializer.m_6170_(LootPoolEntryContainer.java:74) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at net.minecraft.world.level.storage.loot.GsonAdapterFactory$JsonAdapter.serialize(GsonAdapterFactory.java:125) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at com.google.gson.internal.bind.TreeTypeAdapter.write(TreeTypeAdapter.java:81) ~[gson-2.8.9.jar%2321!/:?]
    at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:69) ~[gson-2.8.9.jar%2321!/:?]
    at com.google.gson.internal.bind.ArrayTypeAdapter.write(ArrayTypeAdapter.java:95) ~[gson-2.8.9.jar%2321!/:?]
    at com.google.gson.Gson.toJson(Gson.java:735) ~[gson-2.8.9.jar%2321!/:?]
    at com.google.gson.Gson.toJsonTree(Gson.java:628) ~[gson-2.8.9.jar%2321!/:?]
    at com.google.gson.Gson.toJsonTree(Gson.java:607) ~[gson-2.8.9.jar%2321!/:?]
    at com.google.gson.internal.bind.TreeTypeAdapter$GsonContextImpl.serialize(TreeTypeAdapter.java:155) ~[gson-2.8.9.jar%2321!/:?]
    at net.minecraft.world.level.storage.loot.LootPool$Serializer.serialize(LootPool.java:204) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at net.minecraft.world.level.storage.loot.LootPool$Serializer.serialize(LootPool.java:187) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at com.google.gson.internal.bind.TreeTypeAdapter.write(TreeTypeAdapter.java:81) ~[gson-2.8.9.jar%2321!/:?]
    at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:69) ~[gson-2.8.9.jar%2321!/:?]
    at com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.write(CollectionTypeAdapterFactory.java:97) ~[gson-2.8.9.jar%2321!/:?]
    at com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.write(CollectionTypeAdapterFactory.java:61) ~[gson-2.8.9.jar%2321!/:?]
    at com.google.gson.Gson.toJson(Gson.java:735) ~[gson-2.8.9.jar%2321!/:?]
    at com.google.gson.Gson.toJsonTree(Gson.java:628) ~[gson-2.8.9.jar%2321!/:?]
    at com.google.gson.Gson.toJsonTree(Gson.java:607) ~[gson-2.8.9.jar%2321!/:?]
    at com.google.gson.internal.bind.TreeTypeAdapter$GsonContextImpl.serialize(TreeTypeAdapter.java:155) ~[gson-2.8.9.jar%2321!/:?]
    at net.minecraft.world.level.storage.loot.LootTable$Serializer.serialize(LootTable.java:278) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at net.minecraft.world.level.storage.loot.LootTable$Serializer.serialize(LootTable.java:252) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at com.google.gson.internal.bind.TreeTypeAdapter.write(TreeTypeAdapter.java:81) ~[gson-2.8.9.jar%2321!/:?]
    at com.google.gson.Gson.toJson(Gson.java:735) ~[gson-2.8.9.jar%2321!/:?]
    at com.google.gson.Gson.toJsonTree(Gson.java:628) ~[gson-2.8.9.jar%2321!/:?]
    at com.google.gson.Gson.toJsonTree(Gson.java:607) ~[gson-2.8.9.jar%2321!/:?]
    at uk.me.desert_island.rer.RoughlyEnoughResources.sendLootToPlayers(RoughlyEnoughResources.java:53) ~[rer-2.5.2.jar%23104!/:?]
    at net.minecraft.server.players.PlayerList.handler$zzp000$onPlayerConnect(PlayerList.java:910) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at net.minecraft.server.players.PlayerList.m_11261_(PlayerList.java:239) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at net.minecraft.server.network.ServerLoginPacketListenerImpl.m_143699_(ServerLoginPacketListenerImpl.java:138) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at net.minecraft.server.network.ServerLoginPacketListenerImpl.m_10055_(ServerLoginPacketListenerImpl.java:125) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at net.minecraft.server.network.ServerLoginPacketListenerImpl.m_10050_(ServerLoginPacketListenerImpl.java:69) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at net.minecraft.network.Connection.m_129483_(Connection.java:241) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at net.minecraft.server.network.ServerConnectionListener.m_9721_(ServerConnectionListener.java:143) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at net.minecraft.server.MinecraftServer.m_5703_(MinecraftServer.java:916) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at net.minecraft.server.dedicated.DedicatedServer.m_5703_(DedicatedServer.java:326) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at net.minecraft.server.MinecraftServer.m_5705_(MinecraftServer.java:842) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at net.minecraft.server.MinecraftServer.m_130011_(MinecraftServer.java:685) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at net.minecraft.server.MinecraftServer.m_177918_(MinecraftServer.java:261) ~[server-1.18.2-20220404.173914-srg.jar%23127!/:?]
    at java.lang.Thread.run(Thread.java:1623) [?:?]
[17Nov2023 21:14:07.223] [Server thread/INFO] [net.minecraft.server.network.ServerGamePacketListenerImpl/]: StefanVenkov12 lost connection: Invalid player data
[17Nov2023 21:14:07.224] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer/]: StefanVenkov12 left the game
[17Nov2023 21:14:07.233] [Server thread/INFO] [voicechat/]: [voicechat] Disconnecting client StefanVenkov12

```

I'm sorry if I'm being an idiot, but if someone knows what I need to do, that'd be really helpful!

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • I fight fires for a living, it's in my blood as a volunteer firefighter. But nothing could have prepared me for the fire that almost reduced my family's future to ashes. I had secretly accumulated $150,000 worth of Bitcoin over the years, intending to lock up my children's education and provide my wife with some leeway from our constant shift-work life. That was until a phishing attack struck me while I was out fighting a wildfire. The call had been on a hot afternoon. We were dashing to contain wildfires tearing across parched scrub lands. At such frantic moments, my phone pulsed with a security alert message from what looked like my Bitcoin wallet operator. Drenched with sweat, fatigue, and hyper adrenaline, I had clicked on the link and input my log-ins without questioning anything. I was tricked by hackers during my most vulnerable time. Hours later, returning to the station, I emptied my wallet. The harsh reality hit me with more force than any fire could ever have. My carefully saved safety net had vanished. My heart beat faster than the sirens. I felt as though I had failed my family. I explained my terror of burgers at our favorite local diner that evening to my friend. He leaned in close and whispered a single word: Hackerzed Nemesis Recovery. He swore by their effectiveness, stating they worked miracles when his cousin had crypto stolen from him in a scam. I was skeptical old-school and desperate, so I called them. From the first call, their team treated me like family. They didn't only view figures; they viewed a husband and a father attempting to rectify a horrific error. They labored day and night, following stolen money through blockchain transactions like l detectives. Progress was made every day, translating intricate tech into fireman-speak. Ten days later, I got the call. “We recovered your Bitcoin.” I cried. Right there in the station, surrounded by smoke-stained gear, I let it all out. Relief. Gratitude. Hope they don't stop there. Knowing I worked in emergency services, Hackerzed Nemesis Recovery offered to run an online security workshop for my entire fire department. They turned my disaster into a lesson that safeguarded my team. These folks don’t just recover wallets; they rebuild lives. They rebuilt mine. I fight fires for a living, it's in my blood as a volunteer firefighter. But nothing could have prepared me for the fire that almost reduced my family's future to ashes. I had secretly accumulated $150,000 worth of Bitcoin over the years, intending to lock up my children's education and provide my wife with some leeway from our constant shift-work life. That was until a phishing attack struck me while I was out fighting a wildfire. The call had been on a hot afternoon. We were dashing to contain wildfires tearing across parched scrub lands. At such frantic moments, my phone pulsed with a security alert message from what looked like my Bitcoin wallet operator. Drenched with sweat, fatigue, and hyper adrenaline, I had clicked on the link and input my log-ins without questioning anything. I was tricked by hackers during my most vulnerable time. Hours later, returning to the station, I emptied my wallet. The harsh reality hit me with more force than any fire could ever have. My carefully saved safety net had vanished. My heart beat faster than the sirens. I felt as though I had failed my family. I explained my terror of burgers at our favorite local diner that evening to my friend. He leaned in close and whispered a single word: Hackerzed Nemesis Recovery. He swore by their effectiveness, stating they worked miracles when his cousin had crypto stolen from him in a scam. I was skeptical old-school and desperate, so I called them. From the first call, their team treated me like family. They didn't only view figures; they viewed a husband and a father attempting to rectify a horrific error. They labored day and night, following stolen money through blockchain transactions like l detectives. Progress was made every day, translating intricate tech into fireman-speak. Ten days later, I got the call. “We recovered your Bitcoin.” I cried. Right there in the station, surrounded by smoke-stained gear, I let it all out. Relief. Gratitude. Hope they don't stop there. Knowing I worked in emergency services, Hackerzed Nemesis Recovery offered to run an online security workshop for my entire fire department. They turned my disaster into a lesson that safeguarded my team. These folks don’t just recover wallets; they rebuild lives. They rebuilt mine. Contact : What    s    App: +      1, 6,3        ,9 3,        9,5   4,6,        2,8 Mail:         hackerzednemesis001               (@)            zohomail           (.)     com Website  :          https:        //hackerzednemesis      (.)                 com info               (@)         hackerzednemesis          (.)                    com
    • Can you upload full latest.log somewhere? Perhaps some interesting errors are reported just before the crash happens
    • It now starts but when i try making or joining a new world it crashes and the log says the same errors as before.  
    • Those other mods will need to be downgraded as well then - down to the version in which they supported Create 5. Or you will have to drop the plugins incompatible with Create 6. I know it stings, but you can't have it both ways ¯\_(ツ)_/¯
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.