Serversync generates different configuration files when the server and the client runtime, by editing the configuration file to complete the needs of various operations.
Serversync version
The position of the configuration file 3.6.0 and below Config/Serversync4.0 and above are the same directory as Serversync
The first part of this tutorial takes a 3.6.0 configuration file as an example, the basic configuration of 3.7.0 is similar; the second part takes version 4.1.0 as an example.
Part 1: 3.6.0 version and below
Clientmods settings (for facilitation to push R key finishing, small maps and other client -specific mods)
Adjust the item in the serverSync-Server configuration file B: Push_Client_mods = False, and change it to true.Start a SS server and close it. The Clientmods folder will be automatically established on the server root directory.
Put the R key into the Clientmods folder.
Adjust the defuse_client_mods in the client adjust the file_client_mods in the client.
This can ensure that the client's dedicated MOD will not be deleted.
Serversync-client. (Client configuration file)
#Configuration fileGeneral {
##Set this to train to refuse client mode pushed by the server, [default: false]
B: Refuse_client_mods = false
// Reject the client MOD sent by the server.true: Reject, False: Accept.
}
ServerConnection {
##The ip address of the server [default: 127.0.0.1]
S: server_ip = 127.0.0.1
// Server IP
##The port that your server will be serving on [range: 1 ~ 49151, default: 38067]
I: server_port = 38067
// Synchronous server access port.Please set the port number from 1 ~ 49151, and exceeding this range will cause Serversync to be unable to save the corresponding information correctly!IntersectionAffect automation execution.}
rules {
##TheSe Files are iGnored by Serversync, Add Your Clics Here to Stop Serversync Deleting them.
S: file_ignore_list <
// Reject the list of files synchronized by the client.
}
**/Serversync-*. JAR
**/Serversync-*. CFG
"
}
misc {
##Your Locale String
S: local = zh_cn
// Local language settings
}
}
Serversync-Server.
#Configuration file
General {
###Set true to push client size mods from clientmods directory, set on server [default: false]
B: push_client_mods = false
// Push the client MOD.true: Push, FALSE: Do not push
##The type of sync bebing user, tweak this if you want different network,
I: Sync_mode = 0
// Synchronized network mode (not recommended to modify) is not developed.
}
ServerConnection {
##The port that your server will be serving on [range: 1 ~ 49151, default: 38067]
I: server_port = 38067
// Synchronous server access port.Please set the port number from 1 ~ 49151, and exceeding this range will cause Serversync to be unable to save the corresponding information correctly!Intersection
}
rules {
##The configs are invaluded, by default configs are not synced
S: config_include_list <
// Need a synchronous config file list.All files under the Config folder by default.
"
##These Directories are included, by default Mods and Configs Are Included
S: Directory_include_list
MODS
"
##TheSe Files are iGnored by Serversync, List Auto Updates with Moded to the Clientmods Directory
S: file_ignore_list <
// Refuse the file list sent to the client
**/Serversync-*. JAR
**/Serversync-*. CFG
// The operation of these two lines: refuse to send JAR and CFG files with the names of Serversync-names under all folders
"
}
misc {
##Your Locale String
S: local = zh_cn
// Local language settings
}
Add files to ignore the rules (specifically ignore the rules mode)
Application scenario:
When using SPONGE to open a service, you need to put the plug -in in the Mods folder. When you push the update, you do not need to push the plug -in.
When other needs to be ignored.
Edit Serversync-Server.cfg
[[[[[
S: file_ignore_list <**/Serversync-*. JAR
**/Serversync-*. CFG
"
] Field, add MODS/complete file name.
Example: MODS/Luckperms.jar
Other files ignore the rules (to modify the content inside according to your own needs, but you must ensure that the writing is correct):
Basic rules write MODS/1.12.2/** ignore the 1.12.2 folder under the MODS folder and all the files in the xxxxx file (complete file name) MODS/IC-*.jar
Ignore files in the IC-*. Jar class in the MODS folder; for example, IC-1.0.JAR
**/*. Disabled ignored the file ended in any directory with ".disabled" **/*Tweak*ignored the file name under any directory containing "Tweak" file
Part 2: 4.0.0 and above versions
Serversync 4.1.0 configuration file
-S server-
The configuration is as follows (note, the JSON file is not recommended to add a comment, please delete // and then use it later)
{{
"General": {
"Push_client_mods": false,
// Whether to push the client exclusive MOD, note that the newly created folder Clientmods after opening does not need to be included in the synchronous list
"Sync_mode": 2
// Synchronous mode (1: Online comparison, slower speed; 2: Use FileList, extremely fast), not recommended to modify.
///3.6.0 The default is 1,3.7.0-alpha2.
},
"Connection": {
"Port": 38067,
// The port of monitoring cannot be overlapped with the MC server port
"Buffer": 65536
// New high -level functions, it is not recommended to change (according to the author's statement, the larger the value is transmitted faster, the more upload the upload bandwidth)
},
"Rules": {
"Directories": [[
{{
"PATH": "MODS",
"Mode": "Mirror"
}
// Here is the synchronization rules of the directory that need to be synchronized. There are two modes: Mirror (mirror) and Push (push); // Mirror mode, there must be no extra files. In PUSH mode, it allows extra files.
// Both modes will be updated to the same name to the same (judgment based on hash values). Note that when adding, you need to add a comma after each "}", and there is no comma after the last "}".
// All symbols are English.It is the PUSH mode by default, and it will be mentioned below.
],,,
"Files": {
"Include": [[
"MODS/**"
// Here is a file that needs to be synchronized. The passing symbol refers to the end of version 3.7.0.For example: ** refers to all files, MODS/** is all files in the MODS folder.
// The files contained here are not defined in the above Directories, and will be pushed to the client by default by the PUSH mode.
// The rules are defined but not included here, and it will not be pushed to the client.
// It is recommended to regulate writing, and the rules and file/directory correspond to.When adding, you need to add a comma after each "", and the comma is not allowed after the last "".*/
//example:
// "MODS/**",
// "Save/**"
],,,
"Ignore": [[
"**/Serversync-*. Jar",
"**/Serversync-*. CFG"
// Here is a document that needs to be ignored.Note that if a file is ignored, it will be regarded as a file that does not exist, that is, in the Mirror mode, the client file will be deleted.
Pay attention to the JSON language rules when adding (the same as above)
],,,
"Redirect": [
// Here is the redirect, how to add unknown.But the mechanism can explain:
In the case of allowing clientmod, the content under the clientmods folder will be redirected to the MODS, which is regarded as a file under the MODS and follows the rules of the MODS folder.
]}
},
"MISC": {
"Locale": "zh_cn"
// Language settings
}
}
Serversync 4.1.0 configuration file
-The client-
{{
"General": {
"Refuse_client_mods": false,
// Whether to refuse to accept the client exclusive MOD.
"Sync_mode": 2
// Synchronous mode (not recommended to modify)
},
"Connection": {
"Address": "127.0.0.1",,
// The IP address of the serverSync server
"Port": 38067,
// The port of the serverSync server
"Buffer": 65536
// The value of the value is related to the maximum transmission speed of the server, and it is not recommended to modify it.
},
"Rules": {
"Files": {
"Ignore": [[
"**/Serversync-*. Jar",
"**/Serversync-*. CFG",
// Here is a document that needs to be ignored.
]
}
},
"MISC": {
"Locale": "zh_cn",,
//language
"Theme": "Blue_yellow"
// Update theme
}
}
Regarding automatic running configuration, it can be regarded as a short review of Sizhu (adding 4.1.0 version).There are more bugs for the time being, and GitHub has been submitted, and I look forward to the next version repair.In the 4.2.0 version, the JFX component is integrated, so it is easy to occur (double -click not responding). Waiting for the author to repair. In view of the above situation, the automation execution should be used to use version 3.6.0.
