0.3.0 - beta

Details

  • Filename
    rbuy.jar
  • Uploaded by
  • Uploaded
    Apr 30, 2012
  • Size
    62.38 KB
  • Downloads
    261
  • MD5
    cc05fa66d1c3d45bd8297a81426fe62f

Supported Bukkit Versions

  • 1.2.5
  • 1.2.3

Changelog

0.3.0 - beta [1.2.3 ... 1.2.5]

Minor update: allow <prefix>* instead of the full region name on signs, adjusted internals for better API usage.

(0.2.0) This version no longer depends on admittance for economy !

You now have the economy section in the configuration, stating lists for exclude-plugins, include-plugins, load-plugins to allow to ensure which economy plugins is used (and load it before rbuy is done enabling).

Might work with some older builds as well, probably down to 1.1.


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

Requirements:

  • WorldGuard
  • WorldEdit

CHANGELOG:
(0.3.0)
- (add) Allow a region name prefix on signs with <prefix>*
- (adjust) Change visibility of inner classes.

(0.2.0)
- (refactor) Add economy mixin to not depend on admittance anymore.
- (refactor) renamed some methods.

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:

  • 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.