Find content
Male
The model for your license is almost identical to one that I needed for a project of mine. The only solution that made me happy was writing my own license. Looking at BSD, MIT, and other commercial licenses should give you a good idea on what you need to include. Just make sure that it's very clear that you hold zero liability for its use, and that it may only be used under the conditions you specify. Lastly, make sure the license contains your name, the date, and some contact info so the rightful owner of the project and license (you) is correctly identified.
#4993573 Need advice for going open source
Posted by
on 24 October 2012 - 04:09 PM
#4959405 Ways of forcing players to play together without risk of getting griefed?
Posted by
on 15 July 2012 - 07:04 PM
What you're describing is classic griefing gameplay, you are suppose to work as a team to accomplish a goal. You are dropping the rest of the team under the assumption that you're "higher skill" (chosen tactic to win) is more important then the experience of the players your suppose to be playing with.
But that is not true, as we clearly defined in this topic that griefers don't play to win. We had a winning strategy, just not one that everyone was competent at. Until you consider a wider array of possible ways to play your game (and not to mention, agree on a definition of griefing), designing a way to prevent griefing will either be impossible, counter-productive, and/or impact your target audience.