Bukkit

0.1.8.1 - beta

The efficiency of this approach is under review due to 1.0 changes: absence of total darkness, silk-touch enchantment !
Recommendation: Set ll-avg-min and ll-avg-max to the same value, rather near 2. Remove Netherrack and Soulsand, if too many people are tunneling through the dark looking for nether fortresses.

Player specific display options, permission support (PEX, Bukkit: Player.hasPermission(...) ), bugfixes, changed default configuration. Tested with RB 1337, RB 1317, RB 1060. Running on latest CB 1.0.0-R1.

NOTES:

• Some default settings have been changed. If you delete your old configuration file, you mighlose the experimental partition data, so better use copy and paste for individual entries (See default configuration: Documentation).
• You might want to set suspicious.break.min-freq entries explicitely, to have people mine a minimum number of blocks, before appearing as suspicious, potentially. The value for iron might be preset too low.

CHANGELOG
(0.1.8.1 beta)
- (add) Chat command /dtd or or /dt display for player specific display settings.
- (add) Player specific display options, plus load/save from file.
- (add) Permissions support: Pex, Bukkit: Player.hasPermission(...) - both configurable
- (add) Configuration entry display.hide-exp which is set to true in the default configuration.
- (add) Some default configuration entries for blocks to include: Netherrack, Soulsand, Mycelium and various min-frequ entries (50/100).
- (change) Some default configuration entries (ratios, other).
- (note) Non-player CommandSenders will have permission if they are op.
- (bugfix) Cancelled block break events are not counted anymore.
- (bugfix) mod permission works now.
- (bugfix) More configuration entries can be omitted without crashing DarkTrace on reload.
- (bugfix, minor) calling stats with a non existing number is now intercepted.
- (bugfix, minor) dt remove <player> stated that there is no entry (negation of intended behavior).
- (compat) Refactor to xyzCurrentConfig rather than xyzConfig due to Bukkit API additions/changes.
- (internals) Use getServer().getLogger().warning /info instead of System.out.println.
- (internals) Fake permissions: empty lists are not longer stored.

(0.1.7 beta)
- (bugfix) Players that don't have (configuration-based) permissions and are not op do not cause a stack-overflow (introduced in hot-feature addition).
- (bugfix, minor) console shows all entries by default (no browsing).

(0.1.6 beta)
- [DISPLAY AND BUGFIX UPDATE]
- (add) command shortcuts (ingame versions) for /dt... + (/+), - (/- ), stats (/dts, /st ), suspicious (/su).
- (add) fake permissions "all" for all and "mod" for just checking but not changing data/settings, "browse" for browsing through results.
- (add) dt cleanup command + regular cleanup at most every 4 minutes with the data saving.
- (add) Displaying suspicious players is now divided into report pages with numbered entries.
- (add) browsing commands: /dt ... "+", "-" , <browse-id>, <prefix>+"*" ,
- (add) for stats command: prefixes work as well, and report-id mappings for numbers, further names ending with "*" will be regarded as prefixes, like "123*".
- (add) configuration for display: max-entries, allow-prefixes, show-browse-ids.
- (add) some lowercase-sorting for player names with "dt suspicious".
- (add) add abbreviations "/dt su" for suspicious, "/dt st" for stats.
- (change) set partitions to 12x5 to cover 1 hour with equal intervals.
- (change) changed default light level settings slightly, as well as min-freq to 10.
- (bugfix) Light-level boundaries avg-min, avg-max, avg-dist are now correctly read from the configuration.
- (bugfix, minor) create default configuration: use default values instead of current (for LL-avg-min etc.).

BUGS:

• (minor) Wrong entry in configuration permission lists: clear - the permission is erase (darktrace.erase).
• (minor) The mod permissions do not contain darktrace.item
• (minor ) It seems that the configuratinon permission for display is missing (will not be read from configuration. Use mod instead, for people that may view but not modify stats/etc. If you use permissions, then darktrace.display will take effect.
• (minor) The experimental method seems to have broken, at least after changing the partitions (only the first sections gets filled with entries, which renders it useles). To fully disable it, remove the stats.break.interval.blocks entries. The default configuration hides these values from stats display.