Valve, the Valve logo, Half-Life, the Half-Life logo, the Lambda logo, Steam, the Steam logo, Team Fortress, the Team Fortress logo, Opposing Force, Day of Defeat, the Day of Defeat logo, Counter-Strike, the Counter-Strike logo, Source, the Source logo, Counter-Strike: Condition Zero, Portal, the Portal logo, Dota, the Dota 2 logo, and Defense of the Ancients are trademarks and/or registered trademarks of Valve Corporation. All other trademarks are property of their respective owners. See https://store.steampowered.com/legal for Valve Corporation legal details.
This repo is based on Valve's Source Engine from 2018. Please, use this for studying only, not for commercial purposes. See https://partner.steamgames.com/doc/sdk/uploading/distributing_source_engine if you want to distribute something using Source Engine.
Obsoletium is an open-source, cross-platform game engine.
The Obsoletium project uses an open governance model.
Contributors are expected to act in a collaborative manner to move the project forward. We encourage the constructive exchange of contrary opinions and compromise.
This project has a Code of Conduct.
- Support
- Release types
- Building Obsoletium
- Security
- Contributing to Obsoletium
- Current project team members
- License
- Tools
Looking for help? Check out the instructions for getting support.
- Current: Under active development. Code for the Current release is in the branch for its major version number (for example, v1.x). Obsoletium releases a new major version every 12 months, allowing for breaking changes.
- Custom: You can build code from the Current branch on your own. Use with caution.
Current releases follow semantic versioning. A member of the Release Team signs each Current release.
Binaries, installers, and source tarballs are available at https://github.com/Source-Authors/Obsoletium/releases.
https://github.com/Source-Authors/Obsoletium/releases
Use your own naming schema.
Downloads contain a SHASUMS256.txt.asc file with SHA checksums for the
files and the releaser PGP signature.
You can import the releaser keys in your default keyring, see Release keys for commands to how to do that.
Then, you can verify the files you've downloaded locally:
curl -fsO "https://github.com/Source-Authors/Obsoletium/releases/tag/${VERSION}/SHASUMS256.txt.asc" \
&& gpgv --keyring="${GNUPGHOME:-~/.gnupg}/pubring.kbx" --output SHASUMS256.txt < SHASUMS256.txt.asc \
&& shasum --check SHASUMS256.txt --ignore-missingSee BUILDING.md for instructions on how to build Obsoletium from source and a list of supported platforms.
For information on reporting security vulnerabilities in Obsoletium, see SECURITY.md.
For information about the governance of the Obsoletium project, see GOVERNANCE.md.
- dimhotepus - Dmitry Tsarevich <[email protected]> (he/him)
- RaphaelIT7 - Raphael <[email protected]> (he/him)
Collaborators follow the Collaborator Guide in maintaining the Obsoletium project.
- dimhotepus - Dmitry Tsarevich <[email protected]> (he/him)
Triagers follow the Triage Guide when responding to new issues.
Primary GPG keys for Obsoletium Releasers:
- Dmitry Tsarevich <[email protected]>
D80E14A4A52C46278F7B7B5C3B77A450568588BA
You can import them from a public key server. Have in mind that the project cannot guarantee the availability of the server nor the keys on that server.
gpg --keyserver hkps://keys.openpgp.org --recv-keys D80E14A4A52C46278F7B7B5C3B77A450568588BA # Dmitry TsarevichSee Verifying binaries for how to use these keys to verify a downloaded file.
Obsoletium is available under the SOURCE 1 SDK LICENSE. Obsoletium also includes external libraries that are available under a variety of licenses. See LICENSE for the full license text.
- PVS-Studio - static analyzer for C, C++, C#, and Java code.