@Junrall

Good point - i might have to put on more explanations...

Inside the [..] brackets you have the involved blocks, you can use the command '/dtd bn' (short for '/dt display bn') to always display the block names instead of the block ids. If you use block ids you can always check with '/dti <id>' (short for '/dt item <id>') what the name of the block is.

• N is the number of mined blocks.
• L is light level on mining those blocks.
  (It counts the maximally found light level next to a mined block, it is an average value).
• R is ratio.
  R[1/15] is the ratio of 1 vs 15, i.e. stone versus iron ore: N[1]/N[15] .

The "suspicious" output for /su (short for /dt su) will contain only those entries of players that fail a check versus the threshold that is given in the configuration.

The default values might need adjustment, usually a suspicious entry is something to look further into or to adapt the configuration, like setting the min-frequ entry to a higher value for a specific block, so people need to mine some more before they can appear in the suspicious list.

In this case the suspicious output "L[15]=.0 R[1/15]=1.31" states that the player has mined all iron ore at an average light level of 0, i.e. total darkness (15 would be more like sunlight). In addition the player has mined only 1.31 stone blocks per iron ore block, which is a pretty good ratio, it is hard to tell if it is too good, for you can find iron in surface near caves. Judgement of light levels is a matter of taste, often people turn up brightness, but in most cases mining in darkness would be xrayers or light-cheaters. In such case they would also mine other blocks in darkness, that is why more kinds are included in the configuration, but you can fully customize those.

However... in this case you see both coal and iron ore are mined in darkness, but in such small numbers, that one can not reliably tell what would be the case here - the player probably just took a night out (or a cave) to find some stuff and did not place torches. So in this case you could adjust or add to a higher number for min-frequ for iron and coal in the configuration, like 50 or even 100. Still you could keep an eye on that player to see if the next suspicious entry will be diamond for instance.

You can use '/st <number>' to quickly see the stats for a player listed in the /su page which has entries like '1 dagobert R[1/56]=0.0' then '/st 1' shows the stats of dagobert.

In addition i would recommend to remove the entries now and then, just to be able to track their current behavior better (mining vs. construction of mob-traps or subways). Often the "early stats" can give a good hint about (careless) xrayers, if you use ore-break notification and maybe admins sneaking up on players, then checking stats on breaking (many) ores can help and quickly decide to directly check out what he player is doing. If you want less work for admins you can let them do a little xray and just check those with really bad ratios - or you use an obfuscation plugin like Orebfuscator, if your server is powerful enough and if it is compatible with your setup.

If you remove a single player like '/dt remove dagobert' then his stats will be added to the removed players log. Later DarkTrace might allow comparing those entries, but currently it would involve some moe work.

You can remove all entries with /dt erase all, which is recommendable from time to time - suspicious entries get lost, so this should currently be done, if there are no entries that need special interpretation.

In any case one should not be too fast to ban players just because their ratio is too good or because they mined some blocks in darkness. One should consider how many blocks have been mined (if necessary: adapt the configuration for min-freq!), and depending on what material it is, also if they have mined other blocks in darkness too. Good cave miners can now and then reach a ratio below 16 for stone/diamond, if you just started counting - if you have mcmmo you might even have people one of which will mine all the diamond while the other just helps discovering those.

@Endimmion Thank s for notice ...
I am running it on the latest dev builds usually, currently: 1847.

@Endimmion

Did you set the configuration entry under 'use-permissions' for 'bukkit-perms' to true? Permissions should work...

Then it should work. Otherwise you could your add the player names to one of the lists for the configuration section 'permissions', preferably to 'all' or 'mod' for the easiest way to add people.

/dt reload should do it then.

@Endimmion

I just made a quick addition, to allow for display of block names (0.2.1), it does not work on the console, because the display configuration for the console is fixed and can not yet be changed, neither saved.

In-game you can switch to block names with /d bn or to ids with /d id ...

It is possible to set that individually for sats, suspicious and info (try just /d for reference).

(If /d is used by another plugin , then: /dtd ... or /dt d ...)

@Endimmion

That would be easy to program, though it would make some display really crowded if you use more blocks.

So if i add this, i will have to make it configurable where exactly names are used (everywhere, on stats display, on suspicious display).

I will create a ticket for it and most probably add it to the next version.

Till then you might have /dti <item> to show bukkit-name and id for a given ... id or bukkit-name for the item.

@ctharvey

Ok, i guess i will upload a new version in a couple of hours, which then will be available this weekend, hopefully.
It will contain a bugfix for the light level configuration values not being applied correctly (sorry for that invconvenience...), few command shortcuts and some options to not display everything at once.

Edit: Decided to add a report-view, for faster result iteration/checking.

@ctharvey

Allright, i will first add options for displaying the data / selecting which to display rather than disabling using lightlevels.

Actually i thought of smaller servers at first, but certainly the idea where this should be going would clearly fit bigger servers as well.

So i will add "something" tomorrow for adjusting the display (focus on LL/R/IN , some report-like view with pages of a certain size, writing reports for players with a certain prefix or so.).

This will take another day (so far for quick) due to being held up today and my intention to sleep this night. Let me know if it is time critical (The Bukkit team occasionally is very fast but not always - on approving files for download...), i might send an updated version slightly faster than it will be available here - or if you can fall back to the console - on "/dt suspicious" only the "suspicious" values are shown anyway, though the chat output might somewhat better readable.

@TheDarthNix

Oh ok :)

That will probably be a quick update then.