GolcuOsman
Kızıltaş Madencisi
- En iyi cevaplar
- 0
PHP:
# ==== Variables ====
databases:
# Databases to store variables in. These can either be used as a simple one-server-storage
# where variables are written constantly but only read at server start,
# or as a connection between multiple servers by monitoring the database(s) for changes.
#
# 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.
#
# To be able to use a database you'll need to download the plugin 'SQLibrary' from http://dev.bukkit.org/server-mods/sqlibrary/files/
# and install it in your server's plugin directory like other plugins.
#
# Please note that '/skript reload' will not reload this section, i.e. you'll have to restart Skript for changes to take effect.
# 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.
database paun:
# an example database to describe all possible options.
type: MySQL
# The type of this database. Allowed values are 'CSV', 'SQLite', 'MySQL' and 'disabled'.
# 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.
pattern: {oyuncu.%player%.puan}
# Defines which variables to save in this database.
# This pattern uses Regex syntax, e.g. use 'db_.*' (without the quotes) to store all variables prefixed with 'db_' in this database,
# 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).
# Please note that variables are only stored in one database, and databases are checked from top to bottom,
# e.g. if a variable matches the topmost database's pattern it will be saved there and nowhere else.
# BTW: Patterns are checked in a separate thread, i.e. your server likely won't run slower when using complicated patterns.
monitor changes: false
monitor interval: 20 seconds
# If 'monitor changes' is set to true, variables will repeatedly be checked for updates in the database (in intervals set in 'monitor interval').
# ! Please note that you should set 'pattern', 'monitor changes' and 'monitor interval' to the same values on all servers that access the same database!
# == MySQL configuration ==
host: tr027.nitrado.net# Where the database server is located at, e.g. 'example.com', 'localhost', or '192.168.1.100'
port: 3306# 3306 is MySQL's default port, i.e. you likely won't need to change this value
user: ni426557_1_DB
password: 123456
database: ni426557_1_DB# The database to use. Skript will automatically create a table 'variables21' in this database if it doesn't exist
# (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)
# == SQLite/CSV configuration ==
file: ./plugins/Skript/variables.db
# 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).
# 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/...').
backup interval: 2 hours
# Creates a backup of the file every so often. This can be useful if you ever want to revert variables to an older state.
# Variables are saved constantly no matter what is set here, thus a server crash will never make you loose any variables.
# Set this to 0 to disable this feature.
MySQL example:
# A MySQL database example, with options unrelated to MySQL removed.
type: MySQL# change to line below to enable this database
# type: MySQL
pattern: {oyuncu.%player%.puan}# this pattern will save all variables that start with 'synced_' in this MySQL database.
host: tr027.nitrado.net
port: 3306
user: ni426557_1_DB
password: 123456
database: ni426557_1_DB
monitor changes: true
monitor interval: 20 seconds
SQLite example:
# An SQLite database example.
type: disabled# change to line below to enable this database
# type: SQLite
pattern: db_.*# this pattern will save all variables that start with 'db_' in this SQLite database.
file: ./plugins/Skript/variables.db
# SQLite databases must end in '.db'
backup interval: 0# 0 = don't create backups
monitor changes: false
monitor interval: 20 seconds
default:
# 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.
# This is the last database in this list to catch all variables that have not been saved anywhere else.
# You can modify this database freely, but make sure to know what you're doing if you don't want to loose any variables.
type: CSV
pattern: .*
file: ./plugins/Skript/variables.csv
backup interval: 2 hours
# 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)
# 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_'.
# Be very cautious when doing this however as unsaved variables cannot be recovered after the server has been stopped.
# 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 '(?!-).*'.
# ==== Settings that should not be changed ====
version: 2.2-SNAPSHOT
# DO NOT CHANGE THIS VALUE MANUALLY!
# This saves for which version of Skript this configuration was written for.
# If it does not match the version of the .jar file then the config will be updated automatically.
Son düzenleme:
