🎮 Learning Game Development – Day 9

Source: Dev.to

Debugging Blueprints & Using Print String

🧪 What I Tried / Learned Today

• Learned the importance of debugging Blueprints.
• After inconsistent door behavior on Day 8, I discovered I had no visibility into what was actually running inside my Blueprint.
• Introduced the Print String node as a simple but powerful debugging tool.

Print String helps you:

• Check if an event is firing
• Confirm if an overlap is working
• See if an input key is detected

😕 What Confused Me

• My initial thoughts when something didn’t work were:
  • “My logic is wrong.”
  • “My Blueprint is broken.”
• The real issue was not the logic itself but the lack of insight into where the problem occurred.
• Without debugging, I was merely guessing, which wastes time.

🧠 How I Understood or Fixed It

• Placed Print String nodes at key points in the Blueprint:
  • After Begin Overlap
  • After Input Key Press
  • Just before the door logic
• Observed the on‑screen messages to trace execution flow.
• Discovered scenarios such as:
  • Overlap worked, but input didn’t.
  • Input worked, but the door logic never ran.
• Realized that debugging is an essential part of development, not an optional extra.

🎯 One Lesson for Beginners

• If nothing happens, stay calm.
• Use Print String (or equivalent) to verify each step of your logic.
• Identify exactly where the flow breaks.
• Fix one small issue at a time.

Day 9 was less about adding features and more about understanding what’s actually happening. Slow progress, but it builds a strong foundation. If you’re also learning game development, feel free to follow along.

---

Next entry: Day 10 🎮🚀