Hi everyone,
I’m working on an invoice verification system for a tool I’ve published on the Unity Asset Store. The goal is to verify that users have legitimately purchased the tool by prompting them to enter the invoice number from the email they received after purchasing the tool. The system will then validate the number against a server I’m setting up (using AWS Lambda and API Gateway) that queries Unity’s Asset Store invoice API to check if the invoice exists.
Before finalizing and implementing this, I want to ensure that it complies with Unity’s Asset Store EULA?
Thanks in advance for your input!
I’ve got the invoice verification system fully implemented and working, but I’m starting to second-guess whether it’s worth it.
On one hand, it’s a solid way to deter piracy and protect my work. On the other, it adds a system I’ll need to maintain indefinitely. Even though it would only cost pennies to run it, what happens when I’m no longer working on the tool? Keeping the service running seems unnecessary at that point.
Plus, since the verification script isn’t pre-compiled, it’s easy to bypass by editing the code to skip the API call. My hope was that it would still stop the majority of would-be pirates, but now I’m questioning if the effort justifies the results.
At this point, I feel like the sunk cost fallacy is the only thing keeping me from scrapping it.
I’d love to hear your thoughts!
Hello,
Any form of DRM is not allowed. Please do not add this to your tool. You’re welcome to ask users to verify their invoice before providing them support on Discord or via email, etc, but you can not block users from using the asset they license.
Thanks