#(hsadol) Geyser connected issue: Haven't received PlayerListEntry packet before spawning player!

77 messages · Page 1 of 1 (latest)

radiant geyser
#

Hello, I'm receiving these errors frequently:

[23:29:39 ERROR] [geyser]: Haven't received PlayerListEntry packet before spawning player! We ignore the player a0511996-8caa-258b-ad9a-654cf24eb466
[23:29:39 ERROR] [geyser]: Haven't received PlayerListEntry packet before spawning player! We ignore the player b810b8ef-3097-2a1e-99b4-cc89b7c1baef
...

Now let's take look, I have two NPCs with UUIDs:

    uuid: a0511996-8caa-458b-ad9a-654cf24eb466
    uuid: b810b8ef-3097-4a1e-99b4-cc89b7c1baef

As you can see, number 4 in the third group of uuid chars is always changed for number 2 in Geyser for some reason, and that's causing errors when it like "updates" the NPCs, or when the new one is spawned, when I change the NPC name & skin, etc.

I run 1.21 Purpur & 3501 Citizens build

It's happening for all of the NPCs, even the newly created / updated ones

Note, it's not only Geyser issue, when you open client console log on Java, you can see these errors too, parrarel with the ones in Geyser console:

Server attempted to add player prior to sending player info (Player id 76f367b0-8298-268d-9cfa-0ccade5e4d5a)
Skipping Entity with id entity.minecraft.player

Geyser:
[23:47:33 ERROR] [geyser]: Haven't received PlayerListEntry packet before spawning player! We ignore the player 76f367b0-8298-268d-9cfa-0ccade5e4d5a
atomic scaffoldBOT
#

(hsadol) Geyser connected issue: Haven't received PlayerListEntry packet before spawning player!

atomic scaffoldBOT
#

Hi I'm AutoThreadBot! Don't mind me, I'll just be adding the helper team to this thread so they can see it. A human will get to you soon.

radiant geyser
#

Cannot the issue be solved by /npc playerlist | packet or by scoreboard teams settings ?

twilit grotto
#

Last few times I've tried to look at this geyser hasn't worked for me so I'll see

#

Was fixed for a while

radiant geyser
#

but it isn't only geyser issue

#

I asked on their Discord, and the only thing you need to do is enable logging in the Java Client Launcher and you can see the same error as is in the Geyser

#

This is the same error that is sent by the Java client. We send it in console because we emulate the Java client. If you play with the log open on a vanilla Java client, you will see the same error.

#
Server attempted to add player prior to sending player info (Player id 76f367b0-8298-268d-9cfa-0ccade5e4d5a)
Skipping Entity with id entity.minecraft.player

For me this happened when the NPC updated / spawned (created) or so

#

So to reproduce it you don't even need geyser setup, only the Java Client log is needed

radiant geyser
#

It can be turned in Settings -> Open output log when Minecraft: Java Edition starts

And then just walk around NPCs, maybe try to change skin / rename, or spawn the new one, and you'll see the:

Server attempted to add player prior to sending player info (Player id 76f367b0-8298-268d-9cfa-0ccade5e4d5a)
Skipping Entity with id entity.minecraft.player

