Bukkit

0.10.0 - beta/dev [1.2.3 / 1.2.4]

Fix for WorldGuard not being recognized for some constellations. Added (experimental) similar to have-inside: have-outside, add-enter, add-exit, remove-enter, remove-exit

Successful Tests with:

• CB 2117
• PermissionsEx 1.19.1
• bPermissions 2.7.8 (older version: few local tests)
• bPermissions 2.4 (older version: very few local tests)
• WorldGuard 5.5.2

Changes:

(0.10.0) - (NOTE) Changing filter or ignore permissions might only take effect after cache lifetime expiration, due to internal caching of some permissions (do net set too low currently, do test performance if you change this setting).
- (add) Logging of some errors on severe level now, plus using a minimum delay (configurable in ms: errors.log.min-delay).
- (bugfix) WorldGuard is now set and used, if WorldGuard did not accept a Location.
- (CHANGE) The filter permission now gets checked for removing permdefs too.
- (add) New group uses: have-outside, add-enter, remove-exit, add-exit, remove-enter
- (refactor) Changed packages for some classes, added extra

(0.9.2)
- (bugfix) Removed empty entries from plugin.yml .

(0.9.1)
- (add) Rectangular confinement support.
- (add) Add VehicleEnterEvent for checking position and border calculation.
- (add) Add VehicleMoveEvent and VehicleEnterEvent for border calculation
- (adjust) Make listener methods final.
- (refactor) checkConfinement method

(0.9.0)
- (add) world specific settings for lazy-dist and confine
- (add) confine world settings (limit moving range of players, lazy-dist applies).

(0.8.1)
- (update) compatlayer 0.1.0

(0.8.0)
- (refactor) Switch to new Event system. [removed warnings]

(0.7.2)
- (add) Hot fix for compatibility with older WorldGuard versions.

(0.7.1)
- (add) re-add save-on-check/checkout (saveChanges)

The new group uses (have-outside etc.) are not tested individually, however some refer to internals that have already been in use since the first version and should work in general.

Still the behavior of RSP removing permissions on checkout of players might conflict with some of the new uses (test if they really work, if you intend to use them!).

Currently RSP uses some caching of permissions internally, so manipulating ignore/filter permissions by RSP itself can lead to unintended effects, because changes might only be recognized after expiration of cache lifetime. This caching might be removed with one of the next versions anyway.