Quote: "Wow, does that mean I have to stop sharing the tools I make for AppGameKit?!"
This, this, this is exactly what I had in mind when I wrote the post before yours. Your tools are awesome.
You might have never heard of me, as I am new to this forum. But you have been one of my inspirations to make my own tools and of course use the tools of others. You are literally all over this place and it is as far I can judge a good thing.
I've been using your tools, actually not yet, but I tested some of them and plan on using them somewhen when I finished base/tool coding.
It would be a real shame and a loss for the community if things like your tools and those of others of course would be endangered by this EULA. The good thing is, I guess, that I have not seen one adverse reaction to someone posting tools.
The bad news is, that as long as there is no definite clarity, people could pull the plug anytime.
Thank you baxslash for not only making them, but also providing them to the community.
Quote: "..sounds like anything created with AppGameKit Tier 1 as people can easily go into your media folder and take anything out they want. That's not to say they are legally allowed to, but it's possible..."
Exactly, also it reads as if just near misses graphic/sound asset libraries regardless of their copyright holders terms. Just the word software seems to save us here, while 'software' is often used in the very same licenese agreements for graphic/sound/text/music assests as kinda placeholder, as most of the standard licenes were originally made for software and read weird if the product is not really a software in the end.
Also
Quote: "(d) create, in strict accordance with the associated documentation, unlimited Apps (as defined below), and copy and issue copies of these Apps to the public in object code format only, and subject always to the provisions of section 4 below."
Does this mean, that code snippets or the decision to make a whole game available with source code is not allowed either? Dunno what "object code" means though. But I assume it's the bytecode.byc?