Building a classic adventure game with Blazor
summary
A full adventure engine runs in Blazor WebAssembly using Blazor components plus a tiny in-memory mediator for UI events; graphics come from Phaser JS via optimized JS interop (IJSInProcessRuntime and a Phaser facade), click/hover events call back into C# with DotNetObjectReference, walk paths use a generated visibility graph and QuickGraph Dijkstra for routing, scripts compile with Roslyn after fetching assembly metadata over HTTP, and savegames store diffs to IndexedDB — the demos run end-to-end.
AI-written summary · about
chapters (25)
- 0:00Start
- 1:26King's Quest
- 7:28Blazer Web Assembly
- 9:15Design
- 10:57Action Bar
- 12:02Verb Picker
- 13:42Pops Up Pattern
- 16:20Game View Component
- 20:02Uninitialized Method
- 23:53Select Game Page
- 27:20Javascript Code
- 28:47Ijs Runtime Abstraction
- 32:01First Room
- 32:48Mouse Events
- 36:44Depth Sorting
- 37:40Walk Box
- 40:33Debug Mode
- 42:19Add Actors
- 47:20Metadata References
- 48:14Compile My Script
- 48:44Script Compilation
- 49:05Cat Diagnostics
- 53:45Index Db
- 55:59Global Hotkeys
- 56:51Hot Reloading
related talks
51mHands-on Development Experience Using wasm Blazor
16mFull stack web in .NET 8 with Blazor
59mBuild Blazor Components with Confidence and Precision
53mArchitecting Blazor Applications: An Angular inspired approach
49mArchitecting Blazor applications – An Angular inspired approach
49mArchitecting Blazor applications – An Angular inspired approach
57mRunning Blazor in production, lessons learned
49mArchitecture tips for hybrid apps with .NET MAUI and Blazor