What do you do as a programmer to make a game "feel" good to play?

What the interviewer wants to hear

• Responsive controls with low input latency
• Feedback: screen shake, hit pause, particles, sound, animation
• Forgiving mechanics like coyote time and input buffering
• Smooth camera and easing instead of linear motion
• Iterate with playtests and expose values for tuning

Model answer

Game feel starts with responsiveness: input should affect the character on the very next frame, with quick acceleration and clear animations. Then I add feedback for every important action, such as a short hit pause, screen shake, particles, sound and a flash on the enemy, so hits feel heavy. I also add small forgiving rules players do not notice, like coyote time, where you can still jump a few frames after leaving a ledge, and input buffering, where a jump pressed just before landing still counts. Cameras use smoothing and easing curves instead of hard linear moves. Finally, I expose all these values to designers in data assets, because the right numbers only come from playtesting and tweaking many times.

More easy Game Developer questions

• What is a game loop, and why is delta time important?
• In Unity, what is the difference between Awake, Start, Update, FixedUpdate and LateUpdate?
• How do you use vectors, dot product and cross product in game development?
• How does collision detection work in a game engine, and what is the difference between a collider and a trigger?
• Tell me about a game or game feature you built. What was the hardest problem and how did you solve it?
• Why do game engines like Unity and Unreal favour components over deep inheritance trees for game objects?
• How would you set up version control for a small game team with programmers and artists?
• What are coroutines in Unity, and when would you use them instead of Update or async/await?
• How do you use prefabs, nested prefabs and prefab variants to keep a Unity project organised?