mirror of
https://github.com/mapbase-source/source-sdk-2013.git
synced 2024-12-27 07:15:31 +03:00
f636089003
- Added keyvalue to use random bounds on logic_timer to limit AddToTimer/SubtractFromTimer inputs (suggested by White_Red_Dragons) - Fixed inconsistent env_projectedtexture state on save/load - Added code to allow skybox to use a direct entity handle instead of a stored origin and angles in order to take advantage of entity interpolation while moving (less jittering) - Moved map-specific file manifest parsing to happen after other entities are created (highly experimental) - Added various misc. code improvements related to debug build and MP branch - Fixed some VScript ammo type-related code forgotten in the previous update - Added more VScript functions to CBaseAnimating, including pose parameter functions and the ability to look up bones and get bone position - Added more origin and angles functions for VScript (suggested by krassell)
37 lines
1.8 KiB
Plaintext
37 lines
1.8 KiB
Plaintext
This file details how to contribute to the Mapbase project on GitHub:
|
|
https://github.com/mapbase-source/source-sdk-2013
|
|
|
|
For the original Source SDK 2013 contribution guidelines, click here:
|
|
https://github.com/ValveSoftware/source-sdk-2013/blob/master/CONTRIBUTING
|
|
|
|
---
|
|
|
|
Mapbase is a project which many Source modders draw from, so it has its own unique standards
|
|
for contributions which differ from other projects, but it is still an open-source repository
|
|
that is always open to contributions.
|
|
|
|
Whenever you contribute to the Mapbase repository, you must keep in mind that any contributions
|
|
made could be deployed to all mods utilizing Mapbase, which can include everything from high-profile
|
|
Steam mods to amateur HL2 maps. Many contributions can also end up being available in both SP and MP
|
|
if the contributions are not obviously exclusive to one of the two.
|
|
|
|
All contributions must follow the following rules:
|
|
|
|
* A contribution must be aligned with Mapbase's goals and priorities and should not be "subjective"
|
|
or related to a specific mod or type of mod. For example, fixing an existing issue or adding a
|
|
new tool for mappers to use is usually fine, but adding a new custom weapon with its own assets
|
|
is usually not fit for Mapbase.
|
|
|
|
* All content in a contribution must be either already legally open-source or done with the
|
|
full permission of the contribution's original creator(s).
|
|
|
|
* Code contributions are not obliged to follow Mapbase's preprocessor conventions (e.g. #ifdef MAPBASE),
|
|
although it's acceptable.
|
|
|
|
If your contribution is accepted, you may be listed in Mapbase's credits:
|
|
https://github.com/mapbase-source/source-sdk-2013/wiki/Mapbase-Credits#Contributors
|
|
|
|
You may also receive the "Contributor" or "Major Contributor" role on Mapbase's Discord server if you are
|
|
a member of it.
|
|
|