This is a recommendation to epithumia of an issue you may want to add to your list in the first post.
In a nutshell, it is to be sure a possible contributor to your FM is on-board with his/her material being publically released along with the FM BEFORE it is uploaded to thiefmissions, when there's a good reason that author might not expect it to be released -- in most cases basically getting their informed consent and ensuring proper credit. Even if you think their contribution was very small or their consent was implied ... if there's a reason they might not expect it to be made public, be sure to err on the side of explicitly asking, because this is a person's work going out into the public.
NB, I'm thinking about a person that actually puts *work* into the FM -- from brushwork, to scripting and internal work, to making custom material for just that FM -- not a person that simply makes custom obj's generally available, where the general courtesy of giving credit should be enough.
Just as a reference point, this is a reaction to the recent incident involving the release of The City Square (here for future reference), where one author built some things into another author's FM just as an example of what to do, only to see it publically released, which he didn't expect. Another example was an FM where someone used another person's skybox before that person wanted it released, because he wanted to use it in his own FM first. But I don't want to spend any time dwelling on specific incidents -- enough has been said. It's the general issue I'm concerned about. Situations like these are the ones where you want to get consent before you release their stuff, because they don't expect it.





Reply With Quote
, taffers like this obviously donīt know of the time, effort and anxiety that got a mission this fare, like i sade iīm just wondering


