We see a lot of Unity games every Ludum Dare. In the past, I’ve heard some griping about this, but let’s face it: Unity is perfect for game jams. It has its quirks and limitations, but when time is of the essence, you can’t beat a platform that’s easy to work in and lets you forget about the basics, and jump right in to seeing your idea in action.
However, this can be a bit of a mixed blessing: because Unity handles so much for you behind the scenes, there’s a few steps that are easy to forget about when it comes time to package up your game and submit it, but which go a long way to polishing up the impression your game makes on people rating it. Unity’s gotten a lot better at handling these things in a sane manner, especially with version 5.3, but it still benefits your game to give things a once-over.
If you’re not using Unity, feel free to ignore this post, but if you are – read on! I’m mostly going to be focusing on standalone builds, but it’s a good habit to get in the practice of thinking of these things even when you’re intending on making a web game.
