Updated Using Mapbase Content (markdown)

Blixibon 2020-08-14 17:51:44 -05:00
parent 269d41bb65
commit 1c245e82ed

@ -1,12 +1,12 @@
This page is a work in progress; It will cover how mods should credit Mapbase and its external content. A lot of this hinges on Mapbase v5.0 content which will be released soon.
This page covers how mods should credit Mapbase and its external content. A lot of this was created very recently and may be subject to change.
---
Mapbase is an open-source project and its contents can be distributed and used at the discretion of its users. However, this project represents many parts of the Source modding community packaged into a whole, so credit is taken very seriously.
* **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 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` 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. All external code documented to have been used by Mapbase is listed in both the repository's `README` and a `MAPBASE_CONTENT_USAGE.txt` file in the build on ModDB. Anything not listed inside should be credited to Mapbase itself.
---
@ -14,7 +14,7 @@ Mapbase is an open-source project and its contents can be distributed and used a
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.
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)* are using a unique header as of Mapbase v5.0.
```
//========= Mapbase - https://github.com/mapbase-source/source-sdk-2013 ============//
//