Seedance Game UI Livestream

Gameplay capture with HUD and stream overlay · 游戏实机录屏与直播叠层

The screen itself is the shot: a fake gameplay capture, livestream or desktop recording. It holds up when the overlay layer is pinned to fixed positions and its numbers and banners change in step with the action.

This Skill carries one prompt structure distilled from 15 human-verified Seedance cases on goodcase.ai. It is a sibling of seedance-prompt-library (all templates in one Skill); install this one when you only want this kind of clip. Do not invent structure from general video-generation knowledge: follow the structure below and ground the draft in one anchor case from references/cases.md.

Use when

• GTA-style mission clips, streamer facecam plus game footage, and interactive desktop or UI recordings where the HUD has to read as a real interface.
• 中文：GTA 风格的任务片段、主播小窗加游戏画面、互动桌面或界面录屏这类片子，HUD 要看起来像真的界面。

Workflow

1. Collect inputs. Ask only for what is missing: subject or product, setting, duration, aspect ratio, whether reference images / audio exist, and which language the final prompt should be in.
2. Pick one anchor case. Read references/cases.md, choose the case closest to the request, and name it in the reply. One anchor, never an average of several.
3. Fill the structure block by block. Every block below must be present in the final prompt; an empty block is where prompts go vague.
   1. Format header: duration, aspect ratio, how the take is cut, and a plain statement that this is game capture
   2. Character lock: Image1 for face and identity only, outfit written out in text
   3. Screen layer spec: where each HUD element, facecam, chat or subtitle sits, and what language it uses, fixed throughout
   4. Camera rig: third-person follow distance and FOV, or one locked camera for desktop recordings
   5. Timeline segments: each one carries the action, the HUD state change and any spoken line
   6. Audio: engine, footsteps, keyboard and mouse, ambience, voice language
   7. Strict rules tail: exact character counts, no extra cuts, HUD stays put, how the clip may and may not end
4. Apply the guidance and check the pitfalls (next two sections) before returning anything.
5. Return the finished prompt as one copy-pasteable block, the anchor case link, and a three-line checklist of what to verify in the generated video.

Guidance (from the cases)

• Pin every overlay to a named screen position before the timeline starts. GTA 6 Simulation opens with Fixed full-screen game HUD throughout and puts the streamer in a bottom-right square pink-blue neon facecam; the snow-station trailer assigns one element to each corner, stamina bars top-left, objective banner top-center, date top-right, minimap bottom-left, button prompts bottom-right.
• Treat the HUD as a scoreboard that changes with each beat. GTA 6 Simulation tracks ammo from 24/120 to 14/120 and wanted level from two stars to three; the diamond escape gives every segment its own HUD block, going from MISSION: STEAL VIP NECKLACE to TARGET ACQUIRED to ESCAPE SUCCESSFUL.
• Say outright that it is gameplay and write the camera like a game rig. The Rio chase asks for genuine gameplay, not a cinematic film; the diamond escape writes Clearly a GAME, not anime or cartoon and puts the camera 1.5m behind NAGI, slightly camera-right with FOV breathing between 30 and 60 degrees.
• Count the cast and make each extra person look different. GTA 6 Simulation asks for exactly two dark-red-jacket gang enemies and no extra armed characters; the five o'clock office case gives four coworkers different ages, heights and hair, and states that the boss is the only bald character.
• Split languages by layer and spell out how on-screen text appears. The diamond escape keeps All HUD text English, dialogue in Japanese; the desktop wallpaper case puts subtitles at the left middle of the frame and types them in at about 0.08 to 0.12 seconds per character, with a waveform under them.