In this episode, we're diving into the engine of our Deckart project. Today isn't just a devlog, but a comprehensive technical analysis of how to stop spawning entities and start building systems.
The main topic is CMS (Content Management System). I searched for clear guides on YouTube, but they all only discussed formats (JSON vs. SO), forgetting the idea itself. We'll explore:
— Where should the "truth" about content actually live?
— How to split data into Domain and Visual so that battle logic doesn't care about sounds and sprites.
— Mappers and Providers: how to replace Scriptable Objects with Google Sheets overnight without breaking anything.
And, of course, a live demonstration of how setting up starting decks turned into editing configs without a single line of code.
Inside the video:
00:00 — Intro
00:51 — The Idea of a CMS: WHERE and HOW data lives
03:20 — Breaking Down a CMS
11:36 — Refactoring: Breaking Down Architecture into Layers
14:05 — Join us on Telegram
14:35 — CMS in Code
16:52 — CMS in the Game
18:30 — Starter Decks Demo
19:50 — Wrapping Up
🔥 All the development highlights, diagrams from the video, and daily posts about architecture are on my Telegram:
👉 @DevChefGames
Project Stack:
Unity 6 / C#
VContainer (DI)
Assembly Definitions (Asmdef)
Clean Architecture
#Unity #Gamedev #Architecture #Csharp #IndieDev #CMS #CleanArchitecture #Deckart #GameDevelopment #Programming