implemented an action log & connected up the health bar. I don’t want to go overboard with text effects, but:
- combat actions are colour coded
- more important actions (like attacks) are brighter than others (like harvesting)
- older messages are dimmed

(also health bar lag)

smashed up a cabbage. played with knives. new combat sounds.

(I don’t know what I’m doing)

#gamedev #sounddesign

Made some sound effects for footsteps & potions. my first serious attempt at sound design, feedback is very welcome

(Combat sounds are not mine, included so bsky compression doesn’t crush the volume)

#gamedev #godot #screenshotsaturday

it’s pretty subtle, but I tried recording some of my own sound effects for the UI. (combat audio is placeholder/not mine)

#gamedev #godot

Added some (extremely placeholder) sound effects to the melee combat and it’s starting to feel very satisfying. Might go ahead and add sounds to everything

#gamedev

the isopods don’t like it when you get too close

#gamedev #screenshotsaturday #godot

added damage numbers & some hit fx — trying to make combat feel both snappy and juicy. (no audio yet)

#gamedev

improvements to the lighting system: walls are only lit if you’re on the same side as the light source. (map editor is already hugely useful for creating specific test levels)

#gamedev #screenshotsaturday

Added a basic lighting system (& made the isopods react to it).
#gamedev

heard you like containers. so I put containers in your containers
(implemented chests, randomised loot & openable items)

#screenshotsaturday #gamedev #roguelike

→ Actors have a ‘request_verbs’ method
→ it sends a signal that components can listen for
→ components respond w actions they theoretically support
→ request_verbs checks which are valid in the current context & returns a list
→ UI panel shows the list

(I am v satisfied with how this is working)

nearby / item interaction / inspect UI (I’m using keyboard inputs but this also works with a mouse)