How to protect the module?

[Legacy_WhiteTiger]

               How to prevent the toolset from opening module?*
               
               

               
            

[Legacy_Kato -]

               

Do you mean preventing the toolset from opening a module? As far as I know it's fortunately unfeasible, how could that "protect" the module anyway? If you're working in team and too many builders have access to the same file, you might set permissions accordingly in your OS(or your file sharing website). Alternatively you could provide your builders different copies of your mod so that they only have access to the content you choose...

 

 

Kato

               
               

               
            

[Legacy_kalbaern]

               

If you give us the "why" for your request, several of us could likely discuss other options to help meet your need (like Kato's post above), but there is no way to lock the module per se.

               
               

               
            

[Legacy_WhiteTiger]

               

Protect the module for copyright reasons and avoid the creation of fake versions or someone creating a server online of my module without my permission. I was thinking on create a Special Version in SinglePlayer mode or Multiplayer 2-4 players of my module to play only OFFLine.

 

I was builder in Warcraft III and all my modules of there was protected by a Chinese Program that cause Crash to Toolset if try open the module before extracting the files (the scripts is found in bad format of read and other things to difficult the modification of the module if you try to open it without toolset)

               
               

               
            

[Legacy_Pstemarie]

               

I think you worry too much. I'd venture to say that ALL of the Community Members here have a healthy respect for creator rights and would certainly not duplicate your server without seeking your permission first. For example, WORM released Arbor Falls - arguably the best server created - to the community years ago and not a single person ever tried to duplicate his server. If anything they'd download the released version for inspiration and to see how WORM did things. The same thing would happen with your module.

 

I understand the work you've put into your server, but the greatest strength of this community has always been its willingness to share - which you have done by creating a server. If you're that concerned about people duplicating your server, then don't release the source code. Alternatively, you could post a version that weedles out all of the persistent functionality - since it wouldn't be needed for single player or multi-player use (well, with a DM that can save progress before closing the module). 

               
               

               
            

[Legacy_WhiteTiger]

               I forgot to say, I would share the "special" version of my module in the vault. I'm thinking about this popossibility


I am not sure about publish the new version on vault
               
               

               
            

[Legacy_Fester Pot]

               

Yes, there is a simple way to do so - save a script. When in the /temp0 directory while your module is open, modify the script name with an ASCII character. Then, back in the toolset, save your module. The ASCII character script will be saved when the module in the toolset is saved into .mod format.


The toolset will fail to open the module when it attempts to unpack the module into the /temp0 directory, forcing a manual process kill of nwtoolset.exe.




Pressing OK kills the module from finishing to unpack, leaving the module/temp0 directory empty of files, thus, unable to open in the toolset.

 

I suggest having a backup module too, so you can at least open that in the toolset to continue building.


FP!

               
               

               
            

[Legacy_meaglyn]

               

I think you mean a non-printable ASCII character...

 

But also bear in mind that there are erf extraction tools which will open up the module anyway. If you are concerned about sharing your work then don't share it.  It is also worth remembering that you are probably using a lot of content from people who have willingly shared things with the community. 

               
               

               
            

[Legacy__Guile]

               I don't see why you would be worried about this other than someone at your location trying to edit the module without your permission, unless you feel like people are hacking your computer for your module (doubtful), nevertheless, you could always keep the module on a USB drive & at least 2 other external mediums of storage (as a main plan for back up) and simply copy it from the external medium to the nwn's "modules" folder when you wish to edit it....

You may want to drop $20-$30 bucks on a few USB 3.0 back up drives (16 GB +), it's definitely worth the money!!!!

(I keep all of my personal data & data I don't want falling into other people's hands off my computer entirely, and especially off the net!)