Implemented Playerdata DB Syncing

This commit is contained in:
Sn0wStorm
2020-01-29 15:39:02 +01:00
parent 00f541dafe
commit 1266111f8a
11 changed files with 184 additions and 28 deletions
+17
View File
@@ -66,6 +66,7 @@ maxBrewsInMCBarrels: 6
# hacked clients from reading what exactly was used to brew an item, the data can be encoded/scrambled.
# This is a fast process to stop players from hacking out recipes, once they get hold of a brew.
# Only drawback: brew items can only be used on another server with the same encodeKey.
# When using Brews on multiple (BungeeCord) Servers, define a shared Database below at 'multiServerDB'
# So enable this if you want to make recipe cheating harder, but don't share any brews by world download, schematics, or other means. [false]
enableEncode: false
encodeKey: 0
@@ -774,6 +775,22 @@ useGMInventories: true
useLogBlock: true
# -- MultiServer/BungeeCord --
# If Brewery is running on multiple connected Servers (via BungeeCord)
# a shared Database can be used here to synchronise drunkeness and to be able to use encoded brews between them.
multiServerDB:
# If using the Database is enabled
enabled: false
# If the drunkeness of players should be synchronised between Servers
syncDrunkeness: true
host: localhost
port: '3306'
user: minec
password: xyz
database: base
# -- Imostazioni di distorsione della chat --
# If written Chat is distorted when the Player is Drunk,