What
Replace the current CLI-based entrypoint with a full GUI launcher built on top of ppy.osu.Framework and ppy.osu.Game.
The launcher should become the primary entrypoint for osu!cc and provide a user-facing interface for:
- Installing and configuring osu!cc.
- Selecting and launching the osu!lazer installation.
- Managing osu!cc versions and components.
- Checking for and installing updates.
- Managing installed plugins/mods.
- Displaying relevant launcher/runtime status and errors.
As part of this change, the separate updater plugin should be removed. Its update functionality should be moved into the launcher itself, so updating osu!cc does not require the osu!cc runtime to already be running.
The CLI should either be removed entirely.
Why
The current CLI-oriented workflow makes osu!cc feel more like a developer tool than a complete client-side extension ecosystem.
A dedicated launcher would provide a much more coherent installation and update flow and would also give osu!cc a natural place for functionality that currently has to be implemented as a plugin.
Not a cheat
This feature only changes the local installation, launching, updating, and management experience of osu!cc.
Approach (optional)
A possible architecture would be to introduce a dedicated launcher application based on ppy.osu.Framework, with ppy.osu.Game used where integration with the osu!lazer environment is required.
What
Replace the current CLI-based entrypoint with a full GUI launcher built on top of ppy.osu.Framework and ppy.osu.Game.
The launcher should become the primary entrypoint for osu!cc and provide a user-facing interface for:
As part of this change, the separate updater plugin should be removed. Its update functionality should be moved into the launcher itself, so updating osu!cc does not require the osu!cc runtime to already be running.
The CLI should either be removed entirely.
Why
The current CLI-oriented workflow makes osu!cc feel more like a developer tool than a complete client-side extension ecosystem.
A dedicated launcher would provide a much more coherent installation and update flow and would also give osu!cc a natural place for functionality that currently has to be implemented as a plugin.
Not a cheat
This feature only changes the local installation, launching, updating, and management experience of osu!cc.
Approach (optional)
A possible architecture would be to introduce a dedicated launcher application based on ppy.osu.Framework, with ppy.osu.Game used where integration with the osu!lazer environment is required.