Observed Behavior

If I have a claim, it doesn't go lower then 0.

Expected Behavior

The problem:
The claim area is visible with the wooden stick ( also below zero ), but if you want to demolish or place below zero, you can just do that. Even if it is not your own claim. The claim runs to level zero, so from -1 to -64 it is no longer protected.

Reproduction steps

1. claim area
2. break or build blocks
3. go to level 0
4. break or build blocks
5. claim doesn't go below 0, although you can see the claim with the wooden stick.

Stack trace or error log

There is no warning log.

Server version

Server:
Spigot 1.18.2 R0.1 SNAPSHOT (27-03-2022)

GriefPrevention version

Griefprevention version 16.18

Configuration

Not needed for this bug.
also it is just standard generated.

Plugin list

Griefprevention works fine for what I use, ecxept the claim area.

Running without GriefPrevention

• I attempted running the server without GriefPrevention installed.
• The problem does not occur when GriefPrevention is removed from the server.

Running with only GriefPrevention

• I attempted running only GriefPrevention on the server.
• The issue still occurs when GriefPrevention is the only plugin running.

Running on a fresh, clean server installation

• I attempted testing for the issue on a new server.
• The issue still occurs on a new server.

Using unmodified client

• I attempted testing for the issue with the vanilla client.
• The issue still occurs when using the vanilla client.

We appreciate you taking the time to fill out a bug report!

• I searched for similar issues before submitting this bug report.

Even modifiyng the MaximumDepth it does not work with negative y !!!

Just noticed that if I modify the claimdata to a negative Y coordinate IT WORKS but the plugin doesn't know how to put the - (minus) behind the number LOOOOL

Config is actually very important, because you likely have an old default config that does not have the value for MaximumDepth set to 1.17+ values.

Aaah good to know, so if I delete the old config file and let the plugin create a new one, it could be fixed? I will try it later today!
If not I will react later again and will paste the config file over here as well.

Please stop spamming the tracker with the same message.

Judging by the fact that OP isn't back, it did in fact solve their problem.