MCM Resource Anti-Piracy Placeholders - Historical

Applied By Justis R: May 30, 2019 at 11:05 PM

MCM Resource Anti-Piracy Placeholders
Old VersionNew Version
1[CENTER][SIZE=7]Resource Anti-Piracy Placeholders[/SIZE][/CENTER] 1[CENTER]
2 2[SIZE=7]Resource Anti-Piracy Placeholders[/SIZE]
   3[COLOR=#ff4d4d]NOTICE - This is a draft. The feature is not yet available.[/COLOR][/CENTER]
3[INDENT]To offer MC-Market’s resource creators the utmost means of self-protection when publishing their resources, all resource categories offer placeholders which will be used to inject the download information at their locations every time the resource is downloaded. 4[INDENT]To offer MC-Market’s resource creators the utmost means of self-protection when publishing their resources, all resource categories offer placeholders which will be used to inject the download information at their locations every time the resource is downloaded. 
4This information can be used to identify any users who have leaked your product, identify the exact version which was leaked, and even develop your own DRM system.[/INDENT] 5This information can be used to identify any users who have leaked your product, identify the exact version which was leaked, and even develop your own DRM system.[/INDENT] 
5 6 
... ... 
20[B][SIZE=5]Usage[/SIZE][/B] 21[B][SIZE=5]Usage[/SIZE][/B] 
21 22 
22[INDENT]If you’re going to use these placeholders for anti-piracy purposes, we strongly recommend that you utilize several of them, in order to ensure that misleading information cannot be edited into your resource prior to it being leaked, in an attempt to frame another downloader. 23[INDENT]If you’re going to use these placeholders for anti-piracy purposes, we strongly recommend that you utilize several of them, in order to ensure that misleading information cannot be edited into your resource prior to it being leaked, in an attempt to frame another downloader. 
  24Note that the username placeholder is a poor choice as an anti-piracy measure, since it’s so easily identifiable to crackers. 
23 25 
24Files are read in utf, and if an occurrence of these placeholders is found, it is replaced with the respective download value. The exceptions to this are .zips, .jars, java .class files, and .rars. 26Files are read in utf, and if an occurrence of these placeholders is found, it is replaced with the respective download value. The exceptions to this are .zips, .jars, java .class files, and .rars. 
25[I].zips[/I] and .[I]jars[/I] are opened and processed as directories. 27[I].zips[/I] and .[I]jars[/I] are opened and processed as directories. 
... ... 
49Our most effective option is to ensure that whatever DMR systems we include in our product, they are well hidden and or very difficult to remove without impairing the functionality of the product. 51Our most effective option is to ensure that whatever DMR systems we include in our product, they are well hidden and or very difficult to remove without impairing the functionality of the product. 
50Be creative. Be unique. If you follow suit with what every other developer is doing, crackers will expect those methods to be used, and will know what to look for when opening your product. It is for that reason that we are not listing specific methods here, nor do we offer a standard injected DRM system. 52Be creative. Be unique. If you follow suit with what every other developer is doing, crackers will expect those methods to be used, and will know what to look for when opening your product. It is for that reason that we are not listing specific methods here, nor do we offer a standard injected DRM system. 
51 53 
52If you do have your DRM system disable, delete, or otherwise change the experience of the product when a leak is detected, it is recommended that you keep identifiable data separate from that functionality, so that if is removed, the data needed to trace back the copy to its original downloader, and the leaker can be removed from our website. 52If you do have your DRM system disable, delete, or otherwise change the experience of the product when a leak is detected, it is recommended that you keep identifiable data separate from that functionality, so that the data needed to trace back the copy to its original downloader is not removed, and the leaker’s MCM account can be banned.
53[/INDENT] 55[/INDENT] 
54[SIZE=5][B]Limitations[/B][/SIZE] 56[SIZE=5][B]Limitations[/B][/SIZE] 
55[INDENT] 57[INDENT]