Skip to content

Releases: XZot1K/DisplayShopsAPI

DisplayShopsAPI 1.2.2

04 Nov 04:51
Compare
Choose a tag to compare

This build is intended for 1.5.7 (Build 16) and above

  • The "ChatInteractionStageEvent" now has a new "INCORRECT" enumeration type which is fired when an invalid entry is entered.

DisplayShopsAPI 1.2.1

03 Nov 15:01
Compare
Choose a tag to compare

This build is intended for 1.5.7 (Build 15) and up.

  • Added the "isCancelBlockPlaceEvent" and "setCancelBlockPlaceEvent" methods to the "ShopCreationEvent" allowing cancelling of the internal "BlockPlaceEvent".

  • Adjusted all events to set a default cancellation value.

DisplayShopsAPI 1.2

13 Oct 19:04
Compare
Choose a tag to compare

This build is intended for DisplayShops 1.5.6 (Build 4) and above.

  • Added the "getInventorySpaceForItem" method to the "Manager" interface.
  • The "save" method in the "Shop" interface no longer requires a statement argument.

DisplayShopsAPI 1.1.9

05 Oct 03:56
6ee6992
Compare
Choose a tag to compare

This build is intended for 1.5.7 (Build 1) and above.

  • Replaced the “getCurrentEditor” and “setCurrentEditor” methods in the “Shop” interface with “getCurrentEditors” to allow more precise evaluation of who is actually modifying the shop.
  • Removed the “setBeingEdited” method in the “Shop” interface. The “isBeingEdited” method now uses the new “getCurrentEditors” method and checks if it is empty.
  • Added the “resetEditData” method to the “DataPack” interface.

DisplayShopsAPI 1.1.8

28 Sep 20:56
Compare
Choose a tag to compare

This build is intended for v1.5.6 (Build 6) and 1.5.6 release.

  • The "saveMarketRegions" within the "Manager" interface now requires a SQL statement to operate.
  • Added the "getBaseBlockOffsets" method to the "Manager" interface.

DisplayShopsAPI 1.1.7

22 Sep 21:49
Compare
Choose a tag to compare

This build is intended to be used with DisplayShops v1.5.6 (Build 4) to utilize new methods alongside replaced methods. Please use v1.1.6 for the Spigot release v1.5.5!

  • Added the "toJSON" method to the "SerializeUtil" interface and used it as a replacement for the entire packet setup.
  • Added the "isBeingEdited" and "setBeingEdited" methods to the "Shop" interface. This value is now used for the shops during the editing process.
  • Added the "ShopEditEvent" event which is fired whenever a player opens the edit menu. It is also used by the plugin on the LOWEST priority so it can set the new shop editing value and perform actions.

DisplayShopsAPI 1.1.6

15 Sep 19:11
Compare
Choose a tag to compare

Intended for build 1.5.5 (Build 1)

  • Replaced the "updatePersonalChatTask" method with the "updateChatTimeoutTask" method in the "DataPack" interface for easier clarification and versatility.
  • Added the "ChatInteractionStageEvent" event class which now fires using different stages from the "StageType" enumeration class. This event is NOT cancellable and will fire at different stages during the chat interaction process.

UPDATE - Added the "CANCELLED" entry to the "StageType" enumeration.

DisplayShopsAPI 1.1.5

15 Sep 00:30
Compare
Choose a tag to compare
  • Removed the "sendDisplayPacketToAll" and "sendPossibleDisplayPackets" methods from the "DisplayShopsAPI" interface.
  • Removed all task-related methods from the "DisplayShopsAPI".
  • The "clearDisplayPackets" method in the "DisplayShopsAPI" interface now also kills the display packets.

DisplayShopsAPI 1.1.4

07 Sep 05:01
Compare
Choose a tag to compare

This build is intended for DisplayShops 1.5.4 (Build 5) and above.

  • Added the "getBaseBlockPageMap", "setBaseBlockPageMap", "setCurrentBaseBlockPage", and "getCurrentBaseBlockPage" methods to the "DataPack" interface for the new base-block multi-page system.

DisplayShopsAPI 1.1.3

02 Sep 01:52
Compare
Choose a tag to compare

This build is intended to be used with v1.5.4 (Build 3) and above.

  • Added the "updateAllBaseBlockAccess" method to the "DataPack" object interface.
  • Added the "getShopById" method to the "Manager" interface.
  • The "save" method in the "Shop" object interface now requires an SQL statement to reduce the creation of too many statements in a short period of time.