UPDATE: GAME IS NOW RELEASED ON GOOGLE PLAY!
NOW ON AMAZON APPSTORE FOR FIRE TABLETS!
Hi everyone! Apple Spider is my first release-worthy project in Defold, and it’s been a great experience so far.
The general idea: Spiders are taking over your apple orchard, so you need to fight them off. Throw apples to smash them and make Apple Spider (like apple cider… I know it’s a terrible pun, but I’m a dad ). Spiders appear on-screen in random spots. The speed of generation increases as you level-up. You have a few styles of attack (hand, package, and gatling gun), and some special items to help you (rain and bug spray).
I suppose it’s a casual arcade game? This evolved from me joking around with a clicker game concept, and gradually adding more complexity until it seemed fun.
I’ve spent many hours fine tuning the difficulty progression, and designing the scoring system to encourage some strategy. For example, there are bonuses if you do not waste any ammo.
Also trying quite hard to make the UI & overall experience feel semi-professional as well.
I’m likely going to target Android and Amazon first, then maybe try out Facebook Instant Games.
Gameplay clip:
What I’m liking about Defold (compared to LibGDX):
- Development feels so much faster! The speed at which I can experiment feels so much higher. I attribute a lot of this to the message passing system and choice of a dynamic scripting language.
- Integrated editor and tooling. Atlases, fonts, particle fx, are all way quicker to create & update.
- Effortless performance.
- Automatic asset loading.
Challenges so far with Defold:
- Lua has taken some getting used to. I’m so used to C# and JS in my day job.
- I’m starting to wish Amazon was considered a different native platform. I have to use a different advertising SDK for Amazon release, since many ad networks aren’t fully supported on Fire devices. I had success using the Enhance extension, and configuring it to use Amazon & Vungle ad networks. On the Play Store I was likely just going to use Unity ads to keep the bundle smaller. Anyone know of a simple way to handle this, besides maintaining an Amazon-specific git branch?