Profile & Energy Systems

Overview

A foundational update focused on first-time pilot setup, clean player save initialization, mission energy usage, offline energy regeneration, and internal testing stability.

What Changed

• Added first-time pilot name creation for new players.
• Created a cleaner new-player initialization flow for fresh installs.
• Corrected the issue where internal test player data could appear in deployed builds.
• Ensured Tech Shards, upgrades, and progression data begin from zero for new save data.
• Added the first version of the mission energy system.
• Set the player’s maximum energy capacity to 10 cells.
• Configured each stage launch to consume 1 energy cell.
• Implemented energy regeneration at 1 cells every 12 minutes.
• Allowed energy to regenerate while the app is closed using device-time tracking.
• Prepared the flow for future rewarded-ad energy recovery.

Development Notes

This update was a critical step toward making Phoenix Vector behave like a real deployed game rather than a local development build. The previous test data issue revealed the need for a cleaner new-player flow, proper save initialization, and stronger separation between development testing data and live player progression.

The energy system also began taking shape in this version. Players now have a limited mission launch resource that regenerates over time, creating the foundation for future ad rewards, pacing, and mobile progression tuning.

Next Objectives

Upcoming work will continue refining the front-end experience, improving menu flow, strengthening the N.T.D.C. interface direction, and preparing Phoenix Vector for smoother internal testing updates.