ZC changes to come, and a call for help

[bobby_light]

This is why we wanted a centralized database. I also wanted to put in the license that all quests could only be uploaded to one location, which would prevent exactly what you are describing.

I don't think this would make any difference. Someone willing to "steal" a ZC quest is surely also willing to ignore its license. Encouraging folks to upload their creations however, and otherwise join the community, is an excellent idea.

[ctrl-alt-delete]

I don't think this would make any difference. Someone willing to "steal" a ZC quest is surely also willing to ignore its license. Encouraging folks to upload their creations however, and otherwise join the community, is an excellent idea.

Hypothetically, if somebody stole a quest and took it somewhere else and the original creator discovered it, there wouldn't be much they could do to have it removed(because who owns quests is questionable at best). If the license said it couldn't be there, they could easily have it removed by contacting the host.

Obviously, we decided against the one upload place edit in the license, but it may still be a good idea to list certain places. Here, pzc, etc.

[bobby_light]

Hypothetically, if somebody stole a quest and took it somewhere else and the original creator discovered it, there wouldn't be much they could do to have it removed(because who owns quests is questionable at best). If the license said it couldn't be there, they could easily have it removed by contacting the host.

Obviously, we decided against the one upload place edit in the license, but it may still be a good idea to list certain places. Here, pzc, etc.

Of course keep in mind you folks are free to do whatever you want, I'm just feeling a little argumentative tonight :)

Are you saying you folks have considered having the license extend to quests created with ZQ? If someone puts a *quest* on another web site, the license of *ZQuest/ZC* doesn't matter - unless you're saying that the ZC license will include a clause along the lines of "all quests created with this program can only be hosted on the following sites..." Having the license extend to products created with ZQ seems a little overbearing - other tools such as GameMaker (or compilers in general) never restrict what you can do with generated output.

Back on topic - I'd suggest the obvious choice of simply hosting on github. Beats hosting your own repository - you get failover, backups, etc. for free - and people can easily fork the project to contribute. As far as a build farm, I have no first-hand experience; they've always been administered by someone else. But that's always something you can look into later.

[ctrl-alt-delete]

Of course keep in mind you folks are free to do whatever you want, I'm just feeling a little argumentative tonight :)

Are you saying you folks have considered having the license extend to quests created with ZQ? If someone puts a *quest* on another web site, the license of *ZQuest/ZC* doesn't matter - unless you're saying that the ZC license will include a clause along the lines of "all quests created with this program can only be hosted on the following sites..." Having the license extend to products created with ZQ seems a little overbearing - other tools such as GameMaker (or compilers in general) never restrict what you can do with generated output.

Back on topic - I'd suggest the obvious choice of simply hosting on github. Beats hosting your own repository - you get failover, backups, etc. for free - and people can easily fork the project to contribute. As far as a build farm, I have no first-hand experience; they've always been administered by someone else. But that's always something you can look into later.

I considered it for various reasons, but we decided against it.

github is on the table...we talked about a couple other options too.

[DarkDragon]

The downside to github is that they're more likely to be vigilant about content they fear could give them legal trouble.