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

Protocol changes for 1.21.50 #279

Merged
merged 9 commits into from
Dec 4, 2024
Merged

Protocol changes for 1.21.50 #279

merged 9 commits into from
Dec 4, 2024

Conversation

dries-c
Copy link
Member

@dries-c dries-c commented Nov 25, 2024

No description provided.

Copy link
Member

@ShockedPlot7560 ShockedPlot7560 left a comment

Choose a reason for hiding this comment

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

Look ok to me

Copy link
Member

@dktapps dktapps left a comment

Choose a reason for hiding this comment

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

Aren't there supposed to be new PlayerAuthInput flags in this version? I thought that's why they added the bitset nastiness.

src/serializer/BitSet.php Outdated Show resolved Hide resolved
src/serializer/BitSet.php Outdated Show resolved Hide resolved
tests/phpunit/BitSetTest.php Show resolved Hide resolved
@dktapps dktapps requested a review from a team December 3, 2024 14:14
@GameParrot
Copy link

hasFlag should probably be kept for compatibility

@dktapps
Copy link
Member

dktapps commented Dec 3, 2024

It's a protocol update, we don't care about BC in the protocol. Every update requires breaking stuff anyway.

@dktapps
Copy link
Member

dktapps commented Dec 4, 2024

CI is crying about something unspecified, pls run tests locally and see what the problem is

@dktapps dktapps merged commit bd1ec79 into master Dec 4, 2024
11 checks passed
Comment on lines +30 to +31
private UuidInterface $worldTemplateId;
private string $worldTemplateVersion;
Copy link
Member

Choose a reason for hiding this comment

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

These should be public as there are no get/setters

Copy link
Member Author

Choose a reason for hiding this comment

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

You're right. If someone wants to make a PR of it, go for it. Else I'll sort it out tomorrow

Copy link
Member

Choose a reason for hiding this comment

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

Yeah, the convention has been to keep fields public in older packets and only private them in newly added packets, to ensure the API is consistent within packets

Copy link
Member

Choose a reason for hiding this comment

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

That being said I've never been super sure whether privating the fields was a good idea... what we really need more than anything else is #95

@dries-c dries-c deleted the bedrock-1.21.50 branch December 5, 2024 08:29
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.

7 participants