Required new functionality to allow easy update of DRM protected LUA

[rainersc]

As a LUA Developer in DU i want an easy possibility to allow my customers to update their LUA. As it is today, the only way to "sell" LUA code without open sourcing it is to sell a whole DRM construct under your own creator ID. If the original creator wants to make an update available to his customers, this can only be done manually on a per construct level and has to be done by the original creator due to DRM. tbh, as it is today i am often holding back LUA code as i simply do not want to end up into having a full time job in DU just taking care of updates etc. We need an easy mechanism that enables us to support our customers. One possibility would be something like a LUA Update data element that could e.g. be sold or given away for free via a dispenser. This Lua Update data element can then only be applied once to a Construct and would re-apply the LUA to an existing Seat / PGM Board. Like a self destroying USB Stick that updates a constructs LUA

Without a possibility like this, we are stopping the developments / distribution of new LUA stuff, as usually a developer does not like to end up in "support hell"

[NQ-Ligo]

Hi there !

I understand completely your frustration, I can confirm that we are considering an idea of "itemization" of Lua configs in our project.

But obviously, this takes a lot of time to work and requires resources. So we will certainly not be able to do it before the release, but potentially after the release.

(Side note: Thanks @Archaegeo for maintaining this github and making the Lua community work together ;) )

[samdeane]

Just to chip in with a +1, the generalised solution that @NQ-Ligo mentions - where you had something like a blueprint which could be traded between players, and which applied a script to construct, would be awesome. It could be used for updates but also for primary sales of scripts.