0.1.3 - beta

Details

  • Filename
    rbuy.jar
  • Uploaded by
  • Uploaded
    Jan 9, 2012
  • Size
    35.09 KB
  • Downloads
    429
  • MD5
    39f2c629a14a6d47dc42c44b1cf06736

Supported Bukkit Versions

  • CB 1.1-R3
  • CB 1.1-R1

Changelog

0.1.3 - beta

Running on latest 1.1/CB 1914 currently, latest WorldGuard, WorldEdit, admittance - it might be compatible with earlier versions as well.

Adding support for selling to the members of a region (exclusively), with a config flag. Plus added a convenience option for rremove: set new owners of the removed regions.


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

Requirements:

CHANGELOG:
(0.1.3)
- (add) Allow selling to members (by config flag)
- (bugfix) respects oppermissions for unowned regions now (ops would always have been able to sell those).
- (internals) Added compatlayer 0.0.6 for configuration.

(0.1.2)
- (add) option for rremove: x:own:<player> sets the specified owner(s) as new exclusive owners
- (internals) include WALL_SIGN on checks.
- (internals) Add softdepend for WordlGuard, WorldEdit, admittance

NO WARRANTY WHATSOEVER
I have done a range of tests, but am still unwilling to be responsible for region losses or money transfers failing, crashing servers (unlikely), and similar.

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.