IntellectualSites / IntellectualSites/PlotSquared

Make merged plots count as one

Open
#2,960 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Enhancement
Dominant language
Java
Stars
653
Forks
975
Avg merge
2m
Merged PRs (30d)
6

Description

PlotSquared Feature Suggestion:

How should it be implemented?

If i merge a players plot and i want to rezize that merge (Take plots) i use /p unlink false and then i merge the plots again with /p merge false
but some times the road gets broken, so i have to fix the road with worldedit. it would be nice if there is a command /plot fixroad which fixed the road im standing on. regenerates only that piece of road.
It would be nice, if merged plots will counted as one. so if a player can claim 2 plots. and have 2 plots, and i merge the plots the player can claim one plot more because 1 merge = 1 plot. It would also be nice if the api method. plotplayer.getPlots() returns the plot count as merged plot = 1. it would also be nice, if this feature gets an config option to enable/disable.
Please check: https://issues.intellectualsites.com/issue/PS-148

Additional context

Checklist:

  • I made sure there are no duplicates of my suggestion (Use search)
  • I made sure my suggestion does not exist yet (Check the wiki)
  • I made sure my suggestion is useful for the majority of PlotSquared users

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the /p unlink false and /p merge false commands and the PlotPlayer.getPlots() API method mentioned in the issue. Check the referenced PS-148 issue for related context; completion would need an agreed scope covering merged-plot counting, the optional configuration, and the proposed road-repair command.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.