For #ScreenshotSaturday I have a small UI widget update to share: the incoming message monitor on the top left column.
Basically, it takes the timestamps of new messages in the log from my text-based browser game prototype (Blasphemess), and then it represents visually how many messages there are and how recently they appeared. It updates in real-time, and because it's a log-scaled X-axis, it can range from 1 second ago to 10 hrs ago with clarity for the player.

The intent is to allow players to understand at a glance if they are dealing with new messages coming in actively, or if they are looking at old messages, since some players may be logging in once a day, and others may sit there actively for hours at a time.

The widget is user-configurable, here they are split into 3 streams: combat, misc. and speech monitors, but there's also a combined monitor variant too.

Today in #GameDev I got PyScript, SvelteKit, and PixiJS all playing nicely together in a single docker container.
The result: the game I've been jamming on can display the hexagonal map in the browser.
Despite the game's core being written in Python...

Next up, hooking up controls and actions so that I can play the game outside the developer console.

#GameDevelopment #Svelte #PixiJS #PyScript

For #ScreenshotSaturday I've got my browser game's user interface.
The UI won't win any awards, but... it's functional for a prototype!

I've learned a lot about #Svelte and #SvelteKit and #Frontend dev work in the process of making this. Everything is so reactive thanks to Svelte.

The screenshot shows the top nav bar, a hotbar of preconfigured actions such as combat attacks, a tile map (of the beach district so it's got no SVGs to show off), the message log, and the character information footer.

#GameDev #IndieGameDev

I finally tracked down the last bug related to a race condition in my browser game. I'm using #Postgresql advisory locks with #SQLAlchemy but in certain cases I could get two instances of a status effect applied to an entity that was supposed to be a singleton.

Bug fixing is not how I like spending my #GameDev time, but catching tricky ones like this is a good thing in the long run!

I also added a unit-test to check for this specific context, in case regressions ever happen that allow singletons to duplicate like this again.
The picture is the output of the test failing when I revert the bugfix!