Uploaded May 2026 | Updated September 2026, 2 weeks ago
In Kingdom Come: Deliverance II, quests aren’t isolated scripts—they’re a tightly connected web of story, state, dialogue, and world logic. Making that work at the scale of a 250‑person, six‑year production required tooling designed specifically for narrative complexity.
Warhorse Studios Lead DevOps Programmer, Petr Nohejl breaks down Scout, Warhorse’s proprietary quest system. Originally built as a dialogue editor, Scout evolved into the central system driving quests, random encounters, NPC behavior, and narrative state across the entire game.
Rather than hiding complexity, Scout makes it visible. Petr explains how designers navigate a bird’s‑eye view of quest dependencies, how validation happens long before QA ever sees a build, and why Perforce P4 isn’t just used for version control—but is embedded directly into the workflow.
In this episode:
How Scout grew from a dialogue tool into the core quest and dialogue system for KCD II
Why Warhorse built a custom quest system and how it unlocked access for sound, localization, and narrative teams
The “switchboard” view that exposes quest dependencies across the entire game world
How P4 server‑side triggers validate quest logic before changes hit the build pipeline
Why Warhorse runs real in‑game scenarios 24/7 to catch issues at scale
Lessons carried forward from Kingdom Come: Deliverance I, including the origin of the “I feel quite hungry” meme
Easter eggs, side projects, and the human craft behind a large RPG production
Speakers:
Jase Lindgren, Principal User Advocate, Perforce
Petr Nohejl, Lead DevOps Programmer, Warhorse Studios
Find Us Online:
Perforce.com
perforce.com/podcasts/p4/in-development
linkedin.com/company/perforce
Timestamps:
[00:00:00] Cold Open
[00:02:10] Welcome & Kingdom Come Origins
[00:04:54] Scaling Development at Warhorse
[00:13:42] Quest Assets & Workflow Rules
[00:16:47] Scout Tool Deep Dive
[00:28:45] Validation, Automation & Testing
[00:35:36] Open World Challenges
[00:40:27] Quest Design Examples
[00:47:32] Humor, Memes & Easter Eggs
[00:54:43] History, Career & The Future
In Kingdom Come: Deliverance II, quests aren’t isolated scripts—they’re a tightly connected web of story, state, dialogue, and world logic. Making that work at the scale of a 250‑person, six‑year production required tooling designed specifically for narrative complexity.
Warhorse Studios Lead DevOps Programmer, Petr Nohejl breaks down Scout, Warhorse’s proprietary quest system. Originally built as a dialogue editor, Scout evolved into the central system driving quests, random encounters, NPC behavior, and narrative state across the entire game.
Rather than hiding complexity, Scout makes it visible. Petr explains how designers navigate a bird’s‑eye view of quest dependencies, how validation happens long before QA ever sees a build, and why Perforce P4 isn’t just used for version control—but is embedded directly into the workflow.
In this episode:
How Scout grew from a dialogue tool into the core quest and dialogue system for KCD II
Why Warhorse built a custom quest system and how it unlocked access for sound, localization, and narrative teams
The “switchboard” view that exposes quest dependencies across the entire game world
How P4 server‑side triggers validate quest logic before changes hit the build pipeline
Why Warhorse runs real in‑game scenarios 24/7 to catch issues at scale
Lessons carried forward from Kingdom Come: Deliverance I, including the origin of the “I feel quite hungry” meme
Easter eggs, side projects, and the human craft behind a large RPG production
Speakers:
Jase Lindgren, Principal User Advocate, Perforce
Petr Nohejl, Lead DevOps Programmer, Warhorse Studios
Find Us Online:
Perforce.com
perforce.com/podcasts/p4/in-development
linkedin.com/company/perforce
Timestamps:
[00:00:00] Cold Open
[00:02:10] Welcome & Kingdom Come Origins
[00:04:54] Scaling Development at Warhorse
[00:13:42] Quest Assets & Workflow Rules
[00:16:47] Scout Tool Deep Dive
[00:28:45] Validation, Automation & Testing
[00:35:36] Open World Challenges
[00:40:27] Quest Design Examples
[00:47:32] Humor, Memes & Easter Eggs
[00:54:43] History, Career & The Future
![Eliminating Development Bottlenecks with Fast Data Delivery from Perforce Delphix [Tutorial]](https://i.ytimg.com/vi/oHajDyszReE/mqdefault.jpg "Eliminating Development Bottlenecks with Fast Data Delivery from Perforce Delphix [Tutorial]
Are slow, manual data delivery processes hindering your enterprises innovation? This demonstration shows how Perforce Delphix eliminates critical development bottlenecks with fast, automated, and secure data delivery. See how you can achieve 100x faster provisioning, empower your developers with self-service data control, and dramatically improve storage efficiency.
In this video, Perforce Solutions Engineer Ajay Thotangare walks you through the Delphix platform, contrasting the slow, multi-step legacy approach with the streamlined Delphix way. Discover how our platform enables your teams to provision and refresh full, production-quality data environments in minutes, not weeks. We will demonstrate how our automated provisioning, seamless REST API integration with CI/CD pipelines, and one-step refresh capabilities transform your data operations. Stop waiting for data and start accelerating your release cycles.
Learn more about accelerating your time-to-market and transforming your data strategy.
Chapters:
0:00 - Introduction: The Challenge of Slow Data Delivery
0:23 - The Legacy Way vs. The Delphix Way
1:54 - Delphix Platform Demonstration
2:45 - Automated, Self-Service Provisioning in Minutes
3:39 - Refreshing a Data Environment
4:27 - Business Impact with Delphix
5:06 - Deliver Data at the Speed of Innovation
Ready to learn more?
Read our recent blog on overcoming DevOps bottlenecks: https://ter.li/t0p7ck
Explore Delphix products for faster data delivery: https://ter.li/669mrp
Request your data delivery demo of Delphix: https://ter.li/iivrb6")
