nfell2009

Config

May 6th, 2014
202
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.43 KB | None | 0 0
  1. databases:
  2. # Databases to store variables in. These can either be used as a simple one-server-storage
  3. # where variables are written constantly but only read at server start,
  4. # or as a connection between multiple servers by monitoring the database(s) for changes.
  5. #
  6. # You can define as many databases as you want, just make sure to choose a distinct name for each one, and don't forget to set all options correctly.
  7. #
  8. # To be able to use a database you'll need to download the plugin 'SQLibrary' from http://dev.bukkit.org/server-mods/sqlibrary/files/
  9. # and install it in your server's plugin directory like other plugins.
  10. #
  11. # Please note that '/skript reload' will not reload this section, i.e. you'll have to restart Skript for changes to take effect.
  12.  
  13. # Each database definition must be in a separate section. You can choose any name for the sections, as long as it's not already used.
  14. database 1:
  15. # an example database to describe all possible options.
  16.  
  17. type: none
  18. # The type of this database. Allowed values are 'CSV', 'SQLite', 'MySQL' and 'disabled'.
  19. # CSV uses a text file to store the variables, while SQLite and MySQL use databases, and 'disabled' makes Skript ignore the database as if it wasn't defined at all.
  20.  
  21. pattern: .*
  22. # Defines which variables to save in this database.
  23. # This pattern uses Regex syntax, e.g. use 'db_.*' (without the quotes) to store all variables prefixed with 'db_' in this database,
  24. # or use '.*' (the default value) to store all variables here (recommended for the last database in this list, as otherwise some variables might not be saved).
  25. # Please note that variables are only stored in one database, and databases are checked from top to bottom,
  26. # e.g. if a variable matches the topmost database's pattern it will be saved there and nowhere else.
  27. # BTW: Patterns are checked in a separate thread, i.e. your server likely won't run slower when using complicated patterns.
  28.  
  29. monitor changes: false
  30. monitor interval: 20 seconds
  31. # If 'monitor changes' is set to true, variables will repeatedly be checked for updates in the database (in intervals set in 'monitor interval').
  32. # ! Please note that you should set 'pattern', 'monitor changes' and 'monitor interval' to the same values on all servers that access the same database!
  33.  
  34. # == MySQL configuration ==
  35. host: localhost# Where the database server is located at, e.g. 'example.com', 'localhost', or '192.168.1.100'
  36. port: 3306# 3306 is MySQL's default port, i.e. you likely won't need to change this value
  37. user: root
  38. password: pass
  39. database: skript# The database to use. Skript will automatically create a table 'variables21' in this database if it doesn't exist
  40. # (If the table exists but is defined differently that how Skript expects it to be you'll get errors and no variables will be saved and/or loaded)
  41.  
  42. # == SQLite/CSV configuration ==
  43. file: ./plugins/Skript/variables.db
  44. # Where to save the variables to. For a CSV file, the file extension '.csv' is recommended, but not required, but SQLite database files must end in '.db' (SQLibrary forces this).
  45. # The file path can either be absolute (e.g. 'C:\whatever\...' [Windows] or '/usr/whatever/...' [Unix]), or relative to the server directory (e.g. './plugins/Skript/...').
  46.  
  47. backup interval: 2 hours
  48. # Creates a backup of the file every so often. This can be useful if you ever want to revert variables to an older state.
  49. # Variables are saved constantly no matter what is set here, thus a server crash will never make you loose any variables.
  50. # Set this to 0 to disable this feature.
  51.  
  52.  
  53. sdb:
  54. # Main database for QuartzCraft
  55. type: MySQL
  56.  
  57. pattern: synced_.*# this pattern will save all variables that start with 'synced_' in this MySQL database.
  58.  
  59. host: localhost
  60. port: 3306
  61. user: #####
  62. password: #####
  63. database: #####
  64.  
  65. monitor changes: true
  66. monitor interval: 20 seconds
  67.  
  68. SQLite example:
  69. # An SQLite database example.
  70.  
  71. type: disabled# change to line below to enable this database
  72. # type: SQLite
  73.  
  74. pattern: db_.*# this pattern will save all variables that start with 'db_' in this SQLite database.
  75.  
  76. file: ./plugins/Skript/variables.db
  77. # SQLite databases must end in '.db'
  78.  
  79. backup interval: 0# 0 = don't create backups
  80. monitor changes: false
  81. monitor interval: 20 seconds
  82.  
  83. default:
  84. # The default "database" is a simple text file, with each variable on a separate line and the variable's name, type, and value separated by commas.
  85. # This is the last database in this list to catch all variables that have not been saved anywhere else.
  86. # You can modify this database freely, but make sure to know what you're doing if you don't want to loose any variables.
  87.  
  88. type: CSV
  89.  
  90. pattern: .*
  91.  
  92. file: ./plugins/Skript/variables.csv
  93.  
  94. backup interval: 2 hours
  95.  
  96. # PS: If you don't want some variables to be saved in any database (e.g. variables that contain an %entity% which usually despawn when the server is shut down)
  97. # you can modify the last database's pattern to not match all variables, e.g. use '(?!x_).*' to match all variables that don't start with 'x_'.
  98. # Be very cautious when doing this however as unsaved variables cannot be recovered after the server has been stopped.
  99. # I recommend to use a single character to denote unsaved variables (similar to local variables' '_'), e.g. '-', in which case the last database's pattern should be '(?!-).*'.
Advertisement
Add Comment
Please, Sign In to add comment