Requirements
There are a lot of creative minds in this community. Those who make content all learn through trial and error. Through constantly challenging yourself. Usually the results of that are there for everyone to see. But the road that you had to take to get to those results are more difficult to find. The goal of this tournament is not so much about the results as it is about the road you took to get to the results. Some of these hard requirements reflect that.
The following rules are strict requirements. If you do not meet these requirements then your submission will be disqualified. I don't want to disqualify your submission. Please make sure you've read, understood and applied them accordingly. To list them, you have to:
- (1) Meet the functional requirements
- (2) Use either of the creative licenses on your content
- (3) Document one trial-and-error through text and images or video
- (4) Document the end results through text and images or video
1. License
Almost all of the code base of FAF is shared using an open source license. Such a license guarantees the continuity of the project. The most common license we use is the MIT license. Even some of the game code, including the navigational mesh, has that same license applied to it.
This is in contradiction with a lot of the content in the map or mod vault. Usually there is no license. As a consequence the author retains all rights and people are not allowed to make derivatives. I've always thought this to be in contradiction to the open nature of FAF. This tournament is here to help mitigate this.
All submissions require either one of the following licenses:
or
I'd highly recommend you to license it with the non-commercial license. This prevents people and companies from using your content commercially without your consent.
To license your map you need to:
- (1) Add a
LICENSE.md
file in the map folder with the content of the license - (2) Add a reference to the license in the description of the map
A healthy consequence of this requirement is that your map can be used in other communities such as LOUD and BAR. A lot of my maps are available in the LOUD community. One of my maps is available in the BAR / Zero-k communities.
An exclusion is made to content from websites such as www.textures.com. They allow you to share the content, but they do not allow you to add a creative commons license over their content. You can read more about how to properly license those textures in a separate forum topic.
2. Documenting the road
As mentioned before, we all learn through trial and error. One requirement of this tournament is to document one such trial. It should answer the following questions to some degree:
- (1) What are you trying to accomplish?
- (2) What did you try to accomplish it, and why didn't it work?
- (3) What did you end up doing to accomplish it?
You can create this either using:
- (A) Markdown-compatible text, including images where applicable
- (B) A video that you're sharing on YouTube, available publicly
You can read more about what we'll do with this in the footnotes. There's no quality check on this requirement. You can cheese it if you want to. We hope you don't though. We hope to get a few valuable resources that people can use to learn from. A few examples available at this moment:
These examples are quite extensive , you do not need to create several videos or write several long forum posts. It is sufficient to narrow it down to one topic or insight that you'd like to share with the community.
3. Documenting the result
And as last we're asking you to add some flair to the results. Add a few screenshots and write a few sentences about what the map is about to you. The text needs to be markdown-compatible. As a few examples, see these readme files:
There's more to this tournament than just making maps. It is about sharing the knowledge to create content. It is about promoting the community and the content it creates on a weekly basis.
We'll use the documentation to create several wiki pages about the submissions. These pages include the documentation of the result, the tutorial-like documentation of (a part of) the road and the feedback of the judges. The goal is to create a hub of information that people can access for years to come.