Stages of building a game

Discussion and feedback on Construct 2

Post » Sat Oct 01, 2016 7:09 am

Hi All :)
Can you share from your experience, what would be the stages of building a game?
is there a right way to build a game?
is it better to start the building process right ahead? or some of you start with the art?
if you have tips and tricks I will be happy to hear :)

Posts: 56
Reputation: 548

Post » Sat Oct 01, 2016 7:14 am

The way I've been doing it as least with my current project.

I work on a batch of features at a time. Could be a bunch of small things or a more full release with two or three major implementations like a camera system or new usable items. I keep a txt log where I document changes, and go from build to build like 'pre-alpha build 0.3'. Keep building said builds until you feel you're ready for a stable release, whether for real or get people to help squash bugs you've found in the current build.
Zelda Gamekit (my project)

Example capxs:

Zelda-Style Inventory

Zelda Health

3-saveslot system

[url=]Zelda-like Dialogue[
Posts: 534
Reputation: 19,620

Post » Sat Oct 01, 2016 7:45 am

I would always say work on the core mechanic using crude placeholder sprites, if the game is fun/works, then the art time is justified. I think I would change that rule only if the art was essential to the mechanic. Once core mechanic is fine, move onto next accessory mechanics.
Posts: 45
Reputation: 2,340

Post » Sat Oct 01, 2016 11:55 am

@DankP3 is right. It's a common method to start with placeholder images. Also, don't forget to keep your ideas/notes/workflow organized. Use Trello ( ) or something similar.
Posts: 1,557
Reputation: 20,717

Post » Sat Oct 01, 2016 3:38 pm

I would consider that the stages for game development go like this

Prototyping: Core mechanics
At this stage there is no game fluff. It's only testing out the basic mechanic and find out it it's fun. It's also the stage that let's you find out the hurdles of designing the mechanic. This is also the stage to try out the mechanic with friends to get an opinion on their experience. That way you can also fine tune the mechanic. Also try out multiple mechanics separately if the core idea isn't alone in the game concept.

Pre development
Plan out how the core mechanic will be designed know that you know the complexities. Find simpler ways to build the core mechanic for being used in a flexible manner. Also start planning out how the fluff interacts with your game. It's a good idea to document this for reference.

Alpha Development

Grey box the UI and Meta features
A lot of people will go from mechanic prototype and then wrap around the meta/ui and other features. This is a bad idea. Start by building up your menu's, and game design flow.

Build up your data model and data interaction
Some games require changing data. Such as persistent leveling. Level information whatever it might be. Make sure this is designed. You can go back and make changes as required.

Rebuild your core game mechanics into the the system
That old version you prototyped. Scrap it. learn from it. As your building your new one you know are integrating it into the rest of the game. You have laid down everything else. So now the actual game mechanic can be built on a solid foundation.

Integrating graphics and audio
Once all of this is in place start implementing the graphics, audio and other stuff.

Beta Development
At this point start having people test your game. get feed back. Make changes to improve the game. Release when done.
Posts: 2,455
Reputation: 15,028

Return to Construct 2 General

Who is online

Users browsing this forum: No registered users and 13 guests