Using Plugins to Share Code Among Several UE4 Projects
summary
Cyanide packages shared game code and assets into a single CyaTools plugin that holds both runtime and editor modules so multiple UE4 projects reuse the same systems instead of copy‑pasting ShooterGame. The plugin supplies a Mission Flow System (level‑placed nodes, markers, debug commands), a Dialogue System (JSON import, lip sync, callbacks), a Blueprint‑driven save/load, static delegate interfaces for loose coupling, a body‑part mesh merger, 3D navigation aids and auto NavLink generation, and a custom game template for quick prototypes.
AI-written summary · about
chapters (13)
- 0:00Introduction to Cyanide
- 1:09Game production pipeline
- 3:08Improving the old workflow
- 4:40Introduction to plugins
- 7:17Creating the cyanide plugin
- 9:24Plugin features and template
- 12:18Mission and dialogue tools
- 14:54Shared components and features
- 17:10Technical architecture
- 19:06Mission flow deep dive
- 20:52Workflow demonstration
- 25:12Persistence and styling
- 26:38Future developments
related talks
59mA Study of Plugin Architectures for Supporting Extensible Software
54mOptimizing Game Development Workflows with Visual Studio and AI
32mMaking Plugins for Game Engines as a Business
46mUnity Tech for Indies
58mSomething Blue
55mSo You're Trying to Support a Medium Sized Studio....
54mHow to Apply the Software Engineering Process to the Gamedev Process
40mWhat Tools Should Game Developers Have at Hand at all Times?