Enough chickens, let's focus on bugs

These past few weeks, I've been focusing mainly on re-releasing Chicken Farm, a game I developed a while ago and had "in a drawer". I've even managed to reach an agreement with another indie developer who's trying to port the game to F-Droid, an alternative app store for Android.

But the main project remains Canyon Assault. Right now, the most important element missing is the script.

For now, we have a plane at the bottom of a canyon with a pilot and an artificial intelligence, and we know they're going to fly through it, and that it will flood as they advance. We also know that they will then enter a mine in which they will have to activate a series of volcanoes and that they will finally have to face the monstrous "boss" of the bugs.

We know what's going to happen, but we don't know the reasons or the context. Why do they have to assault the canyon? What time and place are they in? What are the bugs? How can they have that technology? These are all questions the script must answer.

And there's one more question you might ask: is a script necessary? Many games don't have one (or we don't care about it) and they work perfectly.

The main reason for including a script in the game is that our pilot has a companion who is an artificial intelligence, and I want them to maintain a dialogue with each other that makes the experience more enjoyable, especially during transit times.

Anyway, I'm compiling some loose ideas I had and have started turning them into a script. To do this, I'm using the device in the photo at the top, which is an AlphaSmart 3000. Its main advantage is that it's specifically designed for writing and doesn't include any features that could make it a distraction.