Sponsored By

New School Blues Dev. Diary #23: Packaging Part 2

YoyoBolo Games continues its look at packaging a fully developed game with this December 11, 2012 entry on code obfuscation. Read on for an introductory take on the fundamentals of making your game's code all messy like!

Yoyo Bolo, Blogger

February 15, 2013

1 Min Read

Making sure that New School Blues is ready for approval by a web portal demands a few steps that may differ according to the website in question.  While many sites we looked into have similar processes of submission we should stress that we haven’t seen them all and things could be handled differently in different places.

That being said, there are two major steps that YoyoBolo is doing to get NSB ready for submission.  The first is to add a line of code from the hosting site to our code.  This authenticates the game, and makes sure that not just anyone is uploading it.  Next we upload the game to them.  Since we’re using Flash, it’ll be in a swf format.  Just before that though, the swf needs to undergo a process called obfuscation.

image

An example of pre-obfuscated code (unrelated to code below)

Obfuscation of code basically means we take our original code and encrypt it (encode or mix it around) so that it’s hard for people to look at it later, figure out, and/or reverse engineer.  This basically makes it more secure and less likely for people to mess around with.  Many obfuscation tools are free and readily available.

image

An example of obfuscated code (unrelated to code above)

It’s important to remember though that obfuscation doesn’t make the swf impossible to crack, just more difficult.  Luckily since the game is being hosted and distributed by a web portal they have their own added encryption tools, so we get double the protection!

Read more about:

2013Blogs

About the Author(s)

Daily news, dev blogs, and stories from Game Developer straight to your inbox

You May Also Like