Dangerous Collection Postmortem
Introduction: Dangerous Collection is my second solo-developed game, a lighthearted catcher-style experience built in Unity. You play as a treasure-hungry basket, racing against time to collect falling treasures while dodging hazardous items like bombs and cursed bones.
This project was an opportunity to explore a new genre while deepening my understanding of weighted spawning systems and pooled actor management. It also allowed me to experiment with intuitive feedback loops and short-session gameplay design.
What Went Right
System Reuse Across Genres: I successfully adapted pooling, UI flow, and spawn weighting from previous projects into a new genre. This confirmed the flexibility and scalability of my architectural approach.
Clean Execution: The project shipped with no major bugs or blockers. All core systems functioned as intended, and the gameplay loop remained stable across multiple test sessions.
Short-Session Design: I designed a game loop that supports quick, relaxing play. This helped me experiment with pacing and feedback in a low-complexity environment.
Reinforced Skills
-
Modular pooling logic for collectibles and hazards
-
Weighted spawning systems for treasure vs danger balance
-
UI flow from title to game over with minimal friction
-
Browser-based deployment and optimization for short play sessions
What I'd Explore Next
-
Adding temporary powerups and debuffs
-
Adding updated sound effects, visual effects, and animations to play based on what is collected
-
Adding an ability to destroy the dangerous objects rather just dodge them, but make it a reflex challenge requiring precision
Conclusion: Dangerous Collection wasn't about inventing new systems. It was about proving that my existing ones are reusable, adaptable, and reliable. It gave me space to refine my workflow, validate my design instincts, and explore genre flexibility without scope creep.