Documentation/Commands
Command refernce for DarkTrace 0.1.8.1 and above
The root command is /dt , or if that is taken by another plugin: /darktrace.
I refer to the commands as /cmd , as if typed in chat. The commands should work for the console too, just without the first '/'. In order to separate commands with multiple arguments from the rest of the text, sometimes i will write them like '/dt su'.
All command functionality can be accessed by using the root command and the command name as the first argument, still there exist shortcuts and command aliases for faster access. like '/dt su' and '/su' instead of '/dt suspicious'. Some command shortcuts like '/+' also have an alias with double slash, just in case. I will still refer to the standard command and not to the abbreviation commands.
The permission nodes are stated in the tables as well, mind that darktrace.all is the permission to grant everything, while darktrace.mod allows for viewing without changing the data.
For more detailed infromations about permission nodes see: Permissions
Commands by category:
The tables state the command aliases, permission node, description.
| General information | ||
|---|---|---|
| /dt help | darktrace.help | Show a list of possible commands. Later there might be help topics. |
| /dt info | darktrace.info | Show general information about the configuration settings. |
| /dt item <item> 0.1.9: /dt i <item> /dti <item> | darktrace.item | Give name and block id for the specified item. <item> can be a number (block-id) or the name as given in: http://jd.bukkit.org/apidocs/org/bukkit/Material.html This is not case-sensitive, some aliases like gold, diamond, iron are defined in DarkTrace, for the ores. |
| Viewing data | ||
| /dt suspicious /dt su /su | darktrace.suspicious | View a list of suspicious players. The number of entries of a page is defined by the configuration setting max-entries and can be changed individually with the display command. This also maps player names to numbers shown in the display, so their stats can be accessed with '/dt stats <number>'. |
| /dt stats /dt st /dts /st | darktrace.stats | Show average stats for all players (additive) - This is subject to change, it might not be useful, because values vary too much for builders, mining pros and everything in between. To view the stats of an individual player, see below. |
| /dt stats <entry> | darktrace.stats | View the stats for a certain player. <entry> can be the player name or a prefix of a player name. If <entry> it is a number, this will display the stats for the player mapping from 'suspicious' entries. To show the stats of a player whose name starts with a number add a '*' (asterix) to the first letters like '/dt stats 42*', so DarkTrace will treat is as a player name prefix and not as a number. |
| /dt + /+ | darktrace.browse | Show next page for suspicious entries, this will begin from the start if the end was reached. |
| /dt - /- | darktrace.browse | Show the previous page for suspicious entries, this will go to the end, if the first entry was shown. |
| /dt <entry> | darktrace.browse | Show the page for suspicious entries from <entry> on. <entry> can be a number or a prefix of a name ending with '*' (asterix). |
| /dt display /dt d /dtd | darktrace.display | List the commands for altering the individual display settings. These settings only affect the display settings for player that calls it. |
| /dt display me <num> | darktrace.display | Set the number of entries per page for display of suspicious entries. <number> can be anything from 1 to 50, thopugh more then ten is not recommended with the default client. |
| /dt display <spec> ... | darktrace.display | Change the per player display settings. There can be more than one <spec> arguments, as below: sl - Show light levels in stats. hl - Hide light levels in stats. sexp - Show experimental results in stats. hexp - Hide experimental methods in stats. sempty - Show empty suspicious entries (just the name) hempty - Hide empty suspicious entries. sa - Show all (of the other options). ha - Hide all (of the other options). bn - Show block names. bnst - Show block names in stats bnsu - Show block names in suspicious display. bnin - Show block names in info. id - Show block ids (not names). idst - ... idsu - ... idin - ...) |
| Performance related / Administrative | ||
| /dt digest | darktrace.digest | Force update of the temporary stats entries for all players kept in memory, as well as average stats over all players. |
| /dt digest clear | darktrace.digest | Delete temporary stats entries from memory created on calling digest or stats or suspicious. (Subject to removal) |
| /dt cleanup /dt cl | darktrace.cleanup | Delete all temporary entries, such as digests, stats, name-mappings. This releases some memory. |
| Administrative | ||
| /dt enable | darktrace.enable | Set DarkTrace to active, i.e. process block breaks and such, as given by configuration. |
| /dt disable | darktrace.disable | Set DarkTrace to inactive, i.e. stop counting block breaks und such. |
| /dt reload /dt reload config | darktrace.reload | Reload the configuration and apply it. This could affect the data if certain methods or blocks are not to be processed anymore. |
| /dt reload data | darktrace.reload | Reload the data file(s). This leads to reloading the data for the players from the file(s). Thus the data or changes in memory will be lost. |
| /dt reload all | darktrace.reload | Reload both configuration and data (see above). |
| /dt save | darktrace.save | Force saving the data to disk. |
| /dt remove <player> | darktrace.remove | Remove a player from the data. This might save the changed data to disk immediately (subject to change). |
| /dt erase all | darktrace.erase | Erase all data, this will save back to disk (empty file). |
Comments