5) Debugging and Problem Solving

Back to Getting Started

A Professional Debugging Habit

Debugging is not a sign of failure. It is a normal and expected part of programming. The key is to debug systematically.

Step-by-Step Error Workflow

1. Run your code.
2. Read the first error in Messages.
3. Go to that file/line and fix only that issue.
4. Run again immediately.

Many "later" errors disappear after fixing the first one.

When Code Compiles but Behavior Is Wrong

• Print key values with DebugPrint.
• Check whether your conditions are actually true when expected.
• Verify loops are entering and exiting at the right time.

DebugPrint("state=" + Str(state) + ", x=" + Str(playerX) + ", y=" + Str(playerY))

Using Breakpoints Effectively

• Set breakpoints on executable lines only.
• Pause just before suspicious logic.
• Step line by line and observe variable changes.

Common Logic Bugs

• Input bug: using KeyHit when you need continuous movement. Use KeyDown for hold behavior.
• Render bug: forgetting Cls(), causing visual trails.
• State bug: not resetting values when changing game state.
• Resource bug: loading assets repeatedly in the loop instead of once before the loop.

Practical Troubleshooting Checklist

• Did you save the file before running?
• Is the intended startup tab marked as main?
• Are paths and file names correct for assets?
• Are all required end statements present (End If, Next, Wend, etc.)?

Navigation: Previous: Game Development Concepts | Outline | Next: Learning Roadmap and Next Steps