rbuy 2.4.1

Details

  • Filename
    rbuy.jar
  • Uploaded by
  • Uploaded
    Aug 27, 2013
  • Size
    86.25 KB
  • Downloads
    636
  • MD5
    fec61e63cab0a26b25aa82be9e28404b

Supported Bukkit Versions

  • 1.6.2

Changelog

2.4.1

  • Added filters for regions to have different values for max-buy and time-count-buy. (filters: world: region: max-buy/time-count-buy), use __global__ for region to have it count for a world.
  • Add /rinfo sign: Fills in information about the region offered for sale, if the sign is placed on it.
  • Slight internal API changes.
  • Compiled and tested with 1.6.2.
  • Users of swgt must update that too.
  • More docs might follow up.

Might work with some older builds as well.


The configuration has been extended by one entry since 0.1.1 - see main page for reference.

Requirements:

  • WorldGuard
  • WorldEdit

NO WARRANTY WHATSOEVER
I have done a range of tests, and it has been running on servers as expected, still this was a more or less quickly made plugin. Yet there have not been reported any exploits or serious errors with the current version(s).

BUGS:

  • PluginLibSharedLibrary: you must add a dummy plugin name to the list, setting to an empty list like [] will lead to default entries being set (bug in CraftBukkit).
  • Maybe: It might happen that rbuy sets the economy interface more often than needed during enabling. [No harm.]

NOTES:

  • Logging of transactions is done in the plugins/rbuy/runtime.yml file, they are available for the period specified in the configuration (in days), preset is 30 days.
  • Listing nearby regions iterates over all regions by now (due to having failed to use WorldGuards deprecated functionality for that), so this is probably not fit for a large number of regions for sale. To limit this there is configurable limits.
  • It is possible to add regions to the datafile manually, however you should disable rbuy before calling "rreload", bcause rbuy will save data before reloading configuration and data.
  • Each manipulation leads to saving the data, so the full transactions and region offers will be written to the file for each change. This might lead to small performance issues if used by many people with many offers/transactions.