IntellectualSites / IntellectualSites/PlotSquared

Charge for individual plots during `/plot merge` economy

Open
#3,285 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What feature do you want to see added?

Suggestion:

Background:
For a survival Server using plotsquared it makes no sense that the /plot merge price only charges for the event and not for each plot that get merged. The merging costs of plots are one factor to stabilize the economy, players who claim their starting plots in a row (4x1) had an advantage to the players who claim their plots in a square (4x2), The merging costs reaches from each server between 10k till 100k for merging. In germany Citybuild Servers are pretty popular and some Servers who don't use plotsquared have this feature already, it would be nice if it could be implemented in plotsquared too.

Idea how to implement:

In my opinion there would be two possible ways to implement this :

  1. A Setting that could be activated in the config, that for each plot that get merged with /plot merge it will deduct the merge price and not for the event only

  2. A permission like plots.merge.reach.1 or like that. That only 1 plot at a time could be merged with another (This way it would not only benefit Survival Server but Server Owner in general who want to merge 1 Plot at one time)

Are there any alternatives?

Currently there are no alternatives.

Anything else?

No response

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 /plot merge command handling and the existing merge-price behavior. Compare the two proposed approaches—charging per merged plot through configuration or limiting merge reach through permissions—and define which behavior is intended before identifying implementation points. Done means the selected option is implemented and its economy impact is covered by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
game-dev
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.