Console error when using /claim on a 1.18 server while running latest commit (6debf368c9823c01fe747d70d5c1845024d86fa1)
Expected Behavior
No negative impact is observed so far.
Reproduction steps
[12:08:04 INFO]: issued server command: /claim
Stack trace or error log
[12:08:04 INFO]: <name> issued server command: /claim
[12:08:04 WARN]: [GriefPrevention] Plugin GriefPrevention v16.17.1-33-g6debf36 generated an exception while executing task 25112
java.lang.NoSuchFieldError: DESERT_HILLS
at me.ryanhamshire.GriefPrevention.RestoreNatureProcessingTask.getPlayerBlocks(RestoreNatureProcessingTask.java:851) ~[GriefPrevention-dev.jar:?]
at me.ryanhamshire.GriefPrevention.AutoExtendClaimTask.lambda$getBiomeBlocks$0(AutoExtendClaimTask.java:79) ~[GriefPrevention-dev.jar:?]
at java.util.HashMap.computeIfAbsent(HashMap.java:1220) ~[?:?]
at me.ryanhamshire.GriefPrevention.AutoExtendClaimTask.getBiomeBlocks(AutoExtendClaimTask.java:79) ~[GriefPrevention-dev.jar:?]
at me.ryanhamshire.GriefPrevention.AutoExtendClaimTask.getLowestBuiltY(AutoExtendClaimTask.java:58) ~[GriefPrevention-dev.jar:?]
at me.ryanhamshire.GriefPrevention.AutoExtendClaimTask.run(AutoExtendClaimTask.java:33) ~[GriefPrevention-dev.jar:?]
at org.bukkit.craftbukkit.v1_18_R1.scheduler.CraftTask.run(CraftTask.java:101) ~[paper-1.18.jar:git-Paper-35]
at org.bukkit.craftbukkit.v1_18_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:57) ~[paper-1.18.jar:git-Paper-35]
at com.destroystokyo.paper.ServerSchedulerReportingWrapper.run(ServerSchedulerReportingWrapper.java:22) ~[paper-1.18.jar:git-Paper-35]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
at java.lang.Thread.run(Thread.java:833) ~[?:?]
Server version
[12:12:42 INFO]: This server is running Paper version git-Paper-35 (MC: 1.18) (Implementing API version 1.18-R0.1-SNAPSHOT) (Git: 63a97a6)
GriefPrevention version
[12:13:00 INFO]: GriefPrevention version 16.17.1-33-g6debf36
Observed Behavior
Console error when using /claim on a 1.18 server while running latest commit (6debf368c9823c01fe747d70d5c1845024d86fa1)
Expected Behavior
No negative impact is observed so far.
Reproduction steps
[12:08:04 INFO]: issued server command: /claim
Stack trace or error log
Server version
GriefPrevention version
Configuration
Plugin list
No response
Running without GriefPrevention
Running with only GriefPrevention
Running on a fresh, clean server installation
Using unmodified client
We appreciate you taking the time to fill out a bug report!