All build stories

03 / First C# game / Freshman year

Skeleton Survivors

My first C# project, built before I started working with AI.

A small Unity survival game that taught me how classes, game loops, collisions, enemies, scoring, and persistence become something a player can feel.

RoleSolo developer
StatusVideo archive
PeriodFreshman year
StackC# · Unity · Game logic · Object-oriented programming

01 / The beginning

Before production systems, I wanted to make something move.

Skeleton Survivors was a freshman-year Unity project and my first practical reason to care about C#. I built it before I began using AI development tools.

The scope was small: a player survives against chasing enemies while the score and high score record progress. But it turned abstract classes and methods into a feedback loop I could see and play.

02 / What remained

The source was lost, but the project still explains where my interest began.

I no longer have the source repository, so I will not reconstruct technical claims I cannot prove. The gameplay video is the evidence that remains.

Its value in this portfolio is chronological: it shows that my interest in C# existed before my internship and before AI-assisted development became part of my workflow.

System view

A simplified architecture to replace with the final diagram.

This intentionally describes boundaries without exposing credentials, internal hostnames, or company identifiers.

01Player input
02Enemy chase
03Collision loop
04Score + high score

Evidence snapshot

What this story can honestly support.

BuiltFreshman year
AI assistanceNone
SourceNo longer available
EvidenceGameplay video

Media shot list

Replace these cards with safe, deliberate proof.

Every placeholder states exactly what to capture. Use synthetic data and keep secrets, account identifiers, and private company material outside the frame.

YouTube embed

Primary evidence

The original gameplay video documents the surviving build and when this C# learning journey began.

16:9 screenshot

Gameplay loop

Capture a frame that shows the player, several enemies, and the score UI at the same time.

Public portfolio rule

Prove the work without exposing the environment.

All demos should use synthetic content, personal sandbox accounts, rotated credentials, and newly captured media. Never publish tokens, private keys, internal logs, production endpoints, Drive identifiers, or company-only source code.

Next build story

BedReads SEO Reader