Advertisement
Guest User

config seriousviote

a guest
Mar 6th, 2018
91
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.01 KB | None | 0 0
  1. config:{
  2.  
  3. config-version: "4.0"
  4.  
  5. #//Variables - {player} : the person who voted
  6.  
  7. #// {rewards} : The list of random rewards the player received
  8.  
  9.  
  10.  
  11. #//Leaving this empty will disable messages from being shown publicly: Supports color and formatting codes
  12.  
  13. broadcast-message: "&4{player} &eJust Voted! He got {rewards}! If you like it here show your support! &6run &5/vote"
  14.  
  15.  
  16.  
  17. #//-1 will have the system select a number of rewards between rewards-min and rewards-max;
  18.  
  19. random-rewards-number: 1
  20.  
  21. rewards-min:1
  22.  
  23. rewards-max:3
  24.  
  25. #// Under random You can set The tables you would like to use with weights in front for there to be a random chance of choosing from a table.
  26.  
  27. #//In the case that there is only one table it will be chosen.
  28.  
  29. vote-reward:{
  30.  
  31. set:["candy"]
  32.  
  33. }
  34.  
  35. //# Tables are groups of rewards which work as a weighted system. Below are two small examples, but they are very simple and not too elaborate.
  36.  
  37. //# Much like the rewards above, the Tables are re-usable. As a matter of fact the Tables are needed by all "Random" rewards areas.
  38.  
  39. //# They are pretty basic to use, Give it an id (no two id's should be the same) and then make a list with alternating weights and reward ids
  40.  
  41. //# The weights are pretty simple to use, the higher number a reward has the likelier it is to be chosen. in the TableCommon below 'money1' has
  42.  
  43. //# 25/125 chances to be chosen. You can use this to make common, rare , and super rare (etc...) tables which can be used together when you
  44.  
  45. //# want more control over what is being given out.
  46.  
  47.  
  48.  
  49. Tables {
  50.  
  51.  
  52.  
  53. TableCommon: [
  54.  
  55. "70", "tomahawk",
  56.  
  57. "25", "money1"
  58.  
  59. ]
  60.  
  61.  
  62.  
  63. TableYearly: [
  64.  
  65.  
  66.  
  67. "1", "gold2"
  68.  
  69. ]
  70.  
  71.  
  72.  
  73. TableClaims: [
  74.  
  75. "1", "claimblocks"
  76.  
  77. ]
  78.  
  79.  
  80.  
  81. TableMonthly: [
  82.  
  83. "1", "claimblocks"
  84.  
  85. ]
  86.  
  87. TableWeekly:[
  88.  
  89. "1", "money1"
  90.  
  91. ]
  92.  
  93.  
  94.  
  95. }
  96.  
  97.  
  98.  
  99.  
  100.  
  101. //#Each Reward Requires an id "which is the descriptor / identifier such as tomahawk: in the tomahawk reward
  102.  
  103. //# After each Reward requires a name key, and a reward key
  104.  
  105. //# The value for name is just a text String (This can be used to Call it out in the broadcast built in)
  106.  
  107. //#The value for the rewards string is a list of strings. Each String should be a full command and can include the standard variables
  108.  
  109. //# Each new command string needs a comma before it. If your command requires quotations make sure to add escape characters
  110.  
  111. //#-----i.e ----"hello how "are" you"---- is not valid the string should be escaped as follows
  112.  
  113. //# ----"hello how \"are\" you---- The backslash allows the " to be escaped to be ignored by the parser
  114.  
  115. //#
  116.  
  117. //# Every single Reward should have it's id be unique, i.e there should not be more than one tomahawk ect... The name of the items can
  118.  
  119. //# be duplicated though, so a tomahawk1, and a tomahawk2, can have "Steel Tomahawk" as the name"
  120.  
  121.  
  122.  
  123. Rewards {
  124.  
  125.  
  126.  
  127. candy: {
  128.  
  129. name: "Rare Candy"
  130.  
  131. rewards: [
  132.  
  133. "give {player} 4253 2"
  134.  
  135. ]
  136.  
  137. }
  138.  
  139.  
  140.  
  141. yearly: {
  142.  
  143. name: "Yearly Reward"
  144.  
  145. rewards: [
  146.  
  147. "give {player} minecraft:diamond 5",
  148.  
  149. "say {player} is really frk'n dedicated"
  150.  
  151. ]
  152.  
  153. }
  154.  
  155.  
  156.  
  157. gold2: {
  158.  
  159. name: "Gold Ingots"
  160.  
  161. rewards: [
  162.  
  163. "give {player} minecraft:gold_ingot 2"
  164.  
  165. ]
  166.  
  167.  
  168.  
  169. }
  170.  
  171.  
  172.  
  173. money1: {
  174.  
  175. name: "A little cash"
  176.  
  177. rewards:[
  178.  
  179. "adminpay {player} 100"
  180.  
  181. ]
  182.  
  183. }
  184.  
  185.  
  186.  
  187. claimblocks: {
  188.  
  189. name: "50 Claim Blocks"
  190.  
  191. rewards: [
  192.  
  193. "acb {player} 50"
  194.  
  195. ]
  196.  
  197. }
  198.  
  199.  
  200.  
  201. banana: {
  202.  
  203. name: "Banana"
  204.  
  205. rewards: [
  206.  
  207. "say {player} is a banana"
  208.  
  209. ]
  210.  
  211.  
  212.  
  213. }
  214.  
  215.  
  216.  
  217.  
  218.  
  219.  
  220.  
  221. }
  222.  
  223.  
  224.  
  225. #//This Message will Show above the Links.
  226.  
  227. vote-sites-message: "&6Thank You! Below are the places you can vote"
  228.  
  229.  
  230.  
  231. #// Your website voting links, displayed by /vote, these support color formatting. Creates clickable links.
  232.  
  233. #//seriousvotes.commands.vote
  234.  
  235. vote-sites:[
  236.  
  237. "&1http://minecraftservers.org/server/486711",
  238.  
  239. ]
  240.  
  241.  
  242.  
  243.  
  244.  
  245. #// The Milestones Module Requires a Mysql System Setup
  246.  
  247. database:{
  248.  
  249. hostname: "127.0.0.0"
  250.  
  251. port: "3306"
  252.  
  253. name: "COT_SeriousVote"
  254.  
  255. prefix: "SV_"
  256.  
  257. username: "root"
  258.  
  259. password: "You need a password"
  260.  
  261. }
  262.  
  263.  
  264.  
  265. #// Currently we have monthly weekly and yearly, put what you need in the set rewards. these commands will be run
  266.  
  267. #// When a player votes X amount of days in a row, 365,30, 7
  268.  
  269. dailies: {
  270.  
  271. enabled: false
  272.  
  273.  
  274.  
  275. weekly: {
  276.  
  277. message: "This person has earned a 7 day in a row Reward!"
  278.  
  279. set:[
  280.  
  281. "give {player} 4253 4"
  282.  
  283. ]
  284.  
  285. }
  286.  
  287. monthly: {
  288.  
  289. message: "This person has earned a monthly vote Reward!"
  290.  
  291. random:[
  292.  
  293. "27", "TableMonthly"
  294.  
  295. ]
  296.  
  297. set:[
  298.  
  299. "say This is a set Monthly {player} Reward",
  300.  
  301. "acb {player} bananaphone"
  302.  
  303. ]
  304.  
  305. }
  306.  
  307. yearly: {
  308.  
  309. message: "This person has earned a one year of straight voting reward"
  310.  
  311. random:[
  312.  
  313. "27", "TableYearly"
  314.  
  315. ]
  316.  
  317. set:[
  318.  
  319. "say This is a set Yearly {player} Reward",
  320.  
  321. "say Crap, you must play alot"
  322.  
  323. ]
  324.  
  325. }
  326.  
  327. }
  328.  
  329.  
  330.  
  331.  
  332.  
  333. milestones: {
  334.  
  335. enabled: false
  336.  
  337. #//place the number of votes you'd like to enable milestones for inside the brackets separated by commas.
  338.  
  339. records-enabled:["100","1","37"]
  340.  
  341. #// The setup for these is just the same as the normal voting. The tables must be defined in the table section in order for them to be used.
  342.  
  343. records:{
  344.  
  345. 100:{
  346.  
  347. message: "&4{player} has voted for a 100th time in a row!"
  348.  
  349. random:[
  350.  
  351. "27", "claimblocks"
  352.  
  353. ]
  354.  
  355. set: []
  356.  
  357. }
  358.  
  359. 1:{
  360.  
  361. random:[]
  362.  
  363. set: ["one command","two command", "three command", "floor"]
  364.  
  365. }
  366.  
  367.  
  368.  
  369. }
  370.  
  371.  
  372.  
  373. }
  374.  
  375. }
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement