* Make ServerPackaging automatically get extra server assemblies * Make the switch * Use Content.Server.deps.json instead * Remove debug * Rewrite Now recursively fetches dependencies from Content.Server Only copies dependencies not covered by Robust This removes the need to manually specify most of the dependencies, even the content ones! Also look at runtime key properly to figure out the proper dll name. This actually removes some assemblies that were duplicated between the main directory and assemblies (various Microsoft.Extensions stuff) * Fix test compile errors when updating dependencies Ran across this while updating dependencies on the RT .NET 10 update. Should be fine to merge immediately. * More .NET 10 prep * Convert to SLNX Hell yeah * slnx now has size-2 indents * Update SLNX with new RT system * Remove reference to RT test in toolshed test * Remove accidental usage of transitive RT dependencies * Move Robust project references to RobustApi * Update solution file * Fix warnings in pow3r * Fix nullable warnings in integration tests idk where these came from * gitignore binlog files * Fix transitive dependency warnings in Content.Benchmarks * Update slnx * Okay, the Robust API thing didn't pan out. New plan. It apparently broke clean builds, as the dependencies aren't in the project asset list or something anymore. I tried to fix this, but it seems impossible to do without relying on .NET SDK internals, as there's no point in the NuGet graph walk process that seems cleanly extensible. Instead let's just do the much dumber thing: a bunch of .props files for content to import. Hooray! This also means that I have to go through and *explicitly* disable transitive dependencies everywhere in RT. This thankfully isn't too hard. * Update RT to 269.0.0 * One last solution update * Fix more data definition issues * Update RT to 269.0.1 * Fix it again --------- Co-authored-by: DrSmugleaf <drsmugleaf@gmail.com>
Space Station 14 is a remake of SS13 that runs on Robust Toolbox, our homegrown engine written in C#.
This is the primary repo for Space Station 14. To prevent people forking RobustToolbox, a "content" pack is loaded by the client and server. This content pack contains everything needed to play the game on one specific server.
If you want to host or create content for SS14, this is the repo you need. It contains both RobustToolbox and the content pack for development of new content packs.
Links
Documentation/Wiki
Our docs site has documentation on SS14's content, engine, game design, and more.
Additionally, see these resources for license and attribution information:
We also have lots of resources for new contributors to the project.
Contributing
We are happy to accept contributions from anybody. Get in Discord if you want to help. We've got a list of issues that need to be done and anybody can pick them up. Don't be afraid to ask for help either!
Just make sure your changes and pull requests are in accordance with the contribution guidelines.
We are not currently accepting translations of the game on our main repository. If you would like to translate the game into another language, consider creating a fork or contributing to a fork.
AI-generated contributions disclaimer
This project does not accept low-effort or wholesale AI-generated contributions. Examples include, but are not limited to:
- Any code (including yaml) generated by tools like GitHub Copilot, ChatGPT, or similar.
- AI-created artwork, sound files, or other assets.
- Auto-generated documentation, issue reports or pull request descriptions.
Exceptions to this are simple tools like Rider's single-line completion feature.
Building
- Clone this repo:
git clone https://github.com/space-wizards/space-station-14.git
- Go to the project folder and run
RUN_THIS.pyto initialize the submodules and load the engine:
cd space-station-14
python RUN_THIS.py
- Compile the solution:
Build the server using dotnet build.
More detailed instructions on building the project.
License
All code for the content repository is licensed under the MIT license.
Most assets are licensed under CC-BY-SA 3.0 unless stated otherwise. Assets have their license and copyright specified in the metadata file. For example, see the metadata for a crowbar.
Note
Some assets are licensed under the non-commercial CC-BY-NC-SA 3.0 or similar non-commercial licenses and will need to be removed if you wish to use this project commercially.