Night Watch! Part 3 — Polish Your Horror Game in Godot

🐰

You need Parts 1 & 2 first! This workshop polishes the game you built across Parts 1 and 2. Open your Night Watch Godot project and make sure Part 2 is complete before starting.

← Go to Part 2

⭐ 0 XP

Level 1 🔥 0

✨ Polish Progress 0 / 10 steps

★

🌟

Start here

Welcome to Polish Night!

Let's turn good into GREAT...

Current

🎯

Goal

Understand what polish means and open your Night Watch project ready to transform it!

🧒 For the Child

Your game already works brilliantly you've got animatronics, a power meter, multiple nights, and a main menu. But right now the cameras swap instantly, the lights never flicker, and the jump scare just... appears. Polish fixes all of that! We're going to add all the tiny details that make a game feel like a REAL published horror game. Get ready this session is going to be so satisfying!

👨‍👩‍👧 For the Grown-Up

Polish is often 20% of development time but responsible for 80% of perceived quality. This session introduces AnimationPlayer for timed effects, AudioStreamPlayer with generated SFX, modulate-based colour animations, and Sprite2D to replace placeholder geometry. Crucially, we introduce none of these via heavy abstraction each one is added in the simplest possible way, directly to existing nodes, so the child can see and understand every change.

💡

The golden rule of polish: do it LAST. Polishing an unfinished game is a trap you end up perfecting things that get cut later. You built your whole game first. NOW we polish. That's the professional order of operations!

What to do:

1Open Godot 4 and load your Night Watch project.
2Press F5 to confirm everything from Parts 1 & 2 still works correctly.
3Keep the SFX Studio open in a browser tab you'll need it in Step 5: sfx-generator.html
4Keep Pixel Studio open in another tab for Step 4: pixel-studio.html
5Let's go!

🕹️

Try it! Open your Night Watch project in Godot 4. Press F5 and play for 30 seconds. Notice everything that feels a bit "flat" camera swaps, door clicks, the jump scare. By the end of this workshop all of those will feel amazing.

🧠Knowledge Check+15 XP

Why should you polish your game LAST instead of as you build it?

ABecause polish is the easiest part

BBecause Godot requires you to finish gameplay first

CBecause you might end up perfecting things that get cut later

DBecause polish doesn't matter

⚡Quick True or False+15 XP

Camera static is a visual effect that makes camera switching feel more realistic.

Polish changes the core gameplay mechanics of your game.

Screen shake makes jump scares feel more impactful.

📷

Step 1

Camera Static Flash!

That satisfying TV-flicker when you switch views...

Locked

🎯

Goal

When the player clicks a camera button, briefly flash a white noisy overlay before showing the new camera just like the real FNAF.

🧒 For the Child

Have you noticed in FNAF that when you switch cameras the screen goes a bit fuzzy for a split second? That's called camera static it looks like old TV interference. It makes the camera switching feel REAL instead of just instantly swapping. It's actually super easy to add we just show a white flash for a tiny moment every time someone presses a camera button!

👨‍👩‍👧 For the Grown-Up

Add a full-screen ColorRect named "CamStatic" to the UI CanvasLayer (or a new CanvasLayer above the cameras), initially invisible, color white with ~0.7 alpha. In show_cam(), before switching the visible panel, make CamStatic visible, await a short timer (0.06s), then hide it and reveal the new camera. The two-frame flash is enough to feel like static without being distracting.

💡

In real FNAF the static is a sprite sheet animation with noise. Our version a quick white flash achieves 90% of the feel with 5% of the effort. This is a great lesson in "fake it 'til you make it" game feel!

What to do:

1In main.tscn, add a new ColorRect inside your UI CanvasLayer. Name it CamStatic.
2Set its anchors to fill the full screen (anchor_right = 1, anchor_bottom = 1). Set color to white with alpha 0.7. Set Visible: off.
3Mark it as a scene-unique node: right-click → "Access as Unique Name" (so you can use %CamStatic in the script).
4Update the show_cam() function in main.gd with the code below.

# Updated show_cam() in main.gd:

