And I'm glad they didn't. Protecting the installer keeps honest people honest. Protecting the runtime after installed means reduced performance and/or support headaches. That said I hope the developer didn't pay too much for this copy protection when some bespoke checks on the installer would have sufficed.
I'm just glad they didn't use iLok. It's been a pain for me as a legitimate user of a few iLok protected plugins.
I'm just glad they didn't use iLok. It's been a pain for me as a legitimate user of a few iLok protected plugins.