ScrollingMenuSign v2.3.1

Details

  • Filename
    ScrollingMenuSign.jar
  • Uploaded by
  • Uploaded
    Nov 25, 2013
  • Size
    489.76 KB
  • Downloads
    1,088
  • MD5
    9e44d7e8121834a66ce1f3dc03969cae

Supported Bukkit Versions

  • CB 1.6.4-R2.0

Changelog

v2.3.1 (25 Nov 2013)

  • Added a couple of backwards compat methods to the SMSView class. This is intended to allow older versions of Heroes to continue to work with newer releases of ScrollingMenuSign. If you don't use Heroes, this update doesn't bring anything else.

v2.3.0 (14 Nov 2013)

  • Added new view attribute to all scrollable view types: scroll_type. This may be one of "scroll", "page" or "default". "scroll" is the default and current behaviour - the selected item remains in place and the view scrolls around it. The "page" type allows the selection cursor to move and the view will switch to the next/previous page (where there are more items than can be displayed on one page). A value of "default" means to use the global "scroll_type" Configuration setting, which can be one of "scroll" or "page".
  • Item costs: giving or taking items should now use a material name, not a numeric ID. Numeric ID's are still accepted for now, but will log a warning to the console & server.log so that you can fix the menu entry. This is due to numeric IDs being generally deprecated by both Bukkit and Mojang.
  • Inventory views now have a "spacing" attribute (default 0) - this controls how many blank inventory slots are placed between each icon in the inventory.
  • Multisign view rendering should now be somewhat lighter on CPU when the multisign is only 1 sign wide (regardless of how many signs high)
  • Predefined substitutions in commands (e.g. <EXP>, <MONEY> - see Command Parser) are now done on a command-by-command basis rather than all the very start of command parsing. This means that a chained command like "$x,10 && \\You now have <EXP> experience" now reports the new experience amount instead of the previous amount. The previous behaviour can still be achieved by not using chaining, e.g. "$x,10 \\You had <EXP> experience && You now have <EXP> experience"
  • Predefined substitutions in commands should now be a little lighter on CPU.