Skip to content

Professional · Nov 2025 – now

Unannounced game at Blue Gravity Studios

Core gameplay, UI and audio systems, procedural maps and editor tools for a game that isn't public yet.

Blue Gravity Studios logo on a dark blueprint grid; the game itself isn't public yet.

TL;DR

  • Architected core gameplay systems in Unity (C#): a reactive, event-driven stat framework, a universal object-pooling manager and a modular weapon system with six combat archetypes.
  • Built a procedural map generator on a custom Diffusion-Limited Aggregation algorithm for roads and multi-zone biomes, plus editor tools that speed up level authoring.
  • Designed a centralized UI architecture and refactored an inheritance-based button framework from 18 scripts to 4 component-based ones.
  • Built the audio system on FMOD from scratch, then a settings system and gamepad support (Xbox, PlayStation and Switch pads, with input icons that follow the active device).
  • Traced build-only failures to their root causes and audited every asset in the project, identifying about 17,000 unused files.
  • Alongside the code, I keep the team's main content spreadsheet and help coordinate priorities with the other programmers.

Overview

Since November 2025 I've been a Unity Game Developer at Blue Gravity Studios⁠ (opens in a new tab), working remotely from Recife on a game that hasn't been announced. Until it is, I can't name it or show it, so this page describes my part in words only.

What I work on

  • Stats: a reactive, event-driven stat framework.
  • Pooling: a universal object-pooling manager.
  • Weapons: a modular weapon system that supports six combat archetypes.
  • Procedural maps: a map generator built on a custom Diffusion-Limited Aggregation (DLA) algorithm for road placement and multi-zone biomes, with custom Unity editor tools to speed up level authoring.
  • UI: a centralized UI architecture for character select, inventory, NPC shops and multi-tier tooltips. Along the way I refactored an inheritance-based button framework from 18 scripts to 4 component-based ones.
  • Progression and meta systems: chain-quest pools, boss spawns, timed map events and an extraction loop with dynamic difficulty scaling.
  • Audio: an audio system on FMOD, built from scratch. Objects reference data-driven sound definitions (one per FMOD event, kept in sync by an editor tool) instead of raw events. One audio config holds a tab per category (player, combat, enemies and bosses, world, run events, UI), with music and ambience set per stage. World loops freeze on pause while one-shots finish, and a pause snapshot muffles the music. Includes an editor validation tool and a debug trace that logs every sound. I then wired the game's sounds in batches, footsteps that change with the ground surface included.
  • Settings: one source of truth for every setting, with only changed values saved. Resolution changes revert after 20 seconds unless confirmed; 2K, 4K and ultrawide support with ultrawide UI fixes; key rebinding for keyboard and gamepad; a HUD size option. Reachable from the pause menu and the main menu.
  • Gamepad support: a device monitor that knows which input is active and which pad family it is. Input icons per family (Xbox, PlayStation, Switch, generic) follow the active device and any keybind change. A shader-drawn virtual cursor with menu aim assist, and an input router so a button shared by gameplay and UI never triggers twice.
  • Player-facing UI: an end-of-run summary screen that replaced game over, with run statistics and an animated reveal. Meta-progression shop and item-ban screens built on a teammate's backend. A focused targeting mode that locks targets by priority, with a HUD indicator and a world marker. Tooltips that show live stat changes from owned items. Mini-boss health bars, a map-select screen with camera transitions, and shop feedback.
  • Game feel and shaders: camera shake that scales with damage and a damage vignette drawn by a custom shader. A text outline and drop-shadow system with its own shader, because TextMesh Pro's outline couldn't get thick enough. An item-icon outline and glow shader for rarity and item states. A rebuilt health bar that fixed heals not showing, with hurt, heal, overheal and shield feedback.
  • Demo build: I owned the demo's content restrictions: a data-driven item allow-list that leaves shared assets untouched, so merges stay conflict-free, plus character restrictions and a run that ends at the first boss.
  • Build and pipeline debugging: failing 3-hour builds traced to editor-only flags on 188 components in 36 prefabs; music missing only in builds traced to assets duplicated between Resources and Addressables, proven by reading the build's bundles; an editor freeze from a circular stat-data chain; a URP rendering error fixed with a custom renderer feature.
  • Asset audit: an evidence-based audit of every file and package in the project (references, code loads, build contents) that identified about 17,000 unused files (about 16 GB).
  • Debug tooling: every debug shortcut moved into one table backed by dev console commands.
  • Documentation: internal technical documentation for these systems.

Production

Alongside programming, I built and maintain the team's main content spreadsheet: a feature-progress dashboard plus the entity attributes, passives, items and status effects. I create and manage tasks and help coordinate priorities with the other programmers. It's the part of the job where I'm growing toward production.

I'm also the programming point of contact for our audio designer: I planned the audio integration in batches with written briefs, kept the shared SFX database's “implemented” column accurate by checking every row against the game, and flagged design-side issues. I manage the audio branch flow, resolve merge conflicts in Unity assets for the team, cross-check the design document against implemented data, and when a teammate asked, I scoped a multi-boss refactor: an estimate per piece, what would break, and a recommendation.

Results

  • Button framework refactored from 18 scripts to 4 component-based ones
  • 385 FMOD events behind data-driven sound definitions
  • 188 SFX database entries verified against the game
  • A 3-hour build failure traced to 188 components in 36 prefabs
  • About 17,000 unused files (about 16 GB) identified for removal

Like this?

Let's talk

Open to conversations about developer and production roles, and collaborations. I'm in Recife, Brazil (UTC−3).