-
Notifications
You must be signed in to change notification settings - Fork 123
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
Folia support for PlayerVaults #448
Comments
I would like this. |
I am working on Folia support in the rewrite. |
This might be of interest: https://github.com/TechnicallyCoded/FoliaLib Here's the error on startup with the latest PlayerVaults from github on Folia 1.20.1:
|
Sorry, but no interest there. Forcibly shoving folia support into 4.x will fail or risk data corruption or duplication. Rewrite, which is making good progress, is the way to go here. |
Sounds good. Happy to help test when it's ready. |
I'll have updates and testing information available first on Discord, prior to full release. |
Now tracking here: KittehDev/PlayerVaultsX#4 |
Idea
https://github.com/PaperMC/Folia
Here is a summary of everything made with ChatGPT to save some time:
For plugin developers, there are a few key takeaways from the given text:
Folia introduces regionised multithreading, which means that plugins will require modification to function properly. Plugin developers should expect compatibility with existing plugins to be at zero.
Folia introduces new API additions, such as the RegionisedScheduler and EntityScheduler, which can help plugins run on the correct thread context.
To ensure compatibility with Folia, plugin developers must mark their plugin as compatible by placing "folia-supported: true" in the plugin.yml file. Additionally, plugins must take advantage of the RegionisedScheduler and EntityScheduler API to ensure correct behavior.
Plugins should not assume that they can access or modify data in other regions, as Folia regions tick in parallel and do not share data. Plugin developers should take advantage of the upcoming thread-check API to ensure correct behavior.
There are currently broken API, including the scoreboard API, and planned API changes, such as super aggressive thread checks, which may impact plugin development.
Overall, plugin developers should be prepared for significant changes in their plugins to ensure compatibility with Folia. They should take advantage of the new API additions and mark their plugin as compatible to ensure correct behavior. Additionally, they should be aware of the limitations and rules of Folia's regionised multithreading to avoid bugs and errors in their plugins.
Details
Folia will be a game changer for most servers and we need to make sure all plugins supports it, I know that this can take a while to implement.
The text was updated successfully, but these errors were encountered: