-
-
Notifications
You must be signed in to change notification settings - Fork 238
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 #47
Comments
I don't know exactly how much plugin requires a paper api. If someone see this please add an emoji here. |
We have a lot of plugins on our vanilla server that need the Paper API. :> |
This is now considered in roadmap. I'm busy schooling now, and if I have enough time I will work on it. |
Paper support is definitely something I'd love to see supported by Arclight |
I wonder if users prefer Paper API support or just performance and optimize. Please react with ❤️ if API support and 🚀 if performance. |
Hello, Thank you for all the work you do in the project! |
PixelmonMod Community Manager here. A full, clean implementation of Paper is needed for Arclight to be production-ready. Servers with a large amount of players will require the support Paper provides in API and performance. We expect that with our move to 1.16.5, you'll be seeing a lot more pressure from the server community towards Arclight's performance in comparison to projects such as Mohist or even Sponge. Should you need to discuss this further, I'm on your discord, Rasgnarok#6969. |
I think both are a good idea, performance is definitely a huge issue for large scale servers at the moment especially with chunk loading. |
Per discussion in Discord.
|
At least add the adventure API plz |
After Paper changes more of Spigot's behaviors, we might need to re-evaluate the priority of this issue and make a decision. |
Reducing paper api support is actually good thing because idiotic paper devs gives no shit to backwards compatibility. Less paper api support = less paper plugins = less pain. |
Can you implement the paper API?
The text was updated successfully, but these errors were encountered: