Advertisement
Guest User

Untitled

a guest
Oct 12th, 2018
249
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.86 KB | None | 0 0
  1. # Seen Plugin Configuration -- Authors: Nibblesnow (Lead), Gertius
  2. # Contact us via @Nibblesnow#5551 / @Gertius#8021 on Discord if you have any issues or questions.
  3.  
  4. # Database Information - MySQL
  5. database:
  6. host: localhost
  7. port: 3306
  8. database: seen
  9. username: root
  10. password: password
  11. table:
  12. playerdata: playerdata
  13. account: account
  14.  
  15. # What should the date/time format be when /seen'ing a player?
  16. # For more information about how to customize this pattern visit:
  17. # https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html
  18. dateTimeFormat: 'MMMM d, y hh:mm a'
  19.  
  20. # How many player accounts should be able to connect at one time from an IP?
  21. # This works across all of your network and is not server specific. If you only
  22. # have one server this will be taken as a network too. Keep as -1 for no limit.
  23. # Changing this value to 0 means nobody except seen.maxlimit.bypass can connect.
  24. # It is advised to keep this number uniform across your network.
  25. maximumNumberAccounts: -1
  26.  
  27. # Should the plugin hook into LiteBans and provide support?
  28. # This will add colour coding (red = banned, green = unbanned, gray = offline) on
  29. # Affiliated IGNs list and will also use correct ban methods instead of allowing
  30. # Bukkit to execute the commands itself.
  31. allowLiteBansSupport: false
  32.  
  33. # Should last IP and other data be updated to new IP address when a player logs?
  34. # Change to false in lobby servers especially if you use two-factor to prevent
  35. # exploits in which players can get falsely banned or accused.
  36. updateDataOnLogin: true
  37.  
  38. # This can be left true even if updateAddressOnLogin is false since the account would
  39. # be logged under the new IP location and not the current so this may help you to try
  40. # and find who is hacking who's account.
  41. logAccountOnLogin: true
  42.  
  43. # Should data server-wide (not network-wide) be saved onto local disk?
  44. # This allows you to see when a player was last seen LOCALLY and if they have ever
  45. # connected to the server you are currently on.
  46. saveLocalData: true
  47.  
  48. # Should A LOT more information be displayed to Console?
  49. # This should be used for testing purposes only since sufficient information is already
  50. # printed to the Console display.
  51. debug: false
  52.  
  53. # All plugin messages. All can be edited and available variables can be found on the Google Doc.
  54. messages:
  55. no-permission: '&cYou don''t have permission to use this command.'
  56. player-not-found: '&cUnable to find player %player%'
  57. altban:
  58. usage: '&cIncorrect Usage: /%command% <player|UUID> [time] <reason>'
  59. fakealtban:
  60. usage: '&cIncorrect Usage: /%command% <player|UUID> [time] <reason>'
  61. iphistory:
  62. usage: '&cIncorrect Usage: /%command% <player|UUID>'
  63. iplookup:
  64. usage: '&cIncorrect Usage: /%command% <IP>'
  65. namehistory:
  66. usage: '&cIncorrect Usage: /%command% <player|UUID>'
  67. seen:
  68. usage: '&cIncorrect Usage: /%command% <player|UUID>'
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement