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

Paper support stage 3: Migrate to Paper patch. #1661

Open
qyl27 opened this issue Feb 17, 2025 · 6 comments
Open

Paper support stage 3: Migrate to Paper patch. #1661

qyl27 opened this issue Feb 17, 2025 · 6 comments
Assignees
Labels
Category: Bukkit Inconsist behavior with Spigot server Category: Paper API Issue related Paper API implementation Status: Waiting for Fix | 等待处理 Problem confirmed, waiting for fix Tag: Enhancement | 增强 New feature or request Version: Feudal Kings (1.21/1.21.1)

Comments

@qyl27
Copy link
Collaborator

qyl27 commented Feb 17, 2025

Move to the paper patch in 1.21.1, it is the version before massive changes to the upstream API. It is safe to directly move.

@qyl27 qyl27 added Category: Bukkit Inconsist behavior with Spigot server Category: Paper API Issue related Paper API implementation Status: Waiting for Fix | 等待处理 Problem confirmed, waiting for fix Tag: Enhancement | 增强 New feature or request Version: Feudal Kings (1.21/1.21.1) labels Feb 17, 2025
@qyl27 qyl27 self-assigned this Feb 17, 2025
@Kotori0629
Copy link

might break a lot of mod compatibility

@qyl27
Copy link
Collaborator Author

qyl27 commented Feb 19, 2025

might break a lot of mod compatibility

How about listing 6 of them?

@MemencioPerez
Copy link

Move to the paper patch in 1.21.1, it is the version before massive changes to the upstream API. It is safe to directly move.

I think it's important to note that Paper will not pull changes from the Spigot repository after the 1.21.4 hard fork, so it may ease some of the pain of having to keep up with both Spigot and Paper.

@qyl27
Copy link
Collaborator Author

qyl27 commented Feb 23, 2025

Move to the paper patch in 1.21.1, it is the version before massive changes to the upstream API. It is safe to directly move.

I think it's important to note that Paper will not pull changes from the Spigot repository after the 1.21.4 hard fork, so it may ease some of the pain of having to keep up with both Spigot and Paper.

Yes, I haven't considered how to do it after 1.21.4 yet.
Btw, stage 2 should allow us to swiftly switch between the obc source forks. And we will only use the obc sources of Spigot or Paper, without the vanilla patches.

@Kotori0629
Copy link

Move to the paper patch in 1.21.1, it is the version before massive changes to the upstream API. It is safe to directly move.

I think it's important to note that Paper will not pull changes from the Spigot repository after the 1.21.4 hard fork, so it may ease some of the pain of having to keep up with both Spigot and Paper.

Yes, I haven't considered how to do it after 1.21.4 yet. Btw, stage 2 should allow us to swiftly switch between the obc source forks. And we will only use the obc sources of Spigot or Paper, without the vanilla patches.

u can create branch or repository in advance to facilitate code contributions

@qyl27
Copy link
Collaborator Author

qyl27 commented Feb 24, 2025

Move to the paper patch in 1.21.1, it is the version before massive changes to the upstream API. It is safe to directly move.

I think it's important to note that Paper will not pull changes from the Spigot repository after the 1.21.4 hard fork, so it may ease some of the pain of having to keep up with both Spigot and Paper.

Yes, I haven't considered how to do it after 1.21.4 yet. Btw, stage 2 should allow us to swiftly switch between the obc source forks. And we will only use the obc sources of Spigot or Paper, without the vanilla patches.

u can create branch or repository in advance to facilitate code contributions

A branch for stage 1 is already in our private development repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: Bukkit Inconsist behavior with Spigot server Category: Paper API Issue related Paper API implementation Status: Waiting for Fix | 等待处理 Problem confirmed, waiting for fix Tag: Enhancement | 增强 New feature or request Version: Feudal Kings (1.21/1.21.1)
Projects
None yet
Development

No branches or pull requests

3 participants