MapBase/source-sdk-2013-mapbase
1
0
Fork 0
mirror of https://github.com/mapbase-source/source-sdk-2013.git synced 2025-01-12 23:07:55 +03:00
Code Issues Packages Projects Releases Wiki Activity

Updated Using Mapbase Content (markdown)

Blixibon 2020-08-10 16:30:21 -05:00
parent 21b515922c
commit 8d808d07bc
1 changed files with 23 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
Using-Mapbase-Content.md

@ -8,4 +8,26 @@ Mapbase is an open-source project and its contents can be distributed and used a
* **Mods using Mapbase in its entirety must mention that their mod runs on Mapbase.** For example, you can mention "Powered by Mapbase" or "This mod uses Mapbase" in your mod's credits. If your mod is on Steam, it can also be mentioned on the Store page. You can also link to Mapbase's ModDB or GitHub page. The repository's `README` (**note:** not yet updated for v5.0) should be included in any fork of the Mapbase repository. More may be added to this in the future in order to greater account for the external content.
* **Mods using substantial content from Mapbase without fully running on it should credit the content's original creators.** For example, Mapbase uses Saul Rennison's code for dynamic RTT shadow angles in Source 2013. If you were to borrow this from Mapbase's repository for your own mod without running on the rest of Mapbase, you should credit Saul Rennison instead of Mapbase itself. When v5.0 is released, all external code documented to have been used by Mapbase will be listed in both the repository's `README` and the build's `README.txt`. Anything not listed inside should be credited to Mapbase itself.
* **Mods using substantial content from Mapbase without fully running on it should credit the content's original creators.** For example, Mapbase uses Saul Rennison's code for dynamic RTT shadow angles in Source 2013. If you were to borrow this from Mapbase's repository for your own mod without running on the rest of Mapbase, you should credit Saul Rennison instead of Mapbase itself. When v5.0 is released, all external code documented to have been used by Mapbase will be listed in both the repository's `README` and the build's `README.txt`. Anything not listed inside should be credited to Mapbase itself.
---
### Mapbase code
As mentioned above, forks of Mapbase's repository should preserve the `README`'s contents and put any new content at the top, above the Mapbase section.
In order to avoid confusion with code from Valve, code from contributors, and code written by Mapbase's users in forks, all of Mapbase's own files *(entire files created specifically for Mapbase by Mapbase's creators or contributors)* will be using a unique header as of Mapbase v5.0.
```
//========= Mapbase - https://github.com/mapbase-source/source-sdk-2013 ============//
//
// Purpose:
//
// $NoKeywords: $
//=============================================================================//
```
**DISCLAIMER:** Mapbase's files are still a part of a modification of Valve's Source 1 SDK and continues to fall under Valve copyright and licenses.
All code files from the original SDK and external code files borrowed from other sources will usually retain their original header.
Users of Mapbase are advised to avoid using this header in their own files unless they plan to contribute them to Mapbase in the future. Please avoid modifying this header in any file which uses it.