I’ve been reviewing the existing damage system in Clay-Bang. For roguelikes, all enemies must have health, ergo these clays have health. In real life, your aim depends on how the pigeon will break. If you clipped it on the edge, that means you hit the nose. And then there’s the more satisfying shot, hitting it in the middle completely vaporizes the clay and your aim was dead on. This is my approach to simulate those kind of shots.
We are at a pretty good spot with setting up a REST API for the pick-a-gun server. I have some routes and I’m able to get new JSON’s. The overall plan is to throw this inside a docker container but I need one important thing. Logs, the make or break situation to determine if our application is actually doing something or giving us important error messages along the way. I want to use Kibana for monitoring these logs so we’ll form our JSON to make it Kibana friendly. Technically, kibana will receieve any JSON for standard output but we have a nice little tool for making that easier.
We’ve made a big move in moving everything into packages for the pick-a-gun service. Now we want to use the core package and use those function to build a REST API.
For this implementation, I want to use Gorilla mux, a tried and true request and router dispatcher. I can build routes easily and more importantly, middleware is easy to plug in(more on that later.)
I have begun working on a REST API server with Gorilla for the pick a gun service and imported the core API. I realized that Fyne was getting indirectly imported even when the internal core package doesn’t need it, it just runs on the standard library.
Sure it’s indirect, but I’m trying to keep Fyne in the UI. To eliminate this, I need to finally restructure the ui, cli and core into their own packages. When this started as a small project, I admittedly loosened some of my standards in exchange for faster development. The technical debt isn’t bad but I should take a step back to do some general maintenance of my repo.
When I added to the API, I set the table. When I updated the CLI, I fired up the grill. Tonight, when I update my UI, I will feast. So far the development has been smooth. The API required minimal changes so the CLI and UI we’re easy to work on. Only thing I needed to do was update the images and add some buttons for character selection.