Jump to content
  • Advertisement
Sign in to follow this  
  • entries
  • comments
  • views

SquaserZ - Devlog #1

Sign in to follow this  


Introduction Note: This post is divided in two sections: a brief presentation of the game, and the first devlog entry. Additionally, I post here also the current playable build of the project, for both Windows and Android systems.


After failed attempts at starting a game project, due to the sheer amount of crazy ideas I tend to have, I tried to hear all the words the wise say and: try to keep it simple.

And as such, I have embarked in a journey to make my first project: SquaserZ.


SquaserZ is a one-goal game: survive as long as you can, avoiding everything red. The player is always moving, following a certain direction, and the only way to control it, is to stop it and move along a new path.

In your journey, you will have some cruel and outlandish obstacles, such as bombs, missiles, twin-evil-brothers and of course, laserz.

The cruel nature of the lasers.

The even crueler nature of the bombs.

Each round consists in surviving a specific obstacle, having some time to "breath" between levels. However, as we progress the game, there comes a time where a "Special Round" appears and a barrage of non-stopping obstacles come to try to kill us.

The special round.

After the introduction of the game (you can read more here: https://sardinecorp.wordpress.com/2017/01/06/the-problem-with-squares-and-laserz/), I post here my first devlog entry.

Playable Build:

Android Build

Windows Build


Devlog entry, #1: Implementing further systems

Reflecting upon the decisions I make on this project can be hard.
On one side, I want it to be as simple as possible, to mark the first step in my path in game development. On the other hand, I want to make the best that I can, within my current abilities.

This is to say that, even though I had some feedback that the game is "good for release", I want to add a final touch: a simple objective-based system similar to the ones seen in Race to the Sun.

Objective 1 - Implement a Objective-Based System

Before each round, the player is presented with a set of 3 objectives. If he want, he can try to complete each of those objectives.
When an objective is completed, a message appears on screen to give feedback to the player
The objectives have different levels. In the first level we are asked to "run" for 100 px, the next could be 500, for eg.

As such, I have created the following list of objectives types to include in the game:

  • "Run" for X pixels
  • "Run" for X pixels without dying.
  • Reach level X.
  • Get killed by enemy X.
  • Complete a "Special Round"
  • Stay X seconds on the same spot.
  • Collect X objects.
  • Touch the walls X times
  • Touch a corner of the screen X times.
  • Do X impulses on one round.

    Looking at the list, it seems that the objectives are "cliche", however I'm having a hard time devising more objectives with the current constraints of the game.

    Issues and Questions

    At the moment, I'm having some issues devising a UI for this game. At the same time, I'm having some doubts in whether I should implement a collectible system to unlock some skins/whatever. The following list gives a summary of the current Issues and Questions:

    • [Question] Should a "pause" button be placed on the game? I'm having a hard time implementing this, since the player could want to go to that particular part of the screen

      • [Possible Solution] The "pause" button could be replaced by the "back" key on mobile phones and "ESC" on a computer

      • [Question] Are "collectibles" worthwhile implementing on this game?

        • [Possible Solution] If the objective-based system is developed, they could only be placed when the objective in question is active

        • [Question] What is the main goal of the objective-based system?

          • [Possible Solution] Each objective could give X amount of XP in order to level up. Each level could unlock either a skin or something else, to be debated.

          • [Issue] At the moment, it is possible for the player to get stuck within the pieces of geometry left by the explosions. I still do not have a solution for this.

            Looking at the work ahead, I am curious to see how my programming skills will evolve.

            Devlog entry - END

            Starting from this devlog, I will update the current situation of the game, and check if the objectives were completed or not. Furthermore, I will analyse in more detail the issues and questions and see if I could find a feasible solution for them.

            Additionally, if possible, I would like to ask a question: am I proceeding correctly with this type of devlog? Or should I develop the issues more thoroughly? (I am using this devlog in order to improve myself and the game too, being this my main personal devlog).

Sign in to follow this  


Recommended Comments

There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!