Fix vanish api sync error #448

Open
Rothes wants to merge 1 commit from Rothes/vanish-api into ver/1.21.11
Rothes commented 2026-03-19 03:18:31 +01:00 (Migrated from github.com)

Closes #406

Almost no performance impact, should be a good fix before a better vanish API implement.

Let me know if it should be included in the base patch

Closes #406 Almost no performance impact, should be a good fix before a better vanish API implement. Let me know if it should be included in the base patch
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin Rothes/vanish-api:Rothes/vanish-api
git switch Rothes/vanish-api

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch ver/1.21.11
git merge --no-ff Rothes/vanish-api
git switch Rothes/vanish-api
git rebase ver/1.21.11
git switch ver/1.21.11
git merge --ff-only Rothes/vanish-api
git switch Rothes/vanish-api
git rebase ver/1.21.11
git switch ver/1.21.11
git merge --no-ff Rothes/vanish-api
git switch ver/1.21.11
git merge --squash Rothes/vanish-api
git switch ver/1.21.11
git merge --ff-only Rothes/vanish-api
git switch ver/1.21.11
git merge Rothes/vanish-api
git push origin ver/1.21.11
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Minecraft/Folia!448
No description provided.