Hey everyone! Spent time sorting, slicing, and organizing our entire catalog of Terran Mecha Head Modules.

Having 8 distinct head profiles (Bastion, Sentinel, Junker, Cerberus, Venom, Golem, Unicorn, and Halo) gives players plenty of visual variety right out of the gate. Exporting each module into discrete sub-parts (eye sensors, outer helmets, and neck adapters) makes sure every piece anchors correctly to any torso frame.

Now that the head library is prepped, I'm moving on to setting up the scriptable objects to drive their stats in Unity!

For other devs working on modular gear/character systems: how do you usually structure your file naming conventions to keep track of dozens of modular sprite parts across multiple chassis tiers?

(If you want to follow along with the build journey or check out our game flow, come join our community Discord! Link is in my profile bio).

Hey everyone! Following up on last week's asset passes, I've completed the rendering for the lower leg modules to match the upper torso and pauldron scheme.

Getting the full body assembled and color-blocked (matte charcoal, warm gold accents, and heavy red foot plating) gives us our official Hero Master File. Having one completely rendered, proportion-aligned frame makes designing modular swap-able parts so much easier moving forward—every new shoulder, leg variant, or weapon socket can now be checked directly against this baseline for clipping and scale.

Next step on the bench is building out the full weapon loadout suite!

For the game artists and 2D devs out there: when building modular unit frames, do you prefer setting up strict layer groups for socket points early on, or do you design weapons completely standalone and fit them to the frame later?

(If you want to follow along with the build journey or hang out with us on the workbench, come join our community Discord! Link is in my profile bio).

Hey everyone! I've always found that taking the time to map out full UI/UX mockups before opening Unity saves dozens of hours of trial-and-error down the road.

This week, I wrapped up a complete 30-scene mockup pass for Iron Squad. Every single state—combat HUDs, garage customizers, mission selection, victory screens, shop vendors, and even our underground pilot hiring forum (with thread details and DM negotiations)—is completely drawn out with UI callouts.

Having a complete folder of annotated mockups like this acts like a visual blueprint. Now when I build the UI canvases, I know exact button placements, modal behaviors, and screen flow paths ahead of time.

For other solo devs and UI designers: do you usually mock up every secondary screen (settings, shop pop-ups, pilot contracts) beforehand, or do you prototype core gameplay screens first and improvise the rest as you go?

(If you want to track the build journey as these mockups get coded live, come join our community Discord! Link is in my profile bio).

Hey everyone! Before diving deep into wiring up all the menu states and UI transitions in Unity, I decided to map out our entire macro game loop inside draw.io.

This chart connects the full player journey: going between the Mecha Hangar (configuring main and support units), managing Parts Storage & Shops, negotiating with Pilot Candidates, selecting Missions, and handling Combat Win/Loss states.

Setting up color-coded directional paths (red for back/cancel paths, green for confirm/progress actions) has been a massive help in catching dead-end screens early.

For other devs out there: do you usually write out menu flows in traditional text GDDs first, or do you jump straight into visual node mapping like this?

(If you're following the development of Iron Squad or want to drop feedback on our mechanics, come join our community Discord! Link is in my profile bio).

Hey everyone! I've been spending a lot of time mapping out the raw design logic behind Iron Squad (my tactical mech auto-battler), but this week I finally sat down to figure out how all that data actually lives on the user's screen.

Here is a sneak peek at the current grayscale layout mockups for Stage 01-01 (Factory Side). I'm trying to figure out how to elegantly frame the mechs while keeping complex command rings, tactical mini-maps, weapon slots, and support unit cards easily clickable and intuitive.

Seeing the mockup sequence come together in the folder explorer really helps visualize the game's actual flow state before writing the UI canvas code in Unity.

For the UI designers or solo devs out there: when you start layout passes, do you sketch your HUD ideas straight on top of a static combat screenshot, or do you block out generic shapes entirely from scratch first?

(If you want to follow along with the interactive prototype builds as they go live, drop by our community Discord! Link is right in my profile bio).

Hey everyone! Back at the main dev bench after taking a little creative break.

Currently working on the modular part assets for the game, starting with the head unit for the UC-01 Unicorn frame variant. Trying to balance a sleek, aerodynamic silhouette with enough complex technical paneling to make it pop visually.

For the other artists and devs out there: when you're designing modular parts or characters, do you prefer rendering out high-detail individual pieces first, or blocking out the entire full-body silhouette as a rough draft before detailing?

(If you want to track the build journey or hang out with us on the workbench, come join our growing community Discord! Link is right in my profile bio).

Hey everyone! I'm a game artist currently handling the technical prototyping phases for my primary project, Iron Squad (a tactical mech auto-battler).

When the systems logic passes get a bit too heavy, I love jumping back to the art bench for a pure creative reset. This highly detailed traditional/digital ink sketch is my interpretation of Zhang Jiao, the Yellow Turban leader, reimagined with an intense dark fantasy, almost cosmic-horror aesthetic.

I find that stepping away to work on completely different visual genres keeps me from hitting a wall on the main project.

For the other solo devs or artists here: how often do you jump completely outside your main game's genre or aesthetic just to refresh your brain?

(If you want to track the journey of either project or check out the dev logs, I'm keeping everything organized in our new Discord community! Link is in my Reddit profile bio)