Debugging

2026/08/26

Type
Learning Resource
Format
Glossary Article
Version
General
Subject Tags
Code
MIT
Game Assets
2016-2026, GDQuest© - All rights reserved
All else
2016-2026, GDQuest© - All rights reserved
Created
2026/08/26
Updated
2026/08/26

Debugging

When writing code, you will inevitably introduce bugs. A bug is something that messes up the program and makes it do something you didn't want it to do.

Debugging is the process of finding and fixing problems in your program. To be more specific, it is the process of figuring out what code actually does, comparing it with what you intended, and making changes to the program to make it do what you intended.

The word "actually" is important here: The computer just does what your code tells it to do. It doesn't try to interpret what you want it to do.

One of the first rules of debugging is to assume that the mistake is in your own code because most bugs are in the code that we wrote. Don't dismiss bugs as someone else's problem (even when it's not your fault). Part of our role as developers is to provide users and players with the best experience that we can.

Become an Indie Gamedev with GDQuest!

Don't stop here. Step-by-step tutorials are fun but they only take you so far.

Try one of our proven study programs to become an independent Gamedev truly capable of realizing the games you’ve always wanted to make.

Nathan

Founder and teacher at GDQuest
  • Starter Kit
  • Learn Gamedev from Zero
Check out GDSchool

You're welcome in our little community

Get help from peers and pros on GDQuest's Discord server!

20,000 membersJoin Server

Contribute to GDQuest's Free Library

There are multiple ways you can join our effort to create free and open source gamedev resources that are accessible to everyone!

Site in BETA!found a bug?