error, where will be the 268d instead of 468d (with 4 it's in the citizens saves.yml)

And in case someone uses geyser, they see this error in their server console too when Bedrock players are nearby, similarly like the Java ones see this in their own console
But it's not related to Geyser, it can be reproduced even without it. Anyone can easily reproduce it, and prob all players are affected by it

radiant geyser
vagrant magnet
#

yeah got my NPCs at the spawn when someone joins the server or goes to the spawn i get the error message..

twilit grotto
radiant geyser
#

that's strange I'll test that again & try to provide exact steps

vagrant magnet
#

geyser sends me here - caus it are NPCs that are giving the error not real players

twilit grotto
#

hmm in that case is it necessary to fix?

#

this is a cosmetic "error" only

radiant geyser
radiant geyser
#

Wait, after deeper research, you need only CItizens to let it happen
just perform /citizens reload

#

but it happens when you walk over spawn as well, prob when npcs refetch or something?

OR it looks like that when NPC uses your skin

#

I created Test NPC named Test with my skin & it was triggered as well

#
[18:15:57 INFO]: Current Purpur Version: 1.21-2284-4e55e26 (MC: 1.21)*
* You are running the latest version
[18:16:04 INFO]: Citizens version 2.0.35-SNAPSHOT (build 3514)
[18:16:11 INFO]: Bukkit Plugins: (1):
[18:16:11 INFO]:  - Citizens
#

Steps to reproduce

  • Install clean installation of Citizens
  • Make NPC (random name, random skin)
  • Go further from the NPC (50-100 blocks or so)
  • Use /citizens reload, you'll see the error

This error is happening when you're further from NPC & join the game as well (happens only on first join after server restart)

#

yes, you need to be far from the NPC to see this error:
Server attempted to add player prior to sending player info (Player id 40f44b30-b870-26fa-9785-539f80edfdab)
Skipping Entity with id entity.minecraft.player

#

prob like 50-100 blocks far (then it happens on join as well, and this is prob the thing that's happening when players join spawn -> it sends them all the NPCs errors like these)

radiant geyser
# twilit grotto I don't get this message on my java client log

Written reproduction steps, only thing you need is to use the clean installation of citizens, spawn NPC whatever name, go far away, and you can do /citizens reload / relog there

Also stay afk for a while from NPC & you'll see the errors in your log like every 5 mins (prob when the refetch is done or so?)

twilit grotto
#

!rule 8

pure oliveBOT
# twilit grotto !rule 8
Rule 8

Don't overuse the edit/delete buttons. https://denizenscript.com/discord_rules#rule8
Use the edit button to fix typos, and the delete button to remove an accidental post shortly after posting.
Do not remove a post that pings someone, do not edit or delete a post that people have already replied to.

radiant geyser
#

Oh, ok, I'm sorry about this, I just wanted to delete the first initial wrong thoughts I made to simplify messages 😅 When there are now exact steps to reproduce

twilit grotto
#

yeah these steps don't work to reproduce it

#

so maybe I will just look into trying geyser again

radiant geyser
twilit grotto
#

No, I'm not trying on purpur

radiant geyser
#

I'll test paper now

#

yeah it's happeing even there

#

should I try clean server installation in case it is affected by something?

#

it seems to be related to something else as well... it doesn't happen always when I go to different direction, it happens only near spawn prob, I'm trying to discover what can affect it

primal troutBOT
radiant geyser
#

it seems to be affected by something in my spawn area then... it doesn't happen outside it
But the NPC is like 30 blocks behind the spawn, and when I go behind the spawn to any direction there's not this error

radiant geyser
#

even when I cut the whole spawn with entities it's still happening there

#

I don't understand it really, if you can test it on my dev server, there's only citizens & it's in the wild, it would be good, as we could see what's going on there

twilit grotto
#

no, I'm not going to join your dev server

radiant geyser
#

it happens even when I reset world, let me try reset the whole server & install only citizens

#

so even when I reinstall the whole server & install only citizens with default settings it's still happening when using /citizens reload even when I'm near NPCs

#

I'm on 1.21 btw

#

tried even with & without OP & even on 1.20 with viaversion & with the latest citizens build, I'm already out of ideas, i seems to be issue in the plugin, strange you can't reproduce it

twilit grotto
#

I just managed to get geyser working and it is happening on geyser

radiant geyser
#

oh at least, but I'm surprised it's not happening in the Java client for you

twilit grotto
#

I will try to suppress this message that does not affect anything but it may not be possible

#

in which case I will say; it is not reasonably possible to suppress this message that does not affect anything

radiant geyser
#

if there will be some way to do it, it would be nice, since many people report the issue still on geyser & here

Also other NPCs plugin have these issues as well? Not sure if I haven't read that someone switched into diff plugin & it solved, not sure if I should try it, then there maybe could be some solution for it

twilit grotto
#

it is difficult to suppress this message without flickering spawns or very invasive code into minecraft

twilit grotto
#

should be fixed in the new build

brittle oysterBOT
#
Thread Closing Reminder

Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.

If not yet resolved, please reply below to tell us what you still need.

(Note that if there is no reply for a few days, this thread will eventually close itself.)

#

@radiant geyser

radiant geyser
#

on MC client it's still happening, but we'll see on Geyser then

#

or do you think that even this is issue?

twilit grotto
#

I'm not getting anything like that on MC

twilit grotto
#

@vagrant magnet did the latest build fix it for you?

vagrant magnet
#

no still have the error and changing skin issues ... i gave up for now hihi just ignoring it ..

vagrant magnet
#

this are all my spawn NPC's so i just ignore it

twilit grotto
#

what about the new build 3535? @vagrant magnet @radiant geyser

vagrant magnet
#

gonne try that tomorrow not at home today

radiant geyser
#

I think it works now, thanks so much!

brittle oysterBOT
#
Thread Closing Reminder

Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.

If not yet resolved, please reply below to tell us what you still need.

(Note that if there is no reply for a few days, this thread will eventually close itself.)

#

@radiant geyser

undone shell
#

I apologise if reopening tickets is not allowed? Ive updated Citizens (we had this bug prior to updating plugins this morning). Players are reporting the skins of NPC's are not showing. Both Geyser and Citizens is up to date and we're getting the same errors as OP.

brittle oysterBOT
#
Thread Closing Reminder

Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.

If not yet resolved, please reply below to tell us what you still need.

(Note that if there is no reply for a few days, this thread will eventually close itself.)

#

@radiant geyser