Godot FPS AI Voices and AI Video Workflow: Where ElevenLabs and Kling Clips End and Gameplay Begins

A Godot FPS AI voices and AI video workflow splits a game into two kinds of content. One kind can be generated ahead of time: voice lines from ElevenLabs, and video clips from Kling or Higgsfield for intros, cutscenes and trailers. The other kind has to run in the engine: movement, shooting, enemy behaviour and level geometry, all built and tested in Godot. A recent community post puts this split in front of readers, and this specimen uses it to explain where the line falls.

What did the maker share?

The project comes from u/Aware_Bell1295, who posted it to r/aigamedev under the title "Guys, I've been cooking something...". The post shows a first-person shooter made in Godot. It names three AI tools: ElevenLabs for voice, and Higgsfield and Kling for video.

This article doesn't list scene-by-scene details or say how much of the game is playable. Those specifics belong to the maker, and the thread is the place to read them. As you go through the post and its comments, look for three answers:

• Which scenes use generated video, and which are rendered live in Godot.
• Which characters or lines use ElevenLabs voices.
• Whether the footage shows gameplay capture, generated clips, or a mix of both.

The maker's footage stays on Reddit. Follow the link above to watch it in context and to credit the maker directly.

Where do AI clips end and gameplay begin?

A project like this has three layers. Keeping them apart makes it easier to judge what the AI tools contributed.

The key point here is analysis, not a sourced claim. A video clip from Kling or Higgsfield is a fixed sequence of frames. It can't react when the player turns, fires or takes cover. That makes generated video a good fit for moments where the player watches, and a poor fit for anything the player controls.

Voice works differently. An ElevenLabs line is also pre-generated, but Godot decides when to play it. A bark like "Reloading!" can fire whenever an enemy's script reaches that state, so voice lines sit closer to gameplay than video clips do. The design and timing still live in the engine.

For readers judging the project, the main open question is how much of the video shown is real Godot gameplay. A trailer full of generated shots can look further along than the playable build is. Check the thread before drawing conclusions about the game's progress.

How do you get generated video into Godot?

According to the Godot documentation page Playing videos, the VideoStreamPlayer node handles video playback. The same page says the only format supported in core is Ogg Theora, with optional Ogg Vorbis audio.

Video generators usually export MP4, so their clips need converting before Godot can use them. A basic workflow:

1. Export the clip from Kling or Higgsfield at the resolution you need.
2. Convert it to Ogg Theora (.ogv). A typical FFmpeg command looks like this:

ffmpeg -i intro_cutscene.mp4 -c:v libtheora -q:v 6 -c:a libvorbis -q:a 6 intro_cutscene.ogv

3. Put the .ogv file in your project folder so Godot imports it.
4. Add a VideoStreamPlayer node to a cutscene scene and assign the file as its stream.
5. Start playback from script, and connect the node's finished signal to load the gameplay scene when the clip ends.

The Godot docs page covers encoding guidance. Check its recommended quality settings before you settle on the flags above.

One practical result: Theora files can get large, and every clip adds to the exported game's size. In general, a few short generated clips cost less in build size than long generated cutscenes. Scenes staged in-engine with your own models and cameras add almost nothing to download size. They also match the game's art by default.

If you also plan to turn generated clips into 2D animation frames, the site's guide to AI video to 2D sprite animation covers problems that come up between the clip and the sprite sheet.

What should you check before using ElevenLabs voice lines?

ElevenLabs publishes its plans on its pricing page. Before you ship a game with its voices, read that page and the linked terms for three things:

• Commercial use by plan. Confirm that the tier you're on allows voices in a game you sell. Don't assume the free tier covers it.
• Credit limits. Check how the plan counts usage and how many credits a month you get. A shooter can have hundreds of short lines, and regenerating them to get the delivery right uses credits quickly.
• Voice rights. If you use a library voice or a cloned voice, check what the terms say about the rights to that voice and where its output can be used.

A simple way to limit spend is to lock the script before generating. Write every bark and dialogue line in a spreadsheet, settle on a voice for each character, and generate in batches rather than line by line.

Disclosure matters too. Valve asks developers to describe AI-generated content when they submit a game to Steam. The rules have changed since they were introduced, so read the current Steamworks wording before you write your store page. Saying clearly that voices and cutscenes were generated is also simply honest with players.

For a different use of AI voice in games, the specimen on an AI horror game where the monster clones voices shows voice used as a mechanic rather than as recorded dialogue.

What do the video clips cost, according to a vendor comparison?

There's no neutral, game-specific price list for generated cutscenes. One available set of figures comes from a Higgsfield blog post comparing AI avatar generators. According to that post:

• A 10-second 1080p clip costs about $1.00 on Higgsfield's Starter plan ($9 a month, 20 credits).
• Kling comes to about $0.91 per clip on an $8.80-a-month plan (68 credits).
• ElevenLabs avatar clips come to about $2.88 each. The post says the video layer runs on an external engine.

Read these numbers with care. Higgsfield competes with the tools it ranks, so the comparison isn't independent. The figures are for talking-avatar clips, not game cutscenes, which may need several attempts per shot to get consistent characters and camera moves. Prices and credit plans for all three services change often. Check each vendor's current pricing page before you budget.

In practice, a cutscene you keep is often the best of several generations, not the first. Plan for that when you estimate cost.

Verdict: who does this workflow suit?

Based on the tools involved and Godot's documented video support, this workflow suits solo developers who want voiced characters, a polished intro and trailer footage without hiring voice actors or a cinematics team. It works best when the generated material is clearly kept to non-interactive moments.

It doesn't replace gameplay work. Gunfeel, enemy behaviour, level flow and performance still have to be built and tested in Godot. Coding agents can help with that side. The site's guide to the godot-ai MCP server covers letting an agent work in a Godot project.

The limits to plan for:

• Format conversion. Every clip has to become Ogg Theora, and large files increase build size.
• Credit costs. Both voice and video spending grow with every retry.
• Style mismatch. Generated cutscenes can look different from in-engine art, and the jump between them can be jarring.
• Licensing and disclosure. Commercial-use terms vary by plan, and Steam asks for AI disclosure.

For related projects, see how AI agents built a Godot point-and-click adventure, and how one developer took concept art to a playable 3D game. More community builds are in Specimens, and Godot coverage is collected under the Godot tag.