Skip to content

Port from v3.12.0 to v4 #522

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

Merged
merged 8 commits into from
Jun 2, 2025
Merged

Port from v3.12.0 to v4 #522

merged 8 commits into from
Jun 2, 2025

Conversation

It is still not fully fixed due to a bug in ProtocolLib, but nothing we
can do from Triton's side.

(cherry picked from commit b395df7)
Fixes #494

(cherry picked from commit b892cc9)
This should fix the gradle wrapper verification step failing frequently.

(cherry picked from commit d19ac85)
This packet only exists on 1.14 and above.

Fixes #485

(cherry picked from commit 65e7b5d)
Since 1.20.2, the spawn packet no longer includes information about the
visibility of the custom name. This change makes a metadata packet be
sent if the custom name should be hidden.

(cherry picked from commit 13167f4)
@diogotcorreia diogotcorreia added this to the 4.0.0 milestone Jun 2, 2025
@diogotcorreia diogotcorreia self-assigned this Jun 2, 2025
@diogotcorreia diogotcorreia added the port/backport Port changes between Triton versions label Jun 2, 2025
@diogotcorreia diogotcorreia merged commit a22ab45 into v4 Jun 2, 2025
1 check passed
@diogotcorreia diogotcorreia deleted the port-from-v3.12.0 branch June 2, 2025 23:30
@github-project-automation github-project-automation bot moved this to Done in Triton Jun 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
port/backport Port changes between Triton versions
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

1 participant