Game music is heard hundreds of times, so it has to survive repetition. These blueprints favour texture over hooks, keep the ending clean enough to loop, and separate the exploration mood from the combat mood instead of trying to do both at once.
Built to be heard on repeat: a bright lead over a driving pulse, with the breakdown giving the ear somewhere to rest before the loop comes round again.
Style
synthwave, upbeat, around 128 BPM, synthesizers, electronic drums and bass guitar, analog warmth, nostalgic and euphoric, bright square-wave lead, punchy gated drums
Lyrics
[Intro: stripped back]
[Build: building energy]
[Drop: high energy]
[Breakdown: stripped back]
[Outro: fade out]
[End]
The arc is written into the arrangement: a stripped intro, an explicit build, then the drop. That structure is what produces "epic", not the word itself.
Style
cinematic score with orchestral influences, mid-tempo, strings, brass section and percussion, spacious production, triumphant and dark, low string ostinato under rising brass
Lyrics
[Intro: stripped back]
[Build: building energy]
[Drop: high energy]
[Outro: fade out]
[End]
Tension without a payoff, on purpose — there is no drop section, so the cue can sit under a scene indefinitely. Percussion is excluded so nothing implies a beat the picture has to match.
Style
cinematic score, slow tempo, strings and synth pads, minimal production, dark and mysterious, sustained low strings, slow unmetered swells
Ask for a fade-out outro and keep an End tag so the model does not trail off unpredictably. You will still trim the file, but a defined ending gives you a clean cut point.
Should combat and exploration share one prompt?
No. Build them as two versions of one project so the instrument palette stays consistent while the energy changes. That is exactly what version history is for.