Cb Games — Dev

Player is a memory-merchant cyborg in a fallen city. Narrative mechanic: Selling memories changes player stats + unlocks different factions. Act 1: Must sell own happy memory to pay debt. Loses empathy (mechanical effect: +combat, -trust). Act 2: Factions want different memories. Player’s remaining memories determine which endings are possible. Act 3: Final choice: restore old self (costs all power) or rule with stolen memories.

: Gameplay systems, including animation, user interface (UI), sound design, and overall "game feel". cb games dev

Short answer: Just a developer who loves weird mechanics and tight feedback loops. Long answer: I’ve been tinkering with game dev for a few years — Unity, Godot, a little bit of raw C++ and SDL when I’m feeling masochistic. The “cb” stands for the initials behind the code, the commits, and the 2 a.m. debugging sessions where you realize you swapped Y and Z axes again. Player is a memory-merchant cyborg in a fallen city

// Update game logic and state