@rechnight
Unity, GameDev, C#, SoftwareArchitecture, DesignPatterns
Oct 16, 2025 · 7 min read · In this final part, we extend our framework to support multi-scene Unity projects, ensuring that Models, Systems, Utilities, and Event subscriptions persist or unload correctly across scene transitions. We also introduce Unregister methods for Models...
Join discussion
Oct 15, 2025 · 4 min read · In Part 4, we implemented a Scoped Event Bus and type-safe events. Now, before tackling multi-scene architecture, we add Utilities — reusable services that don’t fit into Models, Systems, or Controllers but need to be accessible anywhere in the archi...
Join discussion
Oct 14, 2025 · 6 min read · In Part 3, we introduced IOC and Dependency Injection to manage Systems, Models, and Utilities. Back then, our Architecture class already supported event communication using a simple structure like this: private readonly Dictionary<Type, List<object>...
Join discussion
Oct 13, 2025 · 7 min read · In Part 2, we established the core layers — Model, System, Controller — and their strict communication rules. Everything flowed predictably: Controllers → Commands → Models/Systems → Events → Systems/Controllers Now we enhance this framework with Inv...
Join discussion
Oct 11, 2025 · 8 min read · In Part 1 we built the foundation: the folder layout, the core interfaces (IModel, ISystem, IController, ICommand, IEvent), the Architecture singleton, and a working demo. Now it’s time to step back and see how the pieces actually relate — how data f...
Join discussion