ToolUp Tuesday - #3
Chris and Matt tackle the world events engine, opening the project in Visual Studio for its stronger .NET development experience compared to VS Code. They connect the engine to the Player State models using .NET project references — acknowledging it as a pragmatic but temporary shortcut that will need refactoring into proper NuGet packages later.
The episode dives into game design architecture, conceptualizing the engine as a state machine that loads current world state, applies player inputs and world events, and produces updated state. They design an action points system where players spend points to make decisions each turn, with costs varying by action type. The discussion also covers github.dev for browser-based editing, and they plan to build the player decisions API in Go for the next episode.
Related Content
ToolUp Tuesday - #1
In this debut episode of ToolUp Tuesday, Chris and Matt kick off a new series by planning a massively multiplayer management sim game from scratch. They design a microservices architecture, choosing .NET for the world events engine and Go for player decisions, and set up a GitHub repository with GitHub Projects for backlog management.
ToolUp Tuesday #2
Chris and Matt start building the Player State API using .NET Web API, defining data models for the SpaceBar management sim game. They scaffold the project, discuss minimal APIs versus controller-based approaches, and set up a GitHub Actions CI workflow to build and validate the service on every commit.
Getting into DevRel
What is Developer Relations, and how do you build a career in it? Chris is joined by Martin Woodward — Director of Developer Relations at GitHub and the person who brought Git to Microsoft — to explore the open source contribution funnel, what drives community leaders, the community-building skills that underpin a DevRel career, and how platforms like GitHub Actions achieve explosive growth through network effects.