Skip to article Developer portalAdd your game

GAMENIGHT / DOCUMENTATION

Five-second gameplay previews

Every playable GameNight store entry needs an engaging five-second gameplay montage. Its job is to show how much fun the game contains before someone scrolls past. Technical validity alone is not acceptance.

Upload the clip on the developer portal's Store page before publishing. Use MP4 or WebM, up to 32 MiB. The server measures its length (4.9–5.1 seconds to allow frame rounding). Screenshots and YouTube links are optional. Private preview builds and drafts can be saved before the clip is ready.

Plan the five seconds

Before recording, write a short shot list with the action, players, weapon/item, setting or arena, and intended payoff for each cut. Use 4–6 quick cuts, usually about 0.6–1.3 seconds per shot. Aim for four or more clearly different action beats. Cut into action already starting and leave enough time to see its result. Use straight cuts; transitions, logos and menus must not consume the five seconds.

Show as much meaningful variety as remains readable:

Adapt categories to the actual game. A sports game can show tackles, passes, shots, saves and team sizes instead of weapons. Do not invent features to fill a checklist. If a category does not exist, spend its time on another real mechanic. Avoid repeated shots that all communicate the same thing.

Make the action legible

Frame the relevant players and effects large enough to recognize in a store card and on a phone. Mix close action with a useful wider shot; a distant whole-map view with tiny characters is not a substitute for showing gameplay. Keep subjects in frame through the payoff. Remove setup, countdowns, idle traversal, pauses and empty aftermath. Do not simply take the first five seconds of a match or publish one uninterrupted wide shot because it is easy to capture.

Watch the entire montage at its actual five-second speed, at desktop-card and phone sizes. Inspect every cut: the viewer should immediately understand what is new and see the action land. Shorten or replace dull shots, and lengthen confusing ones. Do not accelerate gameplay to force too much into the time budget.

Capture real gameplay

Use the listed release's simulation and renderer. Never use generated gameplay, animated cover art or fabricated effects. Deterministic bots or staged starting positions, legitimate loadouts and real input sequences are useful for getting clear moments. Keep mechanics, damage, physics and effects faithful to the game. Record any staging in the capture notes; do not present it as a live competitive match. Work in a scratch copy without affecting active player sessions.

Retain a reproducible capture harness and edit decision list: source version/commit and package hash, seed, staging, each source in/out frame, shot length, and what each shot demonstrates. Record hashes for the encoded clip and its poster.

Delivery and acceptance

Review gate: Does the clip visibly cover different players, weapons/abilities, settings, items and signature mechanics wherever the game supports them? Are there several quick, readable cuts with satisfying outcomes? Would someone understand why this game is fun without reading its description? If not, revise the edit.

The hosted service's deploy/cloud/previews/README.md contains engine-specific capture commands and publishing steps. Its PREVIEWS.json records shipped clips.