🎮 Learning Game Development – Day 8

Nothing happened when I pressed the key. That’s when I realized something important. Interaction doesn’t work without events.

Blueprint Events & Player Interaction

This post is part of my daily learning journey in game design and game development. I’m sharing what I learn each day — the basics, the confusion, and the real progress.

🧪 What I Tried / Learned Today

On Day 8, I learned about Blueprint events and player interaction.

Until now, I was creating Blueprints, adding components, and setting up logic — but nothing actually responded in-game.

That’s when I understood something important: logic alone doesn’t do anything unless an event triggers it. I learned that Blueprint events are basically triggers — they decide when something should happen.

Some key events I learned today:

• Event Begin Play – runs when the game starts.
• Tick Event – runs every frame.
• On Component Begin Overlap – runs when something enters a collision.
• Input Events (Key Press) – runs when the player presses a key.

This made one thing clear:
Logic needs an event to start.

😕 What Confused Me

At first, I pressed the interaction key…and nothing happened 😅

I thought my logic was wrong.
But the real problem was simpler. The Blueprint was not receiving player input. Everything looked correct, but without input enabled, the key press event never fired. That small mistake completely blocked the interaction.

🧠 How I Understood or Fixed It

I learned that proper interaction needs three things working together:

• Collision / Trigger - A Box Collision to detect the player.
• Overlap Event - Confirms the player is close enough.
• Input Event - Pressing a key to trigger the action.

Using my door Blueprint from Day 7:

1. The Box Collision detects the player.
2. The Overlap Event confirms proximity.
3. The Input Event triggers the door logic.

Only when all three worked together did the interaction finally make sense. That’s when it clicked.

🎯 One Lesson for Beginners

• Events control when logic runs.
• Interaction needs collision + input + logic.
• One missing connection can break everything.
• Debugging is part of learning.

Day 8 was confusing — but very satisfying once it worked.

Slow progress — but I’m building a strong foundation.

If you’re also learning game development, feel free to follow along.
See you on Day 9 🎮🚀