Configuration

Complete guide to configuring SigmaSellAxe. All configuration files use YAML format and support automatic migration between versions.

Main Configuration

The main configuration file is located at plugins/SigmaSellAxe/config.yml.

Sell Axe Settings

sell-axe:
  # Display name (supports color codes with &)
  name: '&6&lSigma Sell Axe'
  
  # Lore lines displayed on the Sell Axe
  lore:
    - '&7➤ Right-click chests, barrels, or shulkers to sell contents.'
    - '&7➤ Left-click to view all sellable items.'
  
  # Durability settings
  durability:
    enabled: true      # Enable/disable durability loss
    lose-per-sell: 1   # Durability lost per sell operation

Option	Type	Default	Description
`name`	String	`'&6&lSigma Sell Axe'`	Display name of the Sell Axe (supports color codes with `&`)
`lore`	List	2 lines	List of lore lines shown on the Sell Axe
`durability.enabled`	Boolean	`true`	Enable/disable durability loss when selling
`durability.lose-per-sell`	Integer	`1`	Amount of durability lost per sell operation

Features

features:
  left-click-gui: true        # Open GUI on left-click with Sell Axe
  prevent-enchanting: true    # Prevent enchanting the Sell Axe

Option	Type	Default	Description
`left-click-gui`	Boolean	`true`	Open sellable items GUI when left-clicking with Sell Axe
`prevent-enchanting`	Boolean	`true`	Prevent players from enchanting the Sell Axe

Logging

logging:
  enabled: true         # Enable transaction logging to console
  file-logging: true    # Enable logging to files
  log-rotation: true    # Automatically rotate log files

Option	Type	Default	Description
`enabled`	Boolean	`true`	Enable transaction logging to console
`file-logging`	Boolean	`true`	Enable logging to files in `plugins/SigmaSellAxe/logs/`
`log-rotation`	Boolean	`true`	Automatically rotate log files to prevent large files

Debug System

debug:
  enabled: false    # Enable debug logging
  level: BASIC      # BASIC, DETAILED, or VERBOSE

Option	Type	Default	Description
`enabled`	Boolean	`false`	Enable debug logging for troubleshooting
`level`	String	`BASIC`	Debug level: `BASIC`, `DETAILED`, or `VERBOSE`

Debug Levels:

BASIC - Essential debug information (recommended for troubleshooting)
DETAILED - More detailed information including permission checks and price lookups
VERBOSE - Maximum verbosity including all API calls and internal operations

Economy Settings

economy:
  # Shop plugin selection
  shop-plugin: excellentshop  # 'excellentshop', 'economyshopgui', or 'none'
  
  # Fallback prices (used when shop plugin unavailable or item not found)
  fallback-prices:
    DIAMOND_ORE: 150.0
    EMERALD_ORE: 200.0
    IRON_ORE: 50.0
    # ... more items

Option	Type	Default	Description
`shop-plugin`	String	`excellentshop`	Shop plugin to use: `excellentshop`, `economyshopgui`, or `none`
`fallback-prices`	Map	See config	Prices for items not in shop plugins (format: `MATERIAL_NAME: price`)

Integrations

integrations:
  lands-integration: true           # Lands plugin integration
  griefprevention-integration: true # GriefPrevention plugin integration
  worldguard-integration: true      # WorldGuard plugin integration

Option	Type	Default	Description
`lands-integration`	Boolean	`true`	Enable Lands plugin integration for area protection
`griefprevention-integration`	Boolean	`true`	Enable GriefPrevention plugin integration for claim protection
`worldguard-integration`	Boolean	`true`	Enable WorldGuard plugin integration for region protection

Shop Configuration

Shop-specific configuration files are located in plugins/SigmaSellAxe/shops/. These files are automatically generated when shops are detected.

Shop File Structure

shop:
  id: 'farming'           # Unique shop identifier
  name: 'Farming Shop'    # Display name
  enabled: true            # Enable/disable this shop
  priority: 1              # Priority when multiple shops have same item

# Global boost for all items in this shop
global-boost: 0.0

# Item-specific settings
items:
  PUMPKIN:
    boost: 1.0      # 100% boost multiplier
    enabled: true    # Enable/disable selling this item
  MELON:
    boost: 0.5      # 50% boost multiplier
    enabled: true

Option	Type	Description
`shop.id`	String	Unique shop identifier (matches shop plugin's shop ID)
`shop.name`	String	Display name of the shop
`shop.enabled`	Boolean	Enable/disable this shop (disabled shops are ignored)
`shop.priority`	Integer	Priority when multiple shops have the same item (higher = preferred)
`global-boost`	Double	Global boost multiplier for all items in this shop (0.0 = no boost, 1.0 = 100% boost)
`items.MATERIAL.boost`	Double	Item-specific boost multiplier
`items.MATERIAL.enabled`	Boolean	Enable/disable selling this specific item

Boost Calculation

The final sell price is calculated as:

finalPrice = basePrice × (1 + globalBoost + itemBoost)

Example:

Base price: $100
Global boost: 0.5 (50%)
Item boost: 1.0 (100%)
Final price: $100 × (1 + 0.5 + 1.0) = $250

Config Migration

The plugin automatically migrates your configuration when updating versions. This ensures:

New configuration keys are added automatically
Deprecated keys are removed safely
Your custom settings are preserved
Config version is updated automatically

Migration happens automatically on:

Plugin startup
Configuration reload (/sigmasellaxe reload)

Reloading Configuration

Reload the configuration without restarting the server:

/sigmasellaxe reload

This will:

Reload main config (config.yml)
Reload all shop configs
Reinitialize protection plugin integrations
Reinitialize shop plugin integrations
Apply new settings immediately

Regenerating Shop Configs

If you've changed your shop plugin configuration, regenerate shop configs:

/sigmasellaxe regenerate

This will:

Re-detect all shops from your shop plugin
Update shop configuration files
Preserve your custom boosts and settings
Add new items from shops
Remove items no longer in shops

Configuration Best Practices

Backup before changes - Always backup your config before making major changes
Test in development - Test configuration changes on a development server first
Use reload command - Use /sigmasellaxe reload instead of restarting the server
Check logs - Review server logs after configuration changes
Verify config - Use /sigmasellaxe verifyConfig to check for issues