Smiley Player Trader Version 1.7.32

Details

  • Filename
    SmileyPlayerTrader-1.7.32.jar
  • Uploaded by
  • Uploaded
    Jan 28, 2026
  • Size
    420.55 KB
  • Downloads
    155
  • MD5
    0cc0803b54e6e99169c7ac156a75a9fc

Supported Bukkit Versions

  • 1.21.11
  • 1.21.10
  • 1.21.9
  • 1.21.8
  • 1.21.7
  • 1.21.6
  • 1.21.5
  • 1.21.1
  • 1.21.2
  • 1.21.3
  • 1.21.4
  • 1.21
  • 1.20.6
  • 1.20.5
  • 1.20.4
  • 1.20.3
  • 1.20.2
  • 1.20.1
  • 1.20
  • 1.19.4
  • 1.19.3
  • 1.19.2
  • 1.19.1
  • 1.19
  • 1.18.2
  • 1.18.1
  • 1.18
  • 1.17
  • 1.16
  • 1.15

Changelog

Note

The previous release (version 1.7.31) was accidentally built using the code from the release before it (version 1.7.30). This release (version 1.7.32) contains the updates intended for version 1.7.31.

 

Change Log

Important note about permission change: If the plugin's default permissions aren't applied, grant smileyplayertrader.trade.rightclick to everyone to ensure players can continue to trade by right-clicking each other.

  • Support for Minecraft 1.21.11.
  • Option to enable a cooldown between trades (disabled by default). (#92)
  • Option to add commands that are executed after a successful trade. (#91)
  • Added an option to control right-click trading (smileyplayertrader.trade.rightclick).
  • Added WorldGuard flags for right-click trading (spt-right-click-trade) and using the /spt trade remote trade command (spt-remote-trade).

Note: We recommend backing up your SPT database and configuration file, just in case. While it is unlikely something will go wrong, it is always a good idea to have backup. Don't forget to make a backup of your config!

Updating Config

Option 1: Look at //github.com/Mrcomputer1/SmileyPlayerTrader/blob/v" rel="noopener nofollow" target="_blank">https://github.com/Mrcomputer1/SmileyPlayerTrader/blob/v[version number]/src/main/resources/config.yml" rel="nofollow">config.yml and set the settings you want in your config.yml.

Option 2: Rename your config.yml and restart/reload your server and then re-apply your settings to the new config.yml and restart/reload the server again to apply them.