ToolUp Tuesday - #4
Chris and Matt take on Go (Golang) for the first time on the ToolUp Tuesday live stream, building a player decisions REST API for their game application. They start with a recap of Go fundamentals — variables, types, structs, and pointers — before diving into HTTP routing with the Gin framework. The pair discuss Go project structure, comparing it to their .NET and C# backgrounds, and explore how Go handles packages, imports, and the module system. They work through setting up controllers, route handlers, and in-memory data structures, frequently mapping Go concepts back to familiar object-oriented patterns. Along the way, they troubleshoot Go environment issues including version upgrades and GOPATH configuration. The session wraps with a working REST endpoint for player decisions, setting the stage for integrating state stores in future episodes.
Related Content
ToolUp Tuesday - #3
Chris and Matt build the world events engine in .NET, connecting it to the Player State models via project references. They design a state machine architecture for the game engine, discuss action points as a game mechanic, and plan the player decisions API in Go for the next episode.
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.