Give your HTML5 game a new level of protection thanks to JScrambler 5.1

Protecting your hard work and your intellectual property should be one of your priorities, once you spent lots of hours in developing your JavaScript code to create your latest HTML5 game.

Running in a browser, or in a virtual environment like the one created by wrappers like Cordova, 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
* Make reverse engineering to your algorithms
* Steal your code, to reuse it
* Leak altered versions to the Internet

That said, you absolutely need to protect your code in some way, and i found the best way to be JScrambler.

I am using this tool for some years to protect my code, and I have to say I am keeping an eye on its free and paid competitors too, but I believe JScrambler is the most advanced way to protect your code.

Let me be clear: it’s impossible to COMPLETELY protect a game, I mean, there are cracked versions of Skyrim ready to be downloaded around the web, but using JScrambler you will make pirates’ lives that hard they’ll probably prefer to code a game from scratch rather than steal yours.

With its 5.1 version, there are various important improvements, including:

* Synergies across transformations – some transformations now work together to provide a higher degree of obfuscation and protection to your code.

* Targets – which allow you to choose which type of JavaScript primitive types/expressions you want to target.

* Compatibility – Jscrambler is now compliant with the ES2015 spec.

* Better default templates – made templates more suitable to common use-cases like HTML5 games.

* New and Improved Node CLI – customize the behavior of interactions with Jscrambler’s API.

* Refreshed UI & App Dashboard – the UI has been revamped offering an easier protection process and a more efficient organization of your projects.

That said, let’s take the JavaScript source code of “zNumbers” game level generator, and here’s what I got:

The code is really unreadable, and if you try to beautify it with some tools like Online JavaScript Beautyfier, it’s still unreadable:

I can’t even find the strings I am sending as output in the console.

Making your game source hard to understand is a “must do” if you plan to get into game design seriously, and JScrambler is definitively the best tool out in the wild.

More tutorials and guides about code protection using JScrambler will follow, stay tuned.