Assets Contribution Principles

These guidelines are no longer stored on GitHub and can be outdated. For newest version of guide please refer to this page.

Welcome on page which serves as guiding point for anyone who would like to contribute to The Isle of Ansur game through assets making. Contents written here are considered a contract to be abided by both parties - a contributor and owner of leading developer (Toma400).

This page can expand over time given there's a reason to it. That said, if contributor abode by previous rules, they are considered upheld unless there's explicit agreement from contributor to follow updated version of those principles.

---

AI should not be used

As a developer and artist, I highly despise AI generated content, and so I do require assets for IoA being made entirely by human.
There's small exception though, if you used AI to generate things to inspire you, but later did everything by hand, this is acceptable way. I would recommend not supporting AI movement though, for reasons I explained in this thread.

Contribution use rights are permanently moved to developer in lore context

Whatever you pass as a contribution, you grant The Isle of Ansur developer right to use it within the lore context permanently, with also possibility to modify the asset if there's a need.
This means, for instance, book you've written to be used in any form in the future, in either The Isle of Ansur, Baedoor Encyclopaedia, or any other creation which uses Baedoor lore. Or, as another example, your concept art, to be recontextualised as part of Encyclopaedia, game manual, or reshaped into model asset for game use (by some human artist).

Things I do not get permission for is possibility to use this art commercially as a separate product - I cannot sell book you've written as separate thing. But I can sell game I made with said book being one of many in there (however it's unlikely scenario, as current contribution rules are explicitly to solve problems of volunteering system and me considering free distribution as default).

Such huge control over the asset is radical request, let me explain purpose of it:

• The decision of it is made to keep Baedoor lore coherent. If asset can be freely taken out of lore, it means loss of coherency. Therefore, contributing with assets, remember this is serious decision, as I treat similarly seriously any addition to what is considered "canon".
• I will do my best to listen to contributor's will, so as serious as permanent movement of rights sounds, I will also not prey on contributions like big companies do. I will try to preserve my universe first, but if request is possible to keep both parties satisfied, I will happily choose this option.
• Credit, right to use outside of lore context, is absolutely in your hands. The only right I reserve for Baedoor lore is to keep the asset within its context indefinitely and manage it. As Baedoor Encyclopaedia will always be free, your contribution will never be behind paywall, and if I'm ever going to monetise my games, your contribution will be available from outside sources (such as Baedoor Encyclopaedia and games/art being free, referring to your contribution in one way or another).
• You can be ensured your contribution will never be used in AI training by any means. However keep in mind that resources used by my projects are uploaded on GitHub for control version purposes, and while their license prohibits use in context of AI, I can't promise license being followed by GitHub or its parent company.