An open source implementation of the dark souls 3 game server.
Idealistically made for the purpose of allow better alternatives to playing mods than getting your account banned and using the retail ban server. As well as opening up opportunities to improve player safety and choice, by allowing them to segregate themselves off from the pool of cheaters on retail, without loosing network functionality.
No, the server authenticates steam tickets. Please do not ask about piracy, steam emulators or the like, we have no interest in supporting them.
FROM SOFTWARE deserves your support too for the excellent work they do, please buy their games if you can.
Downloads are available on the github releases page - https://github.com/TLeonardUK/ds3os/releases
Once built you should have a folder called Bin, there are 2 subfolders of relevance. Loader and Server.
First run the Server.exe in Server, this will start the actual custom server running on your computer.
The first time the server runs it will emit the file Saved\config.json which contains various matchmaking parameters that you can adjust (and apply by restarting the server) to customise the server.
User can join the server by opening the Loader.exe program in the Loader folder and finding the correct server in the list and clicking the launch button. If the server has been configured to not advertise on the master server (or if running on a LAN without an internet connection), then the server operator can distribute the Saved\server.ds3osconfig file that the server emits, which can be imported into the loader and used to directly connect to the server.
Servers can also be password protected if required by setting as password in Saved\config.json, a password will need to be entered when attempting to launch the game with a protected server.
Most of the games core functionality works now, with some degree of variance to the retail game. We're currently looking to closer match retail server behaviour and make some general improvements to the running of unoffical servers.
- Login, key exchange and network transport
- Announcement messages
- Profile management
- Blood messages
- Bloodstains
- Ghosts
- Summoning
- Invasions
- Visitors (Auto-Summoning via covenant)
- Matchmaking (eg. Correctly matching summoning/invasions/visits with player level)
- Roster of knights
- Archdragon peak bell ringing
- Undead match
- Telemetry and misc server calls (the few that are of use to us)
- Steam ticket authentication.
- Master server support for loader (show available servers).
Future roadmap:
- Regulation file distribution.
- Anticheat (potentially we could do some more harsh checks than FROM does).
- WebUI for server showing gameplay statistics / allowing admin control.
So far we've had several accounts using unoffical servers, for quite a while, and have not had any account penalized on the retail server.
So it seems safe enough. The only way you are going to get banned is if you do things that would normally get you banned then go back to the retail server - cheating and the like.
Currently the project uses visual studio 2019 and C++17 for compilation, and as such is currently limited to windows. At some point in future the codebase will likely be moved over to something platform agnostic like cmake.
Ensure that you have vcpkg (https://vcpkg.io) installed and integrated into visual studio as well, as it is used for managing a few of the dependencies, by doing the following:
- Clone the vcpkg repo:
git clone https://github.com/Microsoft/vcpkg.gitor download the repository as .zip file - Run Windows PowerShell as Administrator and
cdinto the directory, example:cd C:\dev\vcpkg - Enter command:
.\bootstrap-vcpkg.batand wait for it to process - Enter command:
.\vcpkg integrate installand wait for it to process
Building the project should now require opening the Source/DS3OpenServer.sln and building it. To uninstall vcpkg use the .\vcpkg integrate remove command.
/
├── Config/ Contains any useful configuration material, server config files and alike.
├── Protobuf/ Contains the protobuf definitions used by the server's network traffic. Compiling them is done via the bat file in Tools/
├── Resources/ General resources used for building and packaging - icons/readmes/etc.
├── Source/ All source code for the project.
│ ├── Loader/ Simple winforms app that loads DS3 such that it will connect to a custom server.
│ ├── Server/ Source code for the main server.
│ └── ThirdParty/ Source code for any third-party libraries used. Preference is storing source here over using vcpkg modules where practical.
├── Tools/ Various cheat engine tables, bat files and alike used for analysis.
Check our the issues page, or send me a message for suggestions on what can be done.
Right now there are a few server calls we either have stubbed out or returning dummy information, implementing them properly, or finding out the format of the data they need to return would be worth while.
There are also a lot of protobuf fields that are still unknown and use constant values when sent from the server, determining what they represent would be a good improvement.
A lot of the information needed to produce this implementation has been figured out by the community. Especially the members of the ?ServerName? souls modding discord.
The following 3 repositories have provided a lot of information used in this implementation:
https://github.com/garyttierney/ds3-open-re
https://github.com/Jellybaby34/DkS3-Server-Emulator-Rust-Edition
https://github.com/AmirBohd/ModEngine2
Graphics and icons provided by:
Campfire icon made by ultimatearm from www.flaticon.com
Various UI icons made by Mark James from http://www.famfamfam.com/lab/icons/silk/