· 6 years ago · Nov 20, 2019, 01:16 AM
1# ==== Variables ====
2
3databases:
4 # Databases to store variables in. These can either be used as a simple one-server-storage
5 # where variables are written constantly but only read at server start,
6 # or as a connection between multiple servers by monitoring the database(s) for changes.
7 #
8 # 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.
9 #
10 # To be able to use a database you'll need to download the plugin 'SQLibrary' from https://dev.bukkit.org/projects/sqlibrary/files
11 # and install it in your server's plugin directory like other plugins.
12 #
13 # Please note that '/skript reload' will not reload this section, i.e. you'll have to restart Skript for changes to take effect.
14
15 # 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.
16 database 1:
17 # An example database to describe all possible options.
18
19 type: disabled
20 # The type of this database. Allowed values are 'CSV', 'SQLite', 'MySQL' and 'disabled'.
21 # 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.
22
23 pattern: .*
24 # Defines which variables to save in this database.
25 # This pattern uses Regex syntax, e.g. use 'db_.*' (without the quotes) to store all variables prefixed with 'db_' in this database,
26 # 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).
27 # Please note that variables are only stored in one database, and databases are checked from top to bottom,
28 # e.g. if a variable matches the topmost database's pattern it will be saved there and nowhere else.
29 # BTW: Patterns are checked in a separate thread, i.e. your server likely won't run slower when using complicated patterns.
30
31 monitor changes: false
32 monitor interval: 20 seconds
33 # If 'monitor changes' is set to true, variables will repeatedly be checked for updates in the database (in intervals set in 'monitor interval').
34 # ! Please note that you should set 'pattern', 'monitor changes' and 'monitor interval' to the same values on all servers that access the same database!
35
36 # == MySQL configuration ==
37 host: localhost# Where the database server is located at, e.g. 'example.com', 'localhost', or '192.168.1.100'
38 port: 3306# 3306 is MySQL's default port, i.e. you likely won't need to change this value
39 user: root
40 password: pass
41 database: skript# The database to use, the table will be created in this database.
42 table: variables21# The name of the table to create. 'variables21' is the default name, if this was to be omitted.
43 # (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)
44 # == SQLite/CSV configuration ==
45 file: ./plugins/Skript/variables.db
46 # 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).
47 # 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/...').
48
49 #table: variables21
50 # The name of the table to create. 'variables21' is the default name, if this was to be omitted.
51 # (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)
52 # This is generally not required as the the .db file will only be used by Skript, unless you want to split different variables into different tables
53
54 backup interval: 2 hours
55 # Creates a backup of the file every so often. This can be useful if you ever want to revert variables to an older state.
56 # Variables are saved constantly no matter what is set here, thus a server crash will never make you loose any variables.
57 # Set this to 0 to disable this feature.