-
-
Notifications
You must be signed in to change notification settings - Fork 3
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 warns about the usage of Timing(s) #5
Comments
Until Spark can to what Timings v2 can do the hooks will not be removed from the plugin. |
Alright. Just wanted to open a issue for future refference |
Do you still stand by your opinion since timings is disabled by default now on paper? Does this mean everyone using Pipes has to re-enable them? |
Yes
No, only if you want Pipes-specific Timings. Also if Paper ends up removing it completely I will look into adapting it to either Spark (if they ever manage to support this way of doing things), the inbuilt Minecraft profiler or even resurrecting my Paper fork Origami to re-add Timings v2. |
Well currently there is a PR on Paper to remove timings. I believe it won't get merged this update cycle but if mojang keeps introducing breaking updates in subversions maybe in some 1.21.X... |
Used Version
v1.5-SNAPSHOT (build 297)
Environment description
paper 1.20
Log
What is happening?
While it's still working, the timings api is marked for removal and paper is nagging about it.
However, I belive while they make a fuss, they do not ship the api themselfs.
Additional context
You may want to have a look into spark docs
The Timings API is being used in
io.github.apfelcreme.Pipes.Manager
in lines 108, 241, 273, 320where it's only ever called in form of
try (Timing t = <Timing>.startTiming()) {...}
The text was updated successfully, but these errors were encountered: