IntellectualSites / IntellectualSites/PlotSquared
Blocks placed during /plot delete confirmation remain after plot is deleted
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 653
- Forks
- 975
- Avg merge
- 2m
- Merged PRs (30d)
- 6
Description
Server Implementation
Paper
Server Version
1.21.3
Describe the bug
When deleting a plot, any blocks that are placed during the /p confirm phase remain on the plot even after it is deleted or becomes unclaimed.
These blocks are not removed together with the plot deletion process.
To Reproduce
- Initiate a plot deletion (
/plot delete). - While waiting for the confirmation, place several blocks on the plot.
- Execute
/plot confirm. - The plot is deleted / unclaimed, but the blocks placed during the confirmation phase remain instead of being removed.
Expected behaviour
All blocks placed on the plot (including those placed during the deletion confirmation phase) should be removed when the plot is deleted or unclaimed.
Screenshots / Videos
https://github.com/user-attachments/assets/596986e1-f635-4827-aa56-acce8f986757
Error log (if applicable)
No response
Plot Debugpaste
https://athion.net/ISPaster/paste/view/04b06c6d51d3420bab74485da6499af0
PlotSquared Version
PlotSquared version 7.5.10-SNAPSHOT
Checklist
- I have included a Plot debugpaste.
- I am using the newest build from https://www.spigotmc.org/resources/77506/ and the issue still persists.
Anything else?
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the /plot delete and /plot confirm command entry points, then follow the plot deletion or unclaim block-cleanup path. Reproduce the sequence on Paper 1.21.3 with PlotSquared 7.5.10-SNAPSHOT and verify that blocks placed during confirmation are removed when deletion completes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100