AngelModder Posted April 7, 2015 Posted April 7, 2015 Is there a way to install a password or some other form of security on out pk3's so that only the game can use them? One of my recent projects has material that I do not want ANY ONE messing with and or using.My feeling's on this are, I made it, it's mine, make it your self. I've recently discovered a group that had entity modded one of my maps, I am NOT happy about that either.Any ways, is there a way to lock them? Perhaps set the materials within to read only or some thing? Smoo likes this
eezstreet Posted April 7, 2015 Posted April 7, 2015 No. That would require some recoding of the game, and as we found out with JKG, some tools (like WinRar) have tools to bypass encryption. AngelModder likes this
Raz0r Posted April 7, 2015 Posted April 7, 2015 If the game can read it, how can you tell that the malicious person trying to open it isn't "the game"?Encryption and security is very difficult, there are fundamental concepts that people overlook. The only thing you can do is make it difficult. eezstreet and AngelModder like this
Didz Posted April 7, 2015 Posted April 7, 2015 As long as your players' computers have the capability to decrypt the content in order to present them in-game, their computers will also be able to just decrypt the content to extract it onto their hard drives too. No technical measure will prevent this. Your options are 1) get a lawyer, 2) don't release your content, 3) ignore it. Reverse Engineering is also a right protected in the U.S. (DMCA) and the EU (Directive 2009/24/EC). I played JKA for the modding aspect, and entity modding was one of the most enjoyable ways of thinking out-of-the-box while creating fun experiences for players. I don't see how experimenting with entities in maps could be in any way disrespectful to the original creator, unless they're also redistributing repackaged PK3s. Smoo and Raz0r like this
Cerez Posted April 8, 2015 Posted April 8, 2015 An interesting idea -- though, I'm not sure why you would want to forcefully lock everyone out when you are sharing your work with the world -- but passwording is never secure. Your best bet is to clearly state in the readme that you do not wish anyone to modify and adapt upon your work, and to send a warning to those who have done so without your permission.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now