Roadmap · STYGION PLAY
Everything we are building, in the open
No dates, no promises we cannot keep. Just what we are thinking about, what we decided to do, what somebody is working on today, and what is already out.
Last thing out A project can be renamed, cards and all 3 weeks ago
Exploring
4Ideas we keep turning over. None of it is a promise.
A module for our own game
When there is something to play: install it and launch it straight from PLAY.
Hosted-game modules (Arma, Hytale…)
Placeholders and later real modules for games STYGION hosts.
In-shell notifications
Update, friend online, download status — after core flow.
STYGION ID in the shell
Sign-in and later friends / presence — after game launch is solid.
Planned
6Decided. Waiting for its turn.
Onboarding and module choice
First run: data path, which games to install, no bulk you do not need.
Auto-update the PLAY shell
Version check via our backend, changelog, update only with consent.
No mock data, feature isolation
Same rules as Launcher: empty state or WIP, modules isolated.
PLAY — shell for our and hosted games
One home for our own games and for the titles we host. It is not a store, and it does not replace STYGION Launcher — Minecraft modpacks stay there. Nobody is building it yet: there has to be a game for it to launch first.
Module picker + isolated game modules
Root picks a game; each module installs/removes in isolation (MC, Arma, Hytale…).
First game module + launch
When the first module lands (placeholder / own game): install, library and launch from the shell. Minecraft modpacks stay with STYGION Launcher.
Building
0Somebody has their hands on it right now.
Nothing here
Done
0Built and out. Newest at the top.
Nothing here