Limits

Listing, price, alert and cooldown limits — which keys actually work.

Compatible with: GrzybcioRynek 1.0.3Minecraft 26.2Web 0.1.0

Based on GrzybcioRynek 1.0.3 and web 0.1.0 source.

All limits are in config.yml. After change: /market reload.

Listings per player

yaml

settings:
  max-listings-per-player: 10

Counted are active listings for the UUID (getListingCountBySeller). History and mailbox do not count. Message: sell.limit-reached ({limit}).

Admin has no separate limit — lists as a normal player (/market sell / /wystaw).

Price

yaml

settings:
  min-price: 1.0
  max-price: 1000000.0

Checked on listing (sellItem): Double.isFinite(price) and range. Outside range / NaN / Infinity → sell.invalid-price.

On purchase additionally: price must be finite and > 0 (else buy.not-available). Separate purchase cap: anti-abuse.max-transaction-value (default 10000000).

Alerts

yaml

price-alerts:
  max-per-player: 10

Only when price-alerts.enabled. Exceeded: alerts.limit.

Listing cooldown

yaml

anti-abuse:
  enabled: true
  listing-cooldown-seconds: 5

In-memory (ConcurrentHashMap). Server restart clears. enabled: false disables cooldown.

Purchases from the same player

yaml

anti-abuse:
  max-purchases-from-same-player: 20
  purchase-window-seconds: 86400

Pair buyerUUID:sellerUUID. Also in-memory — restart clears counters.

Unused

Key	Status
`settings.gui-rows`	UNUSED — not a GUI limit
`stats.enabled`	UNUSED

No stack limit, category limit, or history limit beyond retention-days (pruning COMPLETED).

Messages

Fees