 |
welcome, guest |
This information comes from readme files and other documentation provided by the creators, but the policies listed below cannot be guaranteed to be true for all of that creator's works. Collaborative projects in particular are likely to be subject to different conditions. If you are looking to rehost or otherwise redistribute a creator's work, you are encouraged to consult any documentation that may have come with it to ensure that you are looking at their most current and relevant policy.
Methods of redistribution fall into two categories. Filesharing is here defined as the act of sharing a work (such as an agent, breed or metaroom) with specific people, usually via email. Rehosting is the act of uploading a work to make it publically available on another web site. Assuming that an author is open to having their work shared or rehosted, it is considered basic etiquette to ensure that any documentation (such as readme files) that were provided with the work remain packaged with it if at all possible. Proper credit should also be given to ensure that any recipients are aware of the work's origin. Updated by Malkin on 4/20/2015 - updating with statement from RProgrammer. Updated by ylukyun on 8/22/2015 - Updating to reflect Liam's statement. Updated by ylukyun on 1/9/2018 - Updating to reflect C-Rex's statement... how did I miss that?. Updated by ylukyun on 1/9/2018 - Dates. Updated by Grendel_Man on 2/28/2018 - Updated own policy. Updated by Grendel_Man on 5/6/2018 - Updated with Norngirl's new policies.. Updated by Laura on 7/5/2018 - added CosmiSynth's policy. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
I'm not going to delete what I said about Amaikokonut just because Jessica disagrees it. Amaikokonut did vanish for well over a year. We did try to contact her while she was gone and those attempts failed. So, yes, my original statement was correct and the conditions she described had been at one point in time. It's more useful in my mind to mention that than to just sweep it all under the rug. The site staff isn't required to alter resources simply because one member doesn't like how we worded something. The policies listed here come straight from the creators' own readme files included with their agents. I will edit the article to be clearer on where the information is coming from, but I see no need for that kind of compromise simply because Jessica dislikes how we're doing things. This is the format agreed upon by the site staff, and it is going to stay the way it is unless the moderators agree on something else that will work better, or Rascii specifically tells me otherwise. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
Another compromise could be to say "unverified" or "needs confirmation". An idea of their previous policy might be more helpful for people trying to find the policies and might be incentive to get more people involved in contacting these developers. The more help the better, y'know? I didn't even know some of these developers existed, so a list of names is still helpful. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
Well said, Kezune. I would be completely fine with this list if everything was verified by the creators. Judging by the names on this list, that's nearly everyone. It's just the few who weren't contacted for an official stance that could create the confusion. Maybe only include those policies that have been verified by their creators? | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Perhaps the best way to look at this list is as a work in progress. With so many developers currently inactive and difficult to get a hold of, it would be difficult to get a fully detailed, comprehensive list of all policies over all agents ever made by any developer. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
... What happened to my comment here about Amaikokonut? It was deleted and the policy is still incorrectly interpreted. I think that ElasticMuffin brings up some good points: This is presented as a definitive list of creator policies, and there is already a great deal of confusion. The individual creator should be the one to provide an official stance on his/her policy. If said creator can't be reached, then having others interpret license language can lead to confusion or, even worse, a wrongly stated policy. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
The problem there is that this gives the appearance of a definitive list of per-person policies right now, when some of these people might have different policies for some of their stuff. For example, you have on here now that I allow all my works to be freely distributed and modified - while your assumption was correct, I never said that - I only applied that to stuff available on Eem Labs. I know this sounds pedantic and obnoxious, but my point is that this stuff is tricky, and trying to interpret people's vaguely-defined licenses in a broad way like this may cause more problems than it solves. Ghosthande wrote: I'd argue that unless you make what you've stated here more clear in the article (this is just an interpretation of some of their preferences, not a definitive listing), then it's actually more misleading than helpful. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
ElasticMuffin: There's no reason why multiple policies would not be mentioned if we came across them--hence why the table lists reference agents already. In this case, the site staff was in agreement that knowing at least some of a creator's preferences was more useful than nothing. Laura: Yes!  Anyone who wants their policy added, or knows of useful information not yet posted here, is welcome to post a reply.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Policy by creator seems like it might be over-generalizing things a bit? Unless the author has specified a blanket policy somewhere, it's probably a per-item deal. Also if you're intending to make a list like this it might be worthwhile to reach out to people like Helen and see what their current stance on this is. It is unfortunate that the CC didn't develop during the age of Github and open-source - might have made it much easier to find all this stuff for download years later and might have made it possible for more people to learn CAOS coding. For what it's worth, anything on Eem Labs (not just my stuff - I checked) may be freely distributed and modified, with credit. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
And people can comment here to have their policies added, right?
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| downloads cobs adoptions creaturelink metarooms breeds gallery art wallpaper screenshots graphics promos sprites |
dev hack shack script reservations dev resources active projects dev forum community links advice chat polls resources |
creatchi forum bookmarks general news help development strangeo survivor |
mycaves log in register lost pw |
0 online |
| creatures caves is your #1 resource for the creatures artificial life game series: creatures, creatures 2, creatures 3, docking station, and the upcoming creatures family. contact help privacy policy terms & conditions rules donate wiki |
||||