Protect, obfuscate and sitelock your HTML5 games and your JavaScript scripts with JScrambler

Emanuele Feronato HTML5, Javascript, Reviews

Protecting your hard work has always been a priority. In the making of your latest HTML5 game, you invested lots of hours in developing your JavaScript code.

Unfortunately, everyone can read it just looking at the source code of the web page your script is running into. In other words, you wrote a script you are basically giving away for free.

By accessing to your source code, another programmer can:

* Violate your license agreement
* Steal secret algorithms
* Steal your code, to reuse it
* Leak altered versions to the Internet

That’s why you need a tool to protect, and obfuscate your source code: JScrambler

With JScrambler you can:

* Protect your Web Game code without hurting performance
* Enforce your licensing
* Domain lock your code
* Discourage others from stealing/hacking your code

Let’s see how it works, testing it on the script I made in the post introducing SUPER JUMP in your HTML5 platform games. This is the original code:

JScrambler has a lot of options to tune the obfuscation but it also provides a quick wizard to complete the process in a couple of clicks:

And this is the output, without sitelocking or date restriction so you can even test it on your own:

Obviously, the game is working:

WASD key to move the green character.

No doubt JScrambler will be my tool to encrypt games and projects

From null to full HTML5 cross platform game

I will take you by hand from the bare bones of JavaScript programming through the creation of a full cross platform HTML5 game, with detailed explainations and source code.

If you don't know where to start, then From null to full HTML5 cross platform game is the book for you.

Comments 3

  1. EarthwormJeff

    Nice work, I just wanted you to know that WASD key is keyboard layout dependent… So on french azerty keyboard, it is really not useable. Maybe, you could get the key code instead of the letters… (or just use the arrows) @+

  2. focus

    Looks like you didn’t used full obfuscation power for the code snipped you posted. This is how your code looks like after first deobfuscation pass (just beautifying one):
    It is already readable, strings are not encrypted at all, variables values (32, 15, etc.) are easily accessible and not obscured, etc. It looks like minifier rather than obfuscator in your example.

Leave a Reply

Your email address will not be published. Required fields are marked *