func show_cam(index: int):
	# Flash the static overlay first
	%CamStatic.visible = true
	await get_tree().create_timer(0.06).timeout
	%CamStatic.visible = false

	# Now swap to the new camera panel
	for i in cam_panels.size():
		cam_panels[i].visible = (i == index)
	current_cam = index

🕹️

Try it! Click between camera buttons quickly. Does each switch have a brief white flash? It should feel very satisfying. If it's too bright or too long, adjust the color alpha or the timer wait time.

🧠Knowledge Check+15 XP

In the camera static effect, what does await get_tree().create_timer(0.06).timeout do?

ACreates a new camera

BWaits 0.06 seconds before continuing

CDeletes the CamStatic node

DSpeeds up the game

💻Fill in the Code+20 XP

Complete the camera static flash code:

func show_cam(index: int): %.visible = await get_tree().create_timer(.timeout %CamStatic.visible =

💡 Hint: The static overlay is called CamStatic. It shows (true) then hides (false) after a short delay.

💡

Step 2

Flickering Office Lights!

The lights are... unstable. How unsettling.

Locked

🎯

Goal

Add a random flicker to the office lighting so the environment feels alive and nervous-making.

🧒 For the Child

Ever been in a spooky movie where the lights flicker? It's terrifying! We're going to make the office lights randomly flicker just for a tiny moment, then back to normal. Most of the time nothing happens. But every now and then: flicker. It makes the whole game feel SO much creepier!

👨‍👩‍👧 For the Grown-Up

Add a semi-transparent dark ColorRect ("LightFlicker") covering the full office area, initially invisible. Add a Timer node ("FlickerTimer") with wait_time around 0.2s and autostart on. In the timeout callback, use randf() to trigger a flicker ~5% of the time briefly show the overlay for 0.08s then hide it.

💡

Randomness creates tension. A light that flickers on a predictable schedule feels mechanical. A light that flickers RANDOMLY keeps the player's brain in a constant low-level alert state.

What to do:

1In main.tscn, add a ColorRect as a child of your root NightWatch node. Name it LightFlicker.
2Set it to cover the full office area. Set color to near-black, alpha ~0.85. Set Visible: off.
3Add a Timer node to NightWatch. Name it FlickerTimer. Set Wait Time: 0.2, Autostart: on.
4Mark LightFlicker as a scene-unique node.
5Add the code below to main.gd.

# Add to main.gd connect FlickerTimer.timeout in _ready():

func _ready():
	# ... your existing _ready() code ...
	$FlickerTimer.timeout.connect(_on_flicker_timer)

func _on_flicker_timer():
	if not game_active:
		return
	if randf() < 0.05:  # 5% chance each tick
		%LightFlicker.visible = true
		await get_tree().create_timer(0.08).timeout
		%LightFlicker.visible = false

🕹️

Try it! Watch the office for 20-30 seconds. Does the light occasionally dip and return? Adjust the randf() threshold (try 0.03 for less frequent, 0.1 for more) until it feels right.

🧠Knowledge Check+15 XP

Why do we use randf() < 0.05 for the flicker instead of a fixed timer?

ARandom flickering is more unsettling than predictable flickering

BBecause Godot doesn't support fixed timers

CTo make the game run faster

DBecause random numbers are easier to code

📝Fill in the Concept+15 XP

The flicker has a % chance of triggering each tick, making it happen roughly every seconds on average.

📳

Step 3

Screen Shake on the Jump Scare!

The whole world shakes when they get you...

Locked

🎯

Goal

When an animatronic triggers the jump scare, violently shake the camera for a second before the game over screen appears.

🧒 For the Child

Right now the jump scare just pops up BOOM, it's there. Imagine if the whole screen shook like an earthquake at the same time? We're going to make the camera rattle around really fast for about a second, then show the game over screen. People are going to SCREAM.

👨‍👩‍👧 For the Grown-Up

Add a Camera2D node to main.tscn. In _trigger_jumpscare(), animate the camera's offset using a Tween rapidly oscillate between small random offsets (e.g. ±15px) over ~0.8 seconds, then reset to (0,0). The Tween approach needs no AnimationPlayer and is cleanly self-contained.

💡

Camera shake is one of game feel's most powerful tools. It communicates impact at a physical level. Use it sparingly only for the jump scare so it retains its impact.

What to do:

1In main.tscn, add a Camera2D node as a child of your NightWatch root. Name it MainCamera.
2Mark it as scene-unique: right-click → "Access as Unique Name".
3Replace your existing _trigger_jumpscare() function in main.gd with the version below.

# Replace _trigger_jumpscare() in main.gd:

func _trigger_jumpscare():
	var tween = create_tween()
	var shake_duration = 0.8
	var elapsed = 0.0
	while elapsed < shake_duration:
		var offset = Vector2(randf_range(-15, 15), randf_range(-12, 12))
		tween.tween_property(%MainCamera, "offset", offset, 0.04)
		elapsed += 0.04
	tween.tween_property(%MainCamera, "offset", Vector2.ZERO, 0.05)

	%JumpScare.visible = true
	await get_tree().create_timer(1.8).timeout
	_game_over()

🕹️

Try it! Let an animatronic reach an open door. When the jump scare triggers, does the screen shake violently? The shake should be fast and chaotic not smooth and gentle.

🔮Predict What Happens+15 XP

If you changed randf_range(-15, 15) to randf_range(-2, 2), what would happen to the screen shake?

AThe shake would be much more violent

BThe shake would be barely noticeable a tiny wobble

CThe game would crash

DThe shake would last longer

📋Order the Steps+15 XP

Put the screen shake steps in the correct order:

Reset camera offset to Vector2.ZERO

Create a new Tween

Show jump scare overlay

Loop random offsets for 0.8 seconds

🎨

Step 4

Custom Pixel Art Sprites!

Replace those coloured boxes with real art!

Locked

🎯

Goal

Use Pixel Studio to draw your own animatronic sprite and replace the placeholder ColorRect with a Sprite2D.

🧒 For the Child

Those coloured rectangles pretending to be animatronics? It's time to replace them! Open Pixel Studio and draw your own version of Freddy a round brown bear face, glowing eyes, maybe a hat! YOUR art in YOUR game is a thousand times better than a perfect rectangle.

👨‍👩‍👧 For the Grown-Up

Pixel Studio exports PNG files. In Godot, drag the PNG into the FileSystem dock. In freddy.tscn, add a Sprite2D child and assign the texture. Recommended sprite size: 64x64 or 128x128 pixels. This is a great opportunity to explain texture reuse.

💡

Making your own art even simple pixel art is one of the most meaningful milestones in game development. The moment a child sees THEIR drawing moving in THEIR game is genuinely unforgettable.

What to do:

1Open Pixel Studio. Draw a 64x64 animatronic sprite.
2Export it as a PNG (click the download button).
3In Godot, drag the PNG file into the FileSystem dock.
4Open freddy.tscn. Add a Sprite2D and assign your texture.
5Adjust the Sprite2D's Scale and Position.
6Optionally hide or delete the old ColorRect.

🕹️

Try it! Open the game and switch to Camera 1 (Stage). Does Freddy now appear as your pixel art sprite instead of a coloured box? Adjust scale if needed.

🧠Knowledge Check+15 XP

What node type do you use in Godot to display a PNG image in your game?

AColorRect

BLabel

CSprite2D

DAudioStreamPlayer

⚡Quick True or False+15 XP

You can reuse the same texture on multiple Sprite2D nodes at different scales.

Sprite2D's default origin is at the top-left corner.

🎵

Step 5

Real Sound Effects!

Doors creak. Power hums. Freddy lurks.

Locked

🎯

Goal

Use SFX Studio to generate a door creak, a power hum, and a jump scare sting then wire them up in Godot.

🧒 For the Child

A horror game without sound is like a haunted house with the lights on! We're going to add three sounds: a creaking GROAN when you close a door, a low electrical HUM in the background, and a horrible SHRIEK when the jump scare triggers. Make them as spooky as you want!

👨‍👩‍👧 For the Grown-Up

SFX Studio exports WAV files. Add three AudioStreamPlayer nodes: DoorSFX (non-looping), AmbientHum (looping, from _ready), and JumpScareSFX (one-shot). Vary AmbientHum's pitch_scale based on power level to create increasing tension.

💡

Audio is responsible for roughly 50% of emotional impact in games and film. Adding sound to a previously silent game is the single highest-return polish step.

What to do:

1Open SFX Studio. Generate and download three sounds.
2Drag all three WAV files into the Godot FileSystem dock.
3Add three AudioStreamPlayer nodes: DoorSFX, AmbientHum, JumpScareSFX.
4Assign each audio file to its matching node's Stream slot.
5For AmbientHum: tick Autoplay and Loop.
6Add the code below to main.gd.

# Add to main.gd:

func _on_left_door_pressed():
	# ... your existing door code ...
	$DoorSFX.play()

func _on_right_door_pressed():
	# ... your existing door code ...
	$DoorSFX.play()

# Vary hum pitch as power drains:
func _update_power(delta):
	# ... your existing drain code ...
	$AmbientHum.pitch_scale = 1.0 + (1.0 - (power / 100.0)) * 0.4

func _trigger_jumpscare():
	$JumpScareSFX.play()
	$AmbientHum.stop()
	# ... rest of your jumpscare code ...

🕹️

Try it! Press a door button do you hear the creak? Can you hear the ambient hum? Get caught does the jump scare play a sound?

💻Fill in the Code+20 XP

Complete the pitch variation code for the ambient hum:

$AmbientHum. = 1.0 + (1.0 - ( / 100.0)) * 0.4

💡 Hint: We're changing the pitch_scale property. The variable that tracks remaining power is called "power".

🧠Knowledge Check+15 XP

Why do we vary the AmbientHum's pitch_scale as power drains?

ATo make the sound louder

BTo save memory

CBecause Godot requires it

DTo create increasing tension as power runs out

⚡

Step 6

Low-Power Warning!

The red glow of impending doom...

Locked

🎯

Goal

When power drops below 20%, add a pulsing red tint to the screen and a repeating warning beep.

🧒 For the Child

When power goes below 20%, the whole office starts glowing a scary red colour that pulses in and out. AND a warning beep starts playing. So the player has THREE ways to know power is low the number, the red glow, AND the sound. It's the panic button!

👨‍👩‍👧 For the Grown-Up

Add a full-screen ColorRect ("PowerWarning") with red color alpha 0. When power drops below 20, start a looping Tween on the alpha (0 to 0.18). Also start a BeepTimer. Use a bool power_warning_active to avoid re-triggering every frame.

💡

Redundant feedback the same information delivered through multiple channels simultaneously (visuals + audio + number) is a cornerstone of good game UX.

What to do:

1Add a ColorRect named PowerWarning to your UI CanvasLayer. Red color, alpha 0.
2Add a Timer named BeepTimer. Wait Time: 1.5, Autostart: off.
3Create a short beep sound and add an AudioStreamPlayer named WarnBeep.
4Add the code below to main.gd.

# Add to main.gd:

var power_warning_active = false

func _update_power(delta):
	# ... your existing power drain code ...
	if power < 20.0 and not power_warning_active and not power_drained:
		power_warning_active = true
		_start_power_warning()

func _start_power_warning():
	$BeepTimer.start()
	$BeepTimer.timeout.connect(func(): $WarnBeep.play())
	var tween = create_tween().set_loops()
	tween.tween_property(%PowerWarning, "color:a", 0.18, 0.4)
	tween.tween_property(%PowerWarning, "color:a", 0.0,  0.4)

func _power_out():
	# ... your existing power-out code ...
	$BeepTimer.stop()
	%PowerWarning.color.a = 0.0

🕹️

Try it! Let your power drain to below 20%. Does the screen pulse red? Do you hear the warning beep?

🧠Knowledge Check+15 XP

Why do we use a power_warning_active boolean?

ATo make the warning louder

BTo prevent the tween from being created every single frame

CTo change the colour of the warning

DIt's not needed it's just a habit

📝Fill in the Concept+15 XP

The power warning uses channels of feedback simultaneously: the power , the red , and the warning .

🚪

Step 7

Door Slam Animation!

Make those doors THUD shut.

Locked

🎯

Goal

When a door closes, animate the door block sliding in from the side instead of just appearing instantly.

🧒 For the Child

Real doors MOVE! We're going to make the door block slide in from the edge of the screen, like a big heavy door slamming shut. It takes about 0.15 seconds and it makes the door feel SOLID and HEAVY.

👨‍👩‍👧 For the Grown-Up

Use a Tween to animate the door block ColorRect's offset_right (for left door) from 0 to 120 in 0.15s using EASE_OUT. For right door: animate offset_left from 960 to 840. Duration matters: 0.15s feels snappy, 0.3s feels sluggish.

💡

Animation duration matters enormously. 0.15 seconds feels snappy and responsive. 0.5 seconds would feel like the door is made of foam. Always err on the side of faster for UI feedback.

What to do:

1Update the door functions to animate using a Tween instead of toggling visible.
2For the left door: tween offset_right from 0 to 120 (0.15s).
3For the right door: tween offset_left from 960 to 840 (0.15s).
4Set door blocks to visible = true in the scene.

# Updated door functions in main.gd:

func _on_left_door_pressed():
	left_door_closed = not left_door_closed
	var tween = create_tween().set_ease(Tween.EASE_OUT)
	if left_door_closed:
		tween.tween_property(%LeftDoorBlock, "offset_right", 120.0, 0.15)
		%CloseLeftDoorButton.text = "🚪 Open Left Door"
	else:
		tween.tween_property(%LeftDoorBlock, "offset_right", 0.0, 0.15)
		%CloseLeftDoorButton.text = "🚪 Close Left Door"

func _on_right_door_pressed():
	right_door_closed = not right_door_closed
	var tween = create_tween().set_ease(Tween.EASE_OUT)
	if right_door_closed:
		tween.tween_property(%RightDoorBlock, "offset_left", 840.0, 0.15)
		%CloseRightDoorButton.text = "🚪 Open Right Door"
	else:
		tween.tween_property(%RightDoorBlock, "offset_left", 960.0, 0.15)
		%CloseRightDoorButton.text = "🚪 Close Right Door"

🕹️

Try it! Press the left door button. Does the dark panel slide in from the left edge? The motion should feel fast and satisfying.

💻Fill in the Code+20 XP

Complete the door animation tween:

var tween = create_tween().set_ease(Tween.) if left_door_closed: tween.tween_property(%LeftDoorBlock, "", 120.0, )

💡 Hint: We use EASE_OUT for the easing. The property is offset_right. The duration is 0.15 seconds.

🧠Knowledge Check+15 XP

Why do we use position/size animation instead of toggling visible for the door?

AIt looks like a real door sliding shut instead of popping into existence

BToggling visible doesn't work in Godot

CIt uses less memory

DBecause Tween is required for all nodes

💀

Step 8

Animated Death Screen!

Going out with a bang (and a slide-in).

Locked

🎯

Goal

Make the game over screen SLIDE in from below and show which animatronic caught you.

🧒 For the Child

Let's make the game-over screen dramatically slide up from the bottom like a curtain falling. And we'll make it say WHO got you "Freddy got you!" or "Bonnie got you!" A dramatic death screen makes losing feel almost... satisfying?

👨‍👩‍👧 For the Grown-Up

Pass the animatronic name into _game_over(). Add a DeathPanel Control that starts 540px below, then Tween offset_top from 540 to 0 over 0.4 seconds. Named consequences increase emotional investment.

💡

Named consequences increase emotional investment. "Game Over" is generic. "Freddy got you because you forgot to check the right door" is a story.

What to do:

1Update _on_animatronic_at_door() to pass the name to _trigger_jumpscare().
2Add a Control named DeathPanel inside GameOverScreen. Set offset_top to 540.
3Update _game_over() with the slide-in animation below.

# Updated functions in main.gd:

var caught_by = "an animatronic"

func _on_animatronic_at_door(side, who = "an animatronic"):
	var door_closed = left_door_closed if side == "left" else right_door_closed
	if door_closed:
		for node in get_tree().get_nodes_in_group("animatronics"):
			if node.get("room") == (3 if side == "left" else 4):
				node.room = 0
				node._update_display()
	else:
		caught_by = who
		_trigger_jumpscare()

func _game_over():
	game_active = false
	%GoLabel.text = "💀 " + caught_by + " got you!"
	%GameOverScreen.visible = true
	var tween = create_tween().set_ease(Tween.EASE_OUT)
	tween.tween_property(%DeathPanel, "offset_top", 0.0, 0.4)

🕹️

Try it! Get caught on purpose. Does the game over screen slide up from the bottom? Does it say which animatronic caught you?

🔮Predict What Happens+15 XP

If you changed the Tween duration from 0.4 to 3.0 seconds, how would the death screen feel?

AMore dramatic and scary

BThe game would crash

CPainfully slow and awkward it would kill the tension

DNo different at all

📋Order the Steps+15 XP

Put the death screen sequence in order:

Tween DeathPanel offset_top from 540 to 0

Set game_active to false

Update GoLabel text with animatronic name

Player sees the animated slide-in

🌅

Step 9

Win Screen Celebration!

You survived. You DESERVE confetti.

Locked

🎯

Goal

Make the win screen feel triumphant a slide-in panel, the current night number, and a confetti particle burst.

🧒 For the Child

Winning should FEEL amazing! We're going to make the win screen slide down from the TOP (like the sun rising at 6am), show which night you survived, and add a burst of colourful confetti. You built a whole horror game and survived five nights you absolutely deserve confetti!

👨‍👩‍👧 For the Grown-Up

Mirror the death screen: WinPanel starting at offset_top = -540, tween to 0. Add a CPUParticles2D node for confetti (built into Godot, no plugins needed). Set emitting = true in _win().

💡

Victory screens are often the most neglected part of indie games. A well-designed win screen is your last impression on the player. Make it memorable.

What to do:

1Add a Control named WinPanel inside WinScreen. Set offset_top to -540.
2Add a CPUParticles2D node named Confetti. Set Emitting: off, Amount: 80, Lifetime: 3.0.
3Update _win() in main.gd with the code below.

# Updated _win() in main.gd:

func _win():
	game_active = false
	%WinLabel.text = "🌅 6 AM! You survived Night " + str(GameManager.current_night) + "!"
	%WinScreen.visible = true
	%Confetti.emitting = true
	var tween = create_tween().set_ease(Tween.EASE_OUT)
	tween.tween_property(%WinPanel, "offset_top", 0.0, 0.5)

🕹️

Try it! Survive a full night (cheat: temporarily set NIGHT_DURATION = 10.0). Does the win panel slide down from above? Do you see confetti?

🧠Knowledge Check+15 XP

What is CPUParticles2D used for in this step?

APlaying sound effects

BMoving the camera

CCreating a confetti celebration burst

DTracking the player's score

⚡Quick True or False+15 XP

CPUParticles2D is built into Godot no extra plugins needed.

The win screen slides UP from below, the same as the death screen.

Setting emitting = true is what starts the confetti particles.

🏆

Step 10

Final Playtest & Share!

Five nights survived. Legends only.

Locked

🎯

Goal

Do a full playthrough of your polished game, fix anything that feels off, then export it and share it!

🧒 For the Child

This is the most important step: actually PLAY your finished game! Try every camera. Close and open doors. Let power run out. Get caught on purpose. Then hand it to someone who has NEVER played it before. Watch their face. Did they jump? That reaction is YOUR work. You should be so, so proud!

👨‍👩‍👧 For the Grown-Up

Encourage a full playthrough of all 5 nights. Then export: Project → Export, add a Web (HTML5) preset, export. HTML5 exports can be uploaded to itch.io for free. That milestone is enormously motivating.

💡

Every professional game goes through playtesting. Watching someone else play your game reveals things you never noticed. This is not a sign of failure it's the most valuable feedback loop in game development.

What to do:

1Play the full game yourself try Night 1 AND Night 5.
2Check each polish step: camera static, light flicker, screen shake, sounds, power warning, door animation, death screen slide, win confetti.
3Fix anything that feels wrong.
4To export: Project → Export. Add Web (HTML5) preset. Click Export Project.
5Upload to itch.io (free) and share the link!

🕹️

Try it! Hand the game to a parent, sibling, or friend. Tell them nothing except "try to survive until 6am." Watch don't help! Then celebrate.

🧠Final Knowledge Check+15 XP

What is the MOST valuable thing about watching someone else play your game?

AIt proves your game has no bugs

BIt reveals things that confuse fresh players that you never noticed

CIt makes you feel good about yourself

DIt's not valuable it's just for fun

⚡Final True or False+15 XP

You should polish your game AFTER the gameplay is complete, not during.

Godot can export games to HTML5 so anyone can play them in a browser.

Playtesting is only useful if you find bugs.

🎉🏆🎮✨🎊

Night Watch is COMPLETE!

You built a fully polished, five-night horror game from scratch. Camera static, flickering lights, screen shake, custom sprites, sound effects, power warnings, animated screens, and confetti. You're a real game developer now!

Total XP

Level

Best Streak

Accuracy

🎮 See All Episodes → ⭐ View My Progress & Certificates

This workshop was free and took many hours to build. If it helped you learn something new, consider supporting the project.

☕ Support on Ko-fi

🎨 What Is Polish?

Polish is the difference between a game that works and a game that feels amazing. None of these steps change how the game is played they change how it feels to play it. A camera flash when you switch views. A light flicker that makes your hands sweat. A screen shake that makes the jump scare genuinely terrifying. Small details, huge impact.

🧒 For the Child

You've already built something incredible a real horror game with multiple monsters, a power meter, and five nights! But right now the cameras just swap instantly and the jump scare just pops up. In this part we're going to add things like flickering lights, a flash when you switch cameras, and a screen shake during the jump scare. When you're done, it will feel EXACTLY like the real FNAF. People are going to scream playing your game! 😱

👨‍👩‍👧 For the Grown-Up

This episode covers: AnimationPlayer for the screen shake and camera static effects, a Timer-based random light flicker, AudioStreamPlayer with generated SFX for doors, power warnings, and ambient hum, replacing placeholder ColorRect nodes with custom Sprite2D pixel art, a low-power warning pulse using modulate animation, and a polished animated death screen with AnimationPlayer. No new gameplay systems pure feel and presentation.

✨ What We're Adding

Camera static flash when switching views
Flickering office lights
Screen shake on the jump scare
Custom pixel art sprites (using Pixel Studio)
Real sound effects (using SFX Studio)
Low-power warning beep & red pulse
Door slam sound & animation
Animated death screen (slides in from off-screen)
Win screen confetti & celebration
Final playtest & share your game!

Night Watch! Part 3 ✨Polish Night Make It Feel Like a Real Game!

🧒 For the Child

👨‍👩‍👧 For the Grown-Up

What to do:

🧒 For the Child

👨‍👩‍👧 For the Grown-Up

What to do:

🧒 For the Child

👨‍👩‍👧 For the Grown-Up

What to do:

🧒 For the Child

👨‍👩‍👧 For the Grown-Up

What to do:

🧒 For the Child

👨‍👩‍👧 For the Grown-Up

What to do:

🧒 For the Child

👨‍👩‍👧 For the Grown-Up

What to do:

🧒 For the Child

👨‍👩‍👧 For the Grown-Up

What to do:

🧒 For the Child

👨‍👩‍👧 For the Grown-Up

What to do:

🧒 For the Child

👨‍👩‍👧 For the Grown-Up

What to do:

🧒 For the Child

👨‍👩‍👧 For the Grown-Up

What to do:

🧒 For the Child

👨‍👩‍👧 For the Grown-Up

What to do:

🎨 What Is Polish?

🧒 For the Child

👨‍👩‍👧 For the Grown-Up

✨ What We're Adding

Make It Yours