How does looking at the code expose you to potential legal liabilities? I'm a bit confused by that.
I will reflect on this though. This is my first time commercially distributing software, and my priorities for the license were for it to protect my IP without being overly restrictive. However, I've had a few people in separate spaces raise concerns with it, and I want my software to be as accessible as possible without compromising my ability to profit from it or expose myself to liability or "theft".
I'm the sole developer of Stipple Effect, so I can update the license with a future release if I feel compelled to do so.
It doesn't matter to everyone but it does move the needle for a subset of people. I love to read my tools' source and fork/hack on/contribute to them.
I also don't see how the license prohibits you from doing what you expressed, though that may be an oversight on my part. I'm happy to be educated or listen to what specific concerns you have about how the license or distribution model limits what you would hope to get out of the program.
I'm just niche and not in your market :D
Do you mean you have some kind of Aseprite plugin, or are you just hot reloading the sprites?
Yea, there's some strange clauses in the eula. For example, the eula stipulates that your operating system must be validly licensed.
> on your computer running a validly licensed copy of the operating system
I don't see how or why this is important at all. In other words, pirated copy of windows is disallowed from using this software.
Not that i have any issues with the eula in general. I think this is good enough to be a paid piece of software. It's just weird to see a clause about the operating system itself.
As far as I can tell, stipulating that end users must be running a validly licensed OS helps protect the licensor (me) in situations where a cracked OS with malware corrupts my software or compromises the whole system.
1) Aseprite is already king in this space, yes, this may be more automatable but asesprite already wires into my engine. In my engine, I can write code to preview behaviors in more or less realtime on file save.
2) what's with the Eula? This is not an open source tool, but it appears to be a source available tool with some strict requirements. I cannot distribute the code or binary, which means that even looking at the code could potentially introduce legal liabilities for me. As an indie, not a risk I'm willing to take. (I have this complaint about Aseprite too, fwiw)