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

Support Folia #809

Closed
wants to merge 19 commits into from
Closed

Conversation

Euphillya
Copy link
Contributor

@Euphillya Euphillya commented Apr 17, 2024

This version breaks Spigot and Paper compatibility before 1.20.1

Features :

  • Support Folia (in progress)

Fix :

@TrueDarkLord
Copy link
Contributor

Oh epic! I will make sure to check this out tomorrow.

Breaking compatibility with older versions also isn't a problem as we tend to now only support the latest releases of PaperMC. Compatibility with older versions has been broken quite a few times by now.

@ryderbelserion ryderbelserion added the status: in progress The pull request or feature in progress label Apr 18, 2024
@Euphillya Euphillya marked this pull request as ready for review April 25, 2024 20:02
@Euphillya
Copy link
Contributor Author

I don't think there is any other incompatibility.

@Euphillya Euphillya changed the base branch from main to ver/1.20.5 April 25, 2024 20:08
Copy link
Contributor

@TrueDarkLord TrueDarkLord left a comment

Choose a reason for hiding this comment

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

All seems to be quite straight forward; just switching over to a different scheduler.
Everything seems to be working as intended based on the quick checks that I did on paper-1.20.4-496.jar as well as on the un-relocated jar.

Just one suggested change and one potential change.

Copy link
Contributor

Choose a reason for hiding this comment

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

For each of the check<enchantName> methods, I would assume that having player.getScheduler().run lower down where the older method was would be better due to it keeping more of the processing off the main thread.

@Euphillya
Copy link
Contributor Author

Is it good ?

@ryderbelserion
Copy link
Member

You have unsigned commits blocking the merge.

@Euphillya
Copy link
Contributor Author

Should I recreate this PR?

@ryderbelserion
Copy link
Member

ryderbelserion commented Apr 27, 2024

git rebase --exec 'git commit --amend --no-edit -n -S' -i development or use a commit hash like 6313ca1

This rebases everything till development (or any hash) and you don't have to copy paste after every commit.

https://superuser.com/questions/397149/can-you-gpg-sign-old-commits

@ryderbelserion
Copy link
Member

git rebase --exec 'git commit --amend --no-edit -n -S' -i development or use a commit hash like 6313ca1

This rebases everything till development (or any hash) and you don't have to copy paste after every commit.

https://superuser.com/questions/397149/can-you-gpg-sign-old-commits

or yeah you can re-create the branch and re-commit then open a new pull request

@Euphillya Euphillya closed this Apr 27, 2024
@Euphillya Euphillya mentioned this pull request Apr 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: in progress The pull request or feature in progress
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants