GrzybcioRynek

Disable a feature

enabled flags in config.yml — what they really disable, and what is dead (stats, history button).

Compatible with: GrzybcioRynek 1.0.3Minecraft 26.2Web 0.1.0

Based on GrzybcioRynek 1.0.3 and web 0.1.0 source.

Almost every optional feature has enabled in config.yml. Two flags behave differently than the name suggests.

Flags that work

yaml
favorites:
  enabled: true

price-alerts:
  enabled: true
  max-per-player: 10

mailbox:
  enabled: true

ratings:
  enabled: true

anti-abuse:
  enabled: true

market-fee:
  enabled: true
Flagfalse means
favorites.enabled/market favoritesfavorites.disabled
price-alerts.enabled/market alertsalerts.disabled
mailbox.enabledmailbox off (items do not go that path as when true)
ratings.enabledseller ratings disabled
anti-abuse.enabledno listing cooldown, same-player purchase limit, or value cap
market-fee.enabledcalculateSaleFee / calculateListingFee return 0

After change: /market reload.

Example

Disable fees and alerts:

yaml
market-fee:
  enabled: false
price-alerts:
  enabled: false

history.enabled — command only

yaml
history:
  enabled: true
  retention-days: 30

Comment in config.yml itself: gates the /market history GUI. Transactions are still saved (refund, ratings).

In MarketCommand:

java
if (!plugin.getConfigManager().isHistoryEnabled()) {
    player.sendMessage("§cHistoria transakcji jest wyłączona.");
    return true;
}

The History button on slot 53 in MarketBrowseGUI does not check this flag. history.enabled: false does not hide the button and does not stop history saving.

stats.enabled — dead

yaml
stats:
  enabled: true

ConfigManager loads statsEnabled. No other Java file reads it. /market stats, the Statistics button (slot 49) and %grybciorynek_*% placeholders work regardless of this flag.

Warning

Setting stats.enabled: false disables nothing. There is no if (isStatsEnabled()) branch in the code.

What you cannot disable with a flag

  • The whole market — disable the plugin or revoke market.use.
  • Browse buttons 45–53 — hardcoded.
  • Vault — without economy the plugin disables itself.
  • Nexo / Oraxen / PAPI — simply do not install those plugins.

Permissions market.history, market.mailbox, market.alerts are in plugin.yml but are not checked in Java — do not use them as an off switch.