Gameplay Videos Generator · skill pública Open Skill
Gameplay Videos Generator
Gameplay Videos Generator é uma Open Skill pública no Digen. Abra para ver o que este fluxo cria.
Anime
4 0 5
https://d7qlwi7tl2u27.cloudfront.net/skill-covers/prod/4005040/2026-09-24/chaw42eg.jpg
# Gameplay Footage Generator
Turns a game concept into smooth, consistent, high-fidelity gameplay-style clips. Output is AI-generated concept footage, not a capture of a real game.
## Defaults (use unless the user says otherwise)
| Setting | Default | Notes |
|---|---|---|
| Orientation | `portrait` (9:16) | `landscape` (16:9) for trailers/YouTube; `square` (1:1) if the tool supports it |
| Resolution | `720P` | `1080P` when the user asks for higher fidelity or final output |
| Duration | 5-8s per clip | Shorter clips hold consistency better |
| Camera | First-person for FPS/racing cockpit; third-person for action/story | |
| Clips | 1 | Move to the multi-clip workflow when the user wants a sequence, trailer, or "a few shots" |
## Workflow
1. **Infer, don't interrogate.** Pull genre, setting, camera, mood, and HUD from the request and fill gaps with defaults. Ask at most **one** question, and only if the scenario is so vague that two very different clips are plausible. State your assumptions in one line when you generate.
2. **Pick the mode:**
- No image provided -> `model='t2v'`, `input_urls=[]`
- One image to animate as the opening frame -> `model='i2v'`, image in `input_urls`
- One or more images for character/environment consistency -> `model='ref2v'`, asset IDs in `input_urls` (at least 1)
- User wants a specific character/environment but supplied no image -> create it first with `generate_image` (`model='t2i'`, `orientation` matching the video, `entity_type='characters'` or `'locations'`), then use it as a `ref2v` reference.
3. **Write the prompt** (see Prompt guide below).
4. **Call `generate_video`** with: `orientation`, `resolution`, `duration`, `name` (short shot title, e.g. "FPS corridor firefight"), `entity_type='gameplay_videos'`, and the English `prompt`.
5. **Report naturally.** Describe what was made and offer one or two concrete tweaks. Never paste raw URLs. Report failures honestly; never invent URLs or claim a clip exists when it does not.
## Prompt guide
Write one dense paragraph in this order:
1. **Genre + camera:** "First-person tactical shooter, smooth handheld tracking shot at eye level."
2. **Subject + single action:** one clear action per clip, using concrete verbs (sprints, vaults, drifts, reloads). Multiple beats in one clip cause drift and artifacts.
3. **Environment:** location, materials, scale, depth cues (foreground/midground/background).
4. **Lighting + atmosphere:** time of day, light sources, weather, particles (dust, smoke, rain).
5. **HUD:** describe by position and shape, e.g. "minimal HUD: ammo counter bottom-right, compass strip top-center, small crosshair." Avoid requiring legible text or exact numbers; generators render text poorly. For 9:16, keep HUD away from the outer edges and bottom ~15% where platform UI overlays sit.
6. **Motion + physics:** weight, recoil, camera shake, suspension, cloth, debris, muzzle flash, motion blur.
7. **Fidelity:** "high visual fidelity, consistent character and environment, smooth natural motion, cinematic game-engine look."
Rules of thumb:
- Phrase constraints positively ("steady camera") rather than as long negative lists.
- Prefer original or generic game worlds. Don't recreate trademarked characters, logos, or exact HUDs of specific commercial games; describe the genre and style instead.
- No real, identifiable people.
## Multi-clip sequences
1. **Plan a shot list first** (3-5 clips): number each with a title, camera, action, and how it cuts to the next. Vary shot scale (wide establishing -> mid action -> close detail -> payoff).
2. **Lock consistency:** generate one character reference and one location reference with `t2i`, then use `ref2v` for every clip.
3. **Repeat a continuity block verbatim** at the start of each prompt: character appearance, outfit, weapon/vehicle, palette, time of day, HUD layout.
4. **Chain when continuity matters:** use a clean last frame of clip N as the `i2v` start image for clip N+1.
5. **Genera