✦ Development timeline
This timeline documents when ideas appeared, when projects changed direction, what was built, and why each milestone mattered.
Vertical archive
The timeline follows development downward. Dates come from your project records, while each card presents only the information suitable for a public technology archive.
A dedicated project space begins organizing the universe, story structure, gameplay systems, shard concepts, and future competitive ideas as one long-term game project.
The storyline defines a squad trapped inside a cosmic storm. A shattered crystal sits at its center, while the storm carries the arena through corrupted systems whose enemies, hazards, and visual identity change around the players in real time.
The project separates its major gameplay systems into a structured development phase and begins recording how cooperative survival, progression, encounters, and future competitive modes fit together.
Void, Solar, Ice, Energy, Storm, Gravity, Toxic, Crystal, Inferno, Tech, Corruption, Time, and Abyss receive distinct identities that can influence enemies, hazards, atmosphere, and player strategy.
Weapon behavior is organized around ammunition types, energy, distance, air conditions, and material penetration. Separate equipment records begin defining how combat gear can support the larger tactical design.
The concept develops around 6v6 search-and-destroy rounds with no respawns, night combat, limited visibility, signal ghosts, deliberate teamwork, and decisions based on incomplete information.
A dedicated PvP map area is added so competitive spaces can be explored without mixing them into the main cooperative story documentation.
The first public version is connected through GitHub and deployed online, creating a home for projects, ideas, development history, and future community discussions under the KillerReaper identity.
The timeline is expanded from broad example entries into dated public summaries based on the real project archive, while unreleased files and sensitive details remain private.
New records will be added whenever a project reaches a milestone, changes direction, produces a prototype, or reveals an important lesson.
What each entry preserves
A useful history explains what actually happened. Each full entry can connect the visible timeline to deeper private or public records.
What the project or idea looked like before the change.
What changed and the reason behind that decision.
What the update created, solved, or made possible.
Connected notes, images, files, prototypes, or code history.
Connected history
An idea can begin in the Ideas archive, appear here when it changes, and later connect to a full project page. This keeps the original thought and the current version from becoming separated.
Explore the Ideas archive →Public record, private source
The website shows selected summaries. Full design documents, raw research, prototypes, and unreleased details can remain private, with Supabase later managing which records visitors may see.