Ever wanted a private server that is quick to update when the game updates, but doesn't sacrifice too much features?
A server that's modular enough and feature complete-ish for battle simulation?
QingqueSR got you covered.
This tutorial assumes you have basic knowledge of terminal usage and traffic redirection via a proxy.
-
Download the proxy tool from here.
-
If you experience internet connectivity issues after playing, manually disable the proxy in your Windows settings.
-
Download the prebuilt version that matches your SR version from here.
-
Extract the ZIP file.
-
Edit configuration files in the
_cfg
folder as needed (refer to the README in that folder). The server will fallback to default config when a file in_cfg
is invalid or missing. -
Run the following executables:
game-server.exe
sdk-server.exe
-
Make sure game traffic is being redirected and have fun.
-
If you want to see the logs when the server panics, run the binary through cmd.
-
You can use
cfg-manager.exe
to easily manage config.json(s).
-
Install the following tools:
- Rust
protoc
(Protocol Buffers compiler)
-
Clone the repository:
git clone https://github.com/f2pqingque/sr.git
-
cd into
sr
-
If you want to use your own protobufs:
- Clone
https://github.com/f2pqingque/sr-proto.git
too - Change dependency source in root Cargo.toml
- Place your proto file in the
sr-proto
folder, and adjust thebuild.rs
file accordingly.
- Clone
-
Edit configuration files in the
_cfg
folder as needed (refer to the README in that folder). -
Build and run the server:
cargo run --release --bin game-server
cargo run --release --bin sdk-server
-
Build and run config.json manager (optional):
cargo run --release --bin cfg-manager
-
Share prebuilt (optional):
rustc pub.rs ./pub.exe [VERSION]
- QingqueSR Developer: Yulian
- QingqueSR Maintainer: Naruse
- SRTools Author: Amizing25
- Protobufs: Amizing25 & Lukopa