u/Aromatic-Ad9337

Hey all! I’m designing active task cards for my game. Players use these cards to track the resources required to complete a task.

The three cards show different states:

• No requirements completed
• One requirement completed
• All requirements completed

The UI was designed in Figma and implemented in Godot. The target audience is desktop players who enjoy management and automation games.

I’d appreciate feedback on:

• Is the progress clear at a glance?
• Are completed and incomplete requirements distinguished enough?
• Is the relationship between each number and its resource icon obvious?
• Does the visual hierarchy work, or does anything attract too much attention?

The main reference for this design was a panel from another game (shown in the second image). However, I don’t like that it replaces the resource amount with a checkmark once the player has collected enough.

Codex made this free game. Enjoy here https://s0fted.itch.io/clikky or directly https://clikky.lua-game.com/

No in-game purchases. Would appreciate any kind of feedback, roast it and/or praise it.

8% weekly usage left >.<
I suppose I'll have to come up with some plans to go out somewhere.

Hey! With Codex I've built a short vertical slice of space roguelite game. While doing it, I questioned myself, what if I just ask you guys about the direction – and the idea clicked in the head – I asked Codex if it can make a simple gameplay video. Turned out Godot has everything for it, so here it is – the simplest video of the gameplay made by Codex.

I'm sure many of you know this possibility, but for me it was a true discovery. Feel so exited!

I think the gunship is kinda overdetailed. Feels like there should be another "step" between interceptor and gunship. May be a cruiser that'll look less detailed than gunship.

Auto-targets the fastest hostile in range. Splash: 120 radius, 70-100% damage.

Auto-targets the fastest hostile in range. Splash: 120 radius, 70-100% damage.

Initially, I explored a few variations for indicating item condition (durability) in the station UI. Then I realized I would need to explain these indicators in a tooltip. So I reduced the number of colors used. Since I also need to highlight the module parameters (in progress), I wanted to avoid making the interface look like a rainbow or a traffic light.

Initially, I explored a few variations for indicating item condition (durability) in the station UI. Then I realized I would need to explain these indicators in a tooltip. So I reduced the number of colors used. Since I also need to highlight the module parameters (in progress), I wanted to avoid making the interface look like a rainbow or a traffic light.

Initially, I explored a few variations for indicating item condition (durability) in the station UI. Then I realized I would need to explain these indicators in a tooltip. So I reduced the number of colors used. Since I also need to highlight the module parameters (in progress), I wanted to avoid making the interface look like a rainbow or a traffic light.

Initially, I explored a few variations for indicating item condition (durability) in the station UI. Then I realized I would need to explain these indicators in a tooltip. So I reduced the number of colors used. Since I also need to highlight the module parameters (in progress), I wanted to avoid making the interface look like a rainbow or a traffic light.

When activated, slows the nearest target. Light pirates (Scouts) are equipped with this module; there's a small chance it will drop when they're destroyed.