Advertisement
Tirco

HeadHunter Default Config

Mar 19th, 2021 (edited)
1,318
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
YAML 2.75 KB | None | 0 0
  1. ###########
  2. ##Options##
  3. ###########
  4. setting:
  5. ##Should we display messages to console?
  6.     debug: false
  7.  
  8. ##Should we overwrite this config if there's an update to it?
  9.     update_overwrite: true
  10.    
  11. ##Announce debugs to admins? headhunter.admin permission node.
  12. ##Can be turned on temporarily with the /headhunteradmin debug command
  13.     debugtoadmins: false
  14.  
  15. ##Should the heads emit particles?
  16.     particles: true
  17.  
  18. ##Should we announce to all players when a player has found all heads?
  19.     announcefindingall: true
  20.  
  21. ##How often should we save the head data? (in minutes)
  22. ##Heads are also saved when a player leaves the server.
  23.     autosaveinterval: 15
  24.  
  25. ## Automatically delete users that haven't been on the server in a while:
  26. ##How long ago should a player have logged in before we purge their data? (Months)
  27. ##0 = never purge.
  28.     purgeafter: 3
  29. ##Should only players that have no progress get purged from the database?
  30.     onlypurgeemptyplayers: true
  31.  
  32. ##Do you need the headhunter.basic permission to unlock heads?
  33.     huntingrequiresperm: false
  34.  
  35. ##How many players should our top list store? -- Stored in Heads.yml
  36. ##
  37.     topamountsaved: 20
  38.    
  39. ##Should we run commands when heads are found (if a command is set?)
  40. ##These commands are run from console.
  41.     commandOnHeadFound: true
  42. ExtraRewards:
  43. ##These rewards are added when the player has found N amount of heads.
  44. ##It can run multiple commands. The commands are run from console.
  45. ##Be careful with give commands, as the plugin does not check if their inventory is full.
  46. ##If the player "ufinds" a head these can trigger again. (Only happens if admins do stuff)
  47. ##You can also use the "ALL" key, which will trigger when all heads have been found.*
  48. ##Arguments: <playername>, <id>, <found>
  49.     1:
  50.        - msg <playername> Nice! You have collected <found> head!
  51.         - msg <playername> I'll be watching you.
  52.     10: []
  53.     ALL: []
  54. ############
  55. ##Messages##
  56. ############
  57. messages:
  58. ##What should the plugins prefix be?
  59.     prefix: "&3[&bHeadHunter&3] "
  60. ##How should we announce a player that has found all skulls?
  61. ##Announcefindingall must be set to true.
  62. ##<found>, <max>, <playername>
  63.     announcefindingallmessage: "&6<playername>&f has found all &c<max>&f heads!"
  64.  
  65. ##What should we tell a player that is hunting for heads?
  66. ##<found>, <max>, <playername>, <idfound>, <headname>
  67.     countmessage: "&aYou just found &f<headname>&a. In total you have found &6<found>&f/<max> &aheads."
  68.     countcommandmessage: "&aYou have found &6<found>&a out of &6<max>&a heads."
  69.    
  70. ##What should we tell a player that already found a head?
  71. ##<found>, <max>, <playername>, <idfound>, <headname>
  72.     repeatmessage: "&aYou have already found this head. &aID: &6<idfound>&a, Name: &6<headname>"
  73.  
  74.  
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement