Project contribution report

Founder-Led Studio ProductionVertical Slice in Development

Project Breathe (Codename)

An original dark-fantasy open-world action RPG built around exploration, omen-driven storytelling, action combat, Spirit Glass equipment, soul-contract companions, and ritual preparation between expeditions.

PROJECT HERO[SCREENSHOT REQUIRED]

Project Overview

Project Breathe is a dark-fantasy open-world action RPG with JRPG influences.

Players explore a layered world, encounter omen-driven stories, fight creatures and hostile forces, recover Spirit Glass and scroll-based rewards, form Soul Contracts with supernatural beings, and return to settlements or ritual spaces to prepare for the next expedition.

Core experience: Explore → Encounter story, omens, and discoveries → Enter action combat → Recover Spirit Glass, scrolls, and materials → Contract, nurture, or strengthen companions → Craft and prepare within settlements → Pursue challenges and deeper regions → Continue exploration.

Its visual and thematic pillars include stained glass, ritual logic, gothic courts, death and grace, soul, flower, and wither motifs, organic life crossed with ancient technology, and beautiful systems carrying dangerous consequences.

Concept, worldbuilding, and systems development began in June 2020. Current production is focused on a scoped Unreal Engine 5.8 vertical slice rather than continuous full production across that entire period.

Project Snapshot

Project origin: June 2020
Role: Founder, Creative Director & Game Designer
Engine: Unreal Engine 5.8
Platform: Windows PC / Steam planned
Studio / ownership: Datura Mist Entertainment LLC
Team model: Founder-led solo production structured for future team expansion
Development: Solo, founder-led, and AI-assisted
Public title: Project Breathe (Codename)
Additional disciplines: Systems design · Writing · Worldbuilding · Technical art · Unreal Engine implementation
Current milestone: Unreal Engine 5.8 vertical slice
Classification: Founder-Led Studio Production
Status: Vertical Slice in Development
Public availability: Not currently public

Vertical-Slice Direction

Long-form concept, narrative, worldbuilding, and systems development began in June 2020.
Current production is focused on a Court of the Fallen vertical slice in Unreal Engine 5.8.
The vertical slice is intended to prove a compact version of movement and exploration, action combat, inventory, persistence, fast travel, carousel-style interface behavior, a limited enemy roster, a tameable familiar, basic Soul Contract behavior, weapons and Spirit Glass interaction, status or lethal effects, friendly AI, challenge-arena behavior, and a concentrated hub, path, and combat-space structure.
These items remain scope and implementation targets and do not establish public availability or verify every planned feature.

My Role

Founder, Creative Director & Game Designer
Original IP creation
Creative direction
Worldbuilding
Narrative development
Core-loop design
Combat and progression design
Creature and familiar systems
Equipment and Spirit Glass design
Soul Contract architecture
Quest and challenge planning
Economy and reward planning
UI and menu direction
Vertical-slice definition
Level and encounter design
Pitch-deck development
Data architecture
Unreal Engine prototyping
Blueprint planning and implementation
Technical-art direction
Documentation and design bibles
Feature dependency mapping
Scope and risk management
QA criteria
AI-assisted production direction

Project Breathe uses an AI-assisted production workflow for research, documentation, system analysis, implementation scaffolding, debugging support, and workflow automation. Ruin created and retains responsibility for the original IP, worldbuilding, narrative, game design, art direction, feature priorities, architecture decisions, acceptance criteria, and final validation. AI-assisted outputs are reviewed, revised, and tested before being accepted into production.

Contribution Record

Game DesignPrimary OwnershipDefines the core exploration, combat, reward, preparation, progression, companion, and challenge experience.Systems DesignPrimary OwnershipDefines the relationships among Spirit Glass, Soul Contracts, ritual preparation, progression, economy, encounters, and content architecture.Creative DirectionPrimary OwnershipDirects the original IP's visual, thematic, mechanical, narrative, and production identity.WorldbuildingPrimary OwnershipCreates and organizes the setting, cultures, motifs, terminology, regions, supernatural logic, and narrative foundations.Writing and NarrativePrimary OwnershipDevelops the narrative foundation, omen-driven storytelling, character and world context, and story-system relationships.Production PlanningPrimary OwnershipDefines production tiers, feature priorities, dependencies, risks, and the path from long-form IP development to a focused milestone.DocumentationPrimary OwnershipMaintains design bibles, mechanic cards, dependency maps, taxonomies, pitch materials, and production-facing records.Vertical-Slice ScopingPrimary OwnershipReduces the broad project vision into a Court of the Fallen proof focused on representative core systems and player flow.Content ArchitecturePrimary OwnershipDefines shared content categories and relationships for items, equipment, creatures, encounters, quests, travel, shops, skills, tutorials, and settings.Data-Driven DesignPrimary OwnershipPlans reusable Data Tables, tags, structs, enums, content schemas, and dependency-aware production structures.Level DesignPrimary OwnershipDefines the vertical slice's hub, traversal route, arena, encounter spaces, challenge flow, and representative zone structure.UI and UX DirectionPrimary OwnershipDirects the carousel-style interface, inventory, preparation, collection, navigation, and player-information requirements.Concept DevelopmentPrimary OwnershipCreates the original concept, thematic pillars, gameplay premise, milestone direction, and pitch foundation.QA and Design ValidationPrimary OwnershipDefines acceptance criteria and reviews player flow, mechanic dependencies, Blueprint behavior, data validity, interface navigation, and scope.Technical ArtSignificant ContributionDirects and develops the stained-glass, ritual, status, material, interface, and environment presentation needed for the focused milestone.Unreal Engine Blueprint WorkSignificant ContributionPlans and implements Blueprint prototypes and supporting gameplay structures for the current Unreal Engine milestone.Environment ProductionSignificant ContributionDevelops the representative hub, route, arena, and visual spaces required to validate the vertical-slice direction.Tools and Workflow AutomationSignificant ContributionUses reusable schemas, templates, structured documentation, and automation where useful to reduce isolated production work.AI-Assisted Production WorkflowSignificant Workflow ComponentUses AI assistance for research, documentation, system analysis, implementation scaffolding, debugging support, and workflow automation under Ruin's review.Gameplay ImplementationIn Active DevelopmentCurrent prototyping is validating player flow and system feasibility for the Court of the Fallen vertical slice.

Systems and Vertical-Slice Scope

Create and direct the original IP, world, narrative foundation, core gameplay loop, progression systems, content architecture, pitch materials, and production plan.
Define the Court of the Fallen vertical slice, its dependencies, acceptance criteria, level and encounter needs, and representative system targets.
Translate broad design material into reusable Unreal Engine structures, focused prototypes, documentation, and future-collaborator-ready production records.
The current milestone is intended to prove a miniature explore → encounter → combat → reward → companion → preparation → progression loop within one concentrated zone.

Spirit Glass and Soul Contracting

Contribution

Defined Spirit Glass as part of the project's equipment and supernatural progression language.
Defined Soul Contracts as a shared framework through which supernatural beings may contribute as active companions, mounts, embedded enchantments, or specialized support relationships.
Connected creature design, equipment, party composition, traversal, progression, narrative relationships, and reward systems.
Kept unrevealed creature identities and complete contract rules outside the public record.

Result

Established a unified design framework connecting supernatural relationships, equipment, rewards, traversal, and player progression.

Ritual Preparation and Consequence

Contribution

Connected Soulflowers, Wither Marks, status effects, ritual preparation, settlement interaction, mortality or consequence, crafting, and recovery.
Designed these concepts to create rhythm between danger, consequence, and preparation.
Kept hidden thresholds, unreleased story consequences, and detailed economy rules outside the public record.

Result

Turned the project's ritual and mortality themes into a practical preparation-and-consequence design structure.

Solar Map Progression

Contribution

Designed the Solar Map as a layered long-term progression structure built around repeated choices, tiers, build specialization, and controlled respec behavior.
Connected progression choices to combat, equipment, and exploration.
Excluded maximum progression counts, complete tier names, choice tables, and exact pity rules from the public record.

Result

Established a long-term progression direction that supports specialization while remaining connected to the wider game loop.

Data-Driven Production Architecture

Contribution

Planned shared content structures for items and ingredients, weapons and armor, Spirit Glass, recipes, sigils and status effects, monsters, familiars and bosses, drop tables, Soul Contracts, encounters and spawn rules, weather, fast travel, shops and pricing, skills, quests and challenges, AI profiles, tutorials, and settings.
Planned Data Tables, tags, structs, and enums to reduce isolated one-off implementations.
Kept complete internal tables and confidential content lists outside the public record.

Result

Created a reusable content-architecture direction intended to support implementation, iteration, and future team expansion.

Court of the Fallen Vertical Slice

Contribution

Scoped one primary zone containing a hub, traversal route, and arena.
Defined representative enemy, tameable familiar, weapon, Spirit Glass, interface, persistence, and challenge targets.
Planned a miniature version of the full exploration, combat, reward, companion, and preparation loop.
Framed the work as a current production target whose implementation status must be verified before public feature claims are made.

Result

Converted the larger IP into a measurable Unreal Engine milestone capable of testing representative player flow and system feasibility.

Development Workflow

01Creative vision
02World and narrative foundation
03Core-loop definition
04Mechanic cards and dependency mapping
05Content taxonomy and data schemas
06Risk and scope review
07Vertical-slice shortlist
08Unreal prototype
09Playtest and validation
10Correction and documentation
11Production expansion

Development began with long-form writing, worldbuilding, and system research.
Mechanics were translated into dependency maps and production documents.
Content categories and data structures were planned for Unreal Engine.
Risks and dependencies were reviewed before implementation.
The full vision was reduced to a focused vertical slice.
Current prototyping validates player flow and system feasibility.
Reusable structures and automation are preferred where useful.
Documentation is written to support future collaborators.

Cross-Disciplinary Collaboration

Project Breathe is currently a founder-led solo production structured for future team expansion.
Current documentation, shared terminology, content schemas, and dependency maps are designed to support future collaborators without implying a present full production team.
AI assistance supports research, documentation, system analysis, implementation scaffolding, debugging, and workflow automation; Ruin reviews, revises, tests, and validates outputs before acceptance.

Problems and Solutions

Problem

The full original-IP vision contains more interconnected systems and content than a focused milestone can prove at once.

Solution

Divided mechanics into core, supporting, and expansion tiers, then defined a focused Court of the Fallen vertical slice.

Outcome

Converted a broad RPG vision into an achievable proof containing exploration, combat, progression, companion interaction, interface, and persistence targets.

Problem

Interdependent content and gameplay systems created a risk of unclear dependencies and isolated one-off design.

Solution

Created content categories, dependency maps, shared terminology, and Data Table planning.

Outcome

Established clearer relationships between content and reduced isolated one-off system design.

Problem

Long-form lore and gameplay mechanics could drift apart as the project expanded.

Solution

Connected world concepts directly to mechanics including Spirit Glass, Soul Contracts, Wither Marks, and ritual preparation.

Outcome

The setting became a source of gameplay rules rather than background exposition.

Problem

Founder-led production creates a finite bandwidth constraint across design, implementation, documentation, validation, and presentation.

Solution

Used structured templates, reusable schemas, scope tiers, AI-assisted research and implementation support, and vertical-slice-first production.

Outcome

Preserved the project's larger identity while making current work measurable and reviewable.

Testing, Review, and Iteration

Testing and review

Current testing focuses on prototype feasibility.
Player-flow review
Mechanic dependencies
Blueprint behavior
Interface navigation
Data validity
Encounter and progression review
Scope validation
Documentation revision

Iteration

Prototype findings are compared against the intended core loop, feature dependencies, and vertical-slice acceptance criteria.
Mechanic cards, content taxonomies, data plans, and implementation priorities are revised as dependencies become clearer.
Current work is evaluated as milestone development rather than full-game validation.
No public QA, external certification, or packaged-milestone availability is claimed.

Current Production Outcome

Project Breathe currently has an extensive original-IP foundation spanning worldbuilding, narrative, systems design, content architecture, visual direction, pitch development, and vertical-slice planning.

Current Unreal Engine 5.8 production is focused on transforming that foundation into a playable Court of the Fallen vertical slice demonstrating exploration, combat, progression, interface, companion behavior, and ritual preparation.
The full game and current vertical-slice milestone remain in development.