New inventories !
v4.0.1.7Added PostgreSQL support: set storage-type: POSTGRESQL (POSTGRES is also accepted) in config.yml and fill in database-configuration (default PostgreSQL port: 5432). The JDBC driver is downloaded automatically by the server. PostgreSQL also works as the shared database of the Redis addon Added Admin player directory, new inventories/admin/admin-main.yml inventory: lists every player with auction activity (listings, purchases, logs or transactions) with %listed%, %sold% and %purchased%, sortable by name, listed, sold or purchased (ZAUCTIONHOUSE_ADMIN_PLAYERS_SORT). Clicking a head opens that player's admin history. Opened by /ah admin without argument, by /ah admin history without player (the player argument is now optional, /ah admin history still opens the player's history) and by the new ZAUCTIONHOUSE_ADMIN_MAIN button (added as "All players" in admin-history-main.yml). Requires zauctionhouse.admin.items. New buttons ZAUCTIONHOUSE_ADMIN_PLAYERS, ZAUCTIONHOUSE_ADMIN_PLAYERS_SORT and ZAUCTIONHOUSE_ADMIN_MAIN Added Admin removal confirmation, new inventories/admin/admin-remove-confirm.yml inventory: with the zauctionhouse.admin.remove.inventory permission, pressing Q (drop) or middle-clicking a listing in the main auction opens it (checked before the container preview). Three options reset on each opening: ZAUCTIONHOUSE_ADMIN_REMOVE_NOTIFY (notify the seller, on by default), ZAUCTIONHOUSE_ADMIN_REMOVE_EXPIRE (move the item to the seller's expired items instead of deleting it, on by default) and ZAUCTIONHOUSE_ADMIN_REMOVE_COPY (give the item to the admin, as a copy when Expire is on so the seller keeps theirs, off by default). ZAUCTIONHOUSE_ADMIN_REMOVE_CONFIRM performs a cluster-safe removal. While the inventory is open, the listing is reserved for the administrator (same mechanism as the purchase confirmation, synchronized across the cluster): it disappears from the other players' auction house and can be neither bought nor removed by its seller. Closing the inventory or clicking Cancel puts it back on sale, and so does a removal that fails. No change is needed in the Redis addon, but every server of the cluster should run the same plugin version Fixed A confirmation inventory (purchase or removal) could release, or confirm, a listing that had meanwhile been reserved by another player: after a reservation was freed by the confirmation timeout, closing or confirming the old window acted on the new reservation, and a player leaving, dying or opening a container preview could put back on sale a listing that someone else was confirming. Each reservation now records its owner and only that player can confirm or release it Added admin-main.yml and admin-remove-confirm.yml are copied automatically on startup on existing installations when missing Added An offline seller notified of an admin removal receives the message on their next join Added admin-listing-removed message in messages.yml, sent to the seller when an admin removes their listing Added ADMIN_REMOVE log type ("Admin Remove"), written for each admin removal and visible in admin-logs API AuctionManager#adminRemoveItem(Player, UUID, Item, StorageType, boolean notify, boolean expire, boolean copy) and its overload with boolean updateInventory, InventoriesLoader#openInventory(Player, Inventories, int, boolean useOldInventories), LogType.ADMIN_REMOVE, PlayerCacheKey ADMIN_PLAYERS_DATA, ADMIN_PLAYERS_LOADING, ADMIN_PLAYERS_SORT, ADMIN_REMOVE_NOTIFY, ADMIN_REMOVE_EXPIRE, ADMIN_REMOVE_COPY and AdminPlayerDTO. Item#getReservationOwner, Item#setReservationOwner and Item#isReservedBy (the player who holds a purchase or removal confirmation on this server, reset when the listing goes back on sale). AuctionRemoveService#removeListedItem now only accepts a listing that is available: a listing in IS_REMOVE_CONFIRM can only be removed from the seller's own confirmation inventory Updated Sarah to version 1.27