How to Create Scripting Tools That Designers Love
summary
Studio replaces ad-hoc Blueprint spaghetti with a small set of concrete systems: a designer-facing game event and game event state for one-parameter multicast responses, a Knowledge Base Expression Builder (KBEB) that infers world state from mission progress, and a conditional actor that spawns content only when needed. The result is rollback-safe worlds, much smaller runtime persistence, faster QA (load-by-objective), and designers wiring a switch-to-door-and-explosion sequence in seconds while engineers keep centralized control and debug hooks.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:35Problem Statement
- 2:28Our Starting Point - Mission System
- 4:13Empowering Designers Safely
- 6:15Switch - Door Communication
- 6:50The Communication Problem
- 8:07The Game Event
- 10:48Game Event State
- 18:00Persistence
- 21:00Scripted Sequences
- 25:48Communication - Design Information Delivery System (DIDS)
- 29:55Game Event - Pure Virtual
- 30:54Required Implementation
- 31:27Filter Groups
- 33:04Display Priority
related talks
51mEmpowering Design: The Tools and Pipelines of Unpacking
48mImproving Data Structures for Rapid & Intelligent Gameplay Design.
39mBehind the Game: Strategies for Building the Tech That Powers Today’s Top Titles.
15mMaking artists happy in Unity
19mTechnical indie game developer tips for starting your framework early
57mBulletproof development with design systems
49mEfficient Programmer++: Examples and Anti-Examples
28mManipulating GUI Structures Declaratively