Bukkit

Permission nodes for DarkTrace 0.1.8.1 and above

If the configuration entry "oppermissions" is set to true, ops have all DarkTrace-related permissions. Further even without any permissions system used it is possible to give players permissions with the list entries under permissions in the configuration. Add the player name to the desired list and the player can use th permission (Usually darktrace.mod and darktrace.all should suffice.).

The most important permission nodes are:

• darktrace.all
  Allows for using every command of DarkTrace, including erasing all data, removing players, saving, reloading.
• darktrace.mod
  Allows for everything related to viewing stats, suspicious entries, including digest. Does not allow for changing the data.

Mind that with oppermissions set to true in the configuration ops will have all permissions for DarkTrace.

Currently there is a node for each command, though some nodes are still subject to change, most permission nodes refer to a command.

Shortcut permissions:

• darktrace.all
  As stated above: all permissions
• darktrace.mod
  As stated above: permissions for viewing data, i.e.:
  help, info, stats, suspicious, browse, digest, cleanup, display

Commands for viewing the data:

• darktrace.help
  Show a list of commands. Later maybe more...
• darktrace.info
  Show info about internal settings.
• darktrace.stats
  Show the stats if a player.
• darktrace.suspicious
  Show suspicious entries. (demands darktrace.browse)
• darktrace.browse
  Necessary for browsing through suspicious entries and later stats entries as well, will probably be removed, because this is needed anyway and should be implied by stats/suspicious.
• darktrace.display
  For using the display command for individual display settings.

Administrative commands that do not affect the data:

• darktrace.cleanup
  Erase digested data from memory, like ratios and suspicious entries. This can be used to release some memory, just in case.
• darktrace.digest
  Force re-calculation of all ratios etc. for all players, this probably has no effect in additions to calling /suspicious, because /suspicious will recalculate changed entries anyway.
• darktrace.save
  Force saving the data to disk.

Administrative permissions/commands that affect the data:

• darktrace.enable
  Set DarkTrace to active
• darktrace.disable
  Set DarkTrace to inactive ( will not add anything to data).
• darktrace.remove
  Remove a player from the data.
• darktrace.erase
  Administrative: clear all data for instance.
• darktrace.reload
  Administrative: reload configuration, reload data