Packt's discount offer for the Stencyl book has ended, so here's an offer from me... My Stencyl Game Development video course on Udemy is on offer for $15 (normally $99!) until the end of December 2015.
There are more than 7 hours of video tutorials, and there are currently almost 500 students enrolled. There's a 30 day money-back guarantee, so you have nothing to lose!
Click here to see the details of the course.
The Duke Dashington competition to win 1 of 2 copies of the game for iOS devices is now over.
Winners have been notified by email, and must respond to the email by midday 7th October 2014 in order to claim their prize. Winners will be announced on the same day.
Thanks again to Adventure Islands for donating the prizes.
You can read the review here, and buy the game for iOS at the App Store, and for Android at Google Play.
Sometimes, errors in our code can be incredibly difficult to find. If we make a major error such as trying to refer to an object that doesn't exist, then when the game is running, we'll at least see an error message telling us that there is a problem; we're given a clue as to where we need to start looking for the problem within our Stencyl code.
However, some errors are not so easy to track down because they are not syntax errors (i.e. 'illegal' code'); our code just doesn't work as planned. These errors are somewhat trickier to locate, and can take hours to resolve. Even more annoyingly, we can spend an age looking for such errors, only for another coder to glance over our shoulder, and immediately spot the problem! Sometimes a bit of luck may have been involved, but more often than not, it's experience that can assist in locating certain types of error.
The purpose of this article is to discuss refactoring, or rearranging code, to make it easy to read, and to assist in eliminating or (more realistically, reducing) the introduction of errors into our code.
When we transferred to our new-style blog in January 2014, we were unable to easily transfer the blog entries from the old system into the new.
We have finally found a way to recover and convert the archives, but it's quite time-consuming, so we're only going to be resurrecting relevant and useful blogs containing tutorials. The process will take some time, but we'll release each entry as soon as it is ready for publication.
All of the older blog tutorials were created in Stencyl 2.x, which has now been superseded by v3.x, but the instructions should still work. If you notice any problems please do leave a comment, and we'll update them where possible.
Please note that the converted blog entries will appear in the correct chronological order, based on the date that they were originally published, so you'll have to scroll to the oldest entries on this blog page in order to see them! However, to save you some trouble, here are links to the first two converted blog entries. We hope that you find them to be useful...
ABOUT STENCYL ATTRIBUTES (AND A BIT MORE DEBUGGING)!
STENCYL EVENTS : DO THIS ONLY ONCE (PLEASE)!