Paper warns about the usage of Timing(s) #5
Description
Used Version
v1.5-SNAPSHOT (build 297)
Environment description
paper 1.20
Log
[18:49:00 WARN]: [!] The timings profiler has been enabled but has been scheduled for removal from Paper in the future.
We recommend installing the spark profiler as a replacement: https://spark.lucko.me/
For more information please visit: https://github.com/PaperMC/Paper/issues/8948
[18:50:23 WARN]: [Pipes] Could not save lang.de.yml to plugins/Pipes/lang.de.yml because lang.de.yml already exists.
[18:50:23 WARN]: Plugin 'Pipes' is creating timing 'move' - this is deprecated behavior, please report it to the authors: Lord36, Phoenix616
[18:50:23 WARN]: Plugin 'Pipes' is creating timing '## filter' - this is deprecated behavior, please report it to the authors: Lord36, Phoenix616
[18:50:23 WARN]: Plugin 'Pipes' is creating timing '## transfer' - this is deprecated behavior, please report it to the authors: Lord36, Phoenix616
[18:50:23 WARN]: Plugin 'Pipes' is creating timing '## filter_amount' - this is deprecated behavior, please report it to the authors: Lord36, Phoenix616
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, 320
where it's only ever called in form of try (Timing t = <Timing>.startTiming()) {...}