Please do explain why you think its bollox. I am genuinely curious as to why people think adding copy protection / locking a "map" is a bad thing. (thats not intended to sound snotty btw

)
OK, I'll try an explain with an analogy within my industry.
Company 'x' decides to build a multi-billion dollar asset and chooses control system 'y' (the ECU of the asset) from company 'z'. Company 'z', under contract supplies company 'x' with said control system.
Once the control system (ECU) is installed, company 'x' is free to choose whether company 'z' tunes the control parameters (mapper), whether to choose to tune using in-house specialists (self tune) or whether to sub-contract to outside tuning specialist (tuner).
The interesting part here is that company 'x' is also free to choose whether to lock the control system or not, it is not company 'z' that decides or controls access but the OWNER, legally. Also, company 'x' is free to make changes as they see fit which has no bearing on any legal recourse for company 'z'.
As with an ECU, the control system is tuned for a specific asset, even if you cloned the asset, it would require tuning separately as no two assets operate exactly the same.
As I see it, there is no IP on mapping as all that any mapper is doing is manipulating control parameters, they are not writing new functionality, merely choosing standard library functionality. Hence why the mappers I use see no reason to lock MY ECU as I OWN IT, not them and I paid for the tune, which is my property, NOT THEIRS.
Edit: The IP is the software within the control system/ECU, not the map.
Just my opinion but everyone is free to disagree
