Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Players spawn, skins and capes, scoreboard, bossbar, fixes and updated protocol lib #41

Merged
merged 9 commits into from
Oct 11, 2019

Conversation

Tim203
Copy link
Member

@Tim203 Tim203 commented Sep 25, 2019

No description provided.

@Redned235
Copy link
Member

Finally had some time to sit down and take a look through this. From what I could see, the code looked fine, however I've not yet had time to test this. I'll do some testing of my own tomorrow but if anyone else wants to try this out, please feel free to do so.

@Flonja
Copy link

Flonja commented Sep 27, 2019

I have tested the skins, the players spawn correctly. The only things I haven't tested are bossbars and scoreboards. And now I'm implementing optifine capes on local

@Tim203
Copy link
Member Author

Tim203 commented Sep 27, 2019

Thanks for testing (I wanted some tests before pushing), but I already have the code local for optifine capes (and some other mods)

@Heath123
Copy link
Contributor

I get this error and I can't see players

Could not translate packet ServerPlayerListEntryPacket
null
.Haven't received PlayerListEntry packet before spawning player! We ignore the player 4f5d306b-17ca-34b2-bea9-bacc6907e17c```

@WesleyVanNeck
Copy link
Contributor

@Heath123 i got same issue i discusted it with tim on discord geyser chat

@Heath123
Copy link
Contributor

Oh, OK

@Heath123
Copy link
Contributor

@WesleyVanNeck What's your Discord name?

Copy link

@Daisreich Daisreich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

coolio

@Daisreich
Copy link

also, i got the same error too.

@Redned235 Redned235 added the Work in Progress The issue is currently being worked on. label Sep 30, 2019
@EOT3000 EOT3000 requested review from LogicismDev, Redned235 and EOT3000 and removed request for LogicismDev, Redned235 and EOT3000 October 1, 2019 02:57
connector/pom.xml Outdated Show resolved Hide resolved
@Redned235
Copy link
Member

Gravity appears to be sent too late, which likely has to do with the issues mentioned in #52. I was launched up into the air and then when everything else loaded, I fell to the ground. Most times, the anticheat detection would kick me off.

@Tim203
Copy link
Member Author

Tim203 commented Oct 5, 2019

That shouldn't possible because it is one of the first packet to be sent (JoinGame), and enabling gravity the last one (in the queue). I don't have any moved too quickly on the servers (and localhost) I tried. And I guess that the CPU spike is caused by the rapidly sent packets after the packetqueue is unfrozen (and the fact that the client keeps connected after he logged out and gets disconnected after the new connected logged in)

@Tim203 Tim203 changed the title Players spawn, player skins, scoreboard, bossbar and updated protocol lib Players spawn, skins and capes, scoreboard, bossbar, fixes and updated protocol lib Oct 5, 2019
@Redned235
Copy link
Member

Did some testing with the latest commit. Players appear only to be added to the player list when in range. If a player is not within my view distance, they are not added to the player list. However when I teleport away from the player added, they are still in the player list. Not sure if this is expected behavior.

As for gravity, I tested this a few times on multiple different servers and didn't have any issues upon first join. However, when switching servers or changing worlds, I was sent up in the air a few times, due to the gravity attribute not being set. Roughly 3/5 switches I was sent up in the air and able to fall back down and not crash. Only on one occurrence did I crash from being sent up too high.

@Tim203
Copy link
Member Author

Tim203 commented Oct 10, 2019

I removed the gravity. And the playerlist is expected when I look at the code, but was not my intension

@Redned235
Copy link
Member

Seems good from my testing and haven't ran into any more issues. Merging.

@Redned235 Redned235 merged commit 30d1570 into GeyserMC:master Oct 11, 2019
@Tim203 Tim203 removed the Work in Progress The issue is currently being worked on. label Oct 22, 2019
Hellohi3654 referenced this pull request in HelloGeyser/Geyser Sep 20, 2020
Camotoy added a commit that referenced this pull request Aug 20, 2022
This probably isn't needed anymore. This was introduced in #41 and is probably no longer needed since we never send movement before the player is spawned, and we don't allow movement to go through until the Bedrock player matches the unconfirmed teleport we create in JavaPlayerPositionTranslator. By removing this we should fix some instances of players kicked for 'flying' as players joining in the air would never respond to gravity until Bedrock finished loading.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants