Analysis done · scanned all of 0:00–6:02 at 0.1s intervals

Building a Game Village with Vibe Coding (sample video)

Sample channel · Landscape 1920×1080 · 24fps
6:02Video length
32 scenesavg 11.3s
31 hard cuts0 transition effects
0%Live action

Scene timeline

Code motion Source image Source video
0:001:002:003:004:005:006:02
Live action shot with people or a camera: none (0%)

Auto-detection (live_action_check.py) flagged 11 segments (13–17s, 20–24s, 174–176s, 210–232s, 306–311s, 311–315s, 317–329s, 348–350s, 352–354s, 356–359s, 360–362s) as “live-action video”, but a check of all 25 contact sheets at 0.5s intervals showed every one was a 3D render or game screen recording. The whole frame keeps moving, so it was detected like camera noise. Live-action photo candidates: 0.

“Source videos” that play the live-action role Click to see that scene's prompt

S01 Result video (game engine view) · 6.1s
S03 Aerial render video · 10.6s
S19 Alley walk · 13.6s
S29 Character gameplay · 8.5s

Usage rules (measured)

ItemValue
Share Source video 62.7% Source image 21.1% Code only 16.2%
PlacementThe first 23.5s and the last 81s are all result video. The middle alternates with diagrams and images
LengthEach video shot runs 6.1–14.8s with no edits inside the shot (exception: five 0.4s cuts in the first 2s of S30)
TransitionsHard cuts in and out
FramingEye-level push-in, aerial push-in, turntable on a solid backdrop, slow close-up move, third-person gameplay
Overlays1 title tag + one subtitle line (+ 3 numbered cards or a before/after wipe line)
This video has no live-action footage, so you don't need to decide “what to do about live-action scenes” before writing the script. For source video, prepare your own screen recordings or renders.