Clarification on BA branding and mutators policy
Posted: 05 Sep 2010, 11:48
Supercedeed on 13/12/2016 by community wide guidelines - https://springrts.com/wiki/Licenses_Forking_Mutators
Kept for reference only.
Just thought i'd post some official guidelines on BA's "Branding" use for in map/mod mutators & forks:
> Mutators and forks should contain some significant difference to the usual BA gameplay.
- Map mutators are best for small changes that are map specific (e.g. Duck Fusions).
- Mod mutators are best for small unit/game changes (e.g. King of the Hill)
- Substantial changes should be made with a fork & an entirely new mod file.
Naming conventions
> Mutator names should make it explicitly clear that the map/mod is a mutator which has a BAx.x dependence or will modify content from BA.x.x; e.g.
-- Something (BAx.xx)
-- BA Something (BAx.x)
> Names and version numbers of forks should clearly distinguish the fork from BA.
Not Acceptable
> Names designed to impersonate e.g. "Balanced Annihilation Vx.(x+1)" or "Balanced Annihilation Improved Edition".
> Anything which has a file based dependency on some particular lobby or engine version. (Forcing dependency on a particular BA version is allowed.)
> Any smartass work around of the above
If in doubt - ask! The Spring Mods have been supportive so far on the subject of Mod Hijacking so I'd appreciate everyone's cooperation on this :)
Kept for reference only.
Just thought i'd post some official guidelines on BA's "Branding" use for in map/mod mutators & forks:
> Mutators and forks should contain some significant difference to the usual BA gameplay.
- Map mutators are best for small changes that are map specific (e.g. Duck Fusions).
- Mod mutators are best for small unit/game changes (e.g. King of the Hill)
- Substantial changes should be made with a fork & an entirely new mod file.
Naming conventions
> Mutator names should make it explicitly clear that the map/mod is a mutator which has a BAx.x dependence or will modify content from BA.x.x; e.g.
-- Something (BAx.xx)
-- BA Something (BAx.x)
> Names and version numbers of forks should clearly distinguish the fork from BA.
Not Acceptable
> Names designed to impersonate e.g. "Balanced Annihilation Vx.(x+1)" or "Balanced Annihilation Improved Edition".
> Anything which has a file based dependency on some particular lobby or engine version. (Forcing dependency on a particular BA version is allowed.)
> Any smartass work around of the above
If in doubt - ask! The Spring Mods have been supportive so far on the subject of Mod Hijacking so I'd appreciate everyone's cooperation on this :)