Releases: M1PPosu/m1pplauncher
Releases · M1PPosu/m1pplauncher
v4.0b
M1PP Launcher v4.0b
Added
- Added a standard Windows
Setup.exeinstaller. - Added packaged updater support.
- Added launcher logging under
%LOCALAPPDATA%\M1PPLauncher\logs. - Added Discord Rich Presence support.
- Added built-in tosu support for telemetry/RPC.
- Added uninstall for very simple and easy uninstall.
- Added console
- Added Status
- Added Shortcuts (quick access buttons)
Changed
osu!stableis now the active supported client path.osu!lazeris temporarily disabled because M1Lazer is currently shut down for now.- Updated the launcher UI for the v4.0b release.
- Updated the News tab slides and links.
- Updated the bundled RelaxPatcher build. (Though RelaxPatcher seems to not work)
- Reworked the launcher build process so the updater is built first and bundled into the launcher.
- Standardized the Windows build path through
build.batandbuild-installer.bat. - Repo QoL, and other structural changes.
- Prob some other stuff I can't think of because this took 5 months to release.. ?
Fixed
- Fixed missing PySide6 bundling in the frozen executable.
- Fixed
qasyncbackend initialization by forcing PySide6 before import. - Fixed fresh installs not being able to launch osu because
installdata.jsonwas missing. - Fixed launcher-side osu startup polling so it stops after launch verification/injection instead of polling for the entire osu session.
- Fixed the Mods folder button to use the installed launcher mods directory.
- Fixed update prompt behavior so stale legacy version metadata does not trigger false update prompts.
- Fixed installer uninstall cleanup for launcher files, settings, logs, mods, and shortcuts.
- Prob some other stuff I can't think of because this took 5 months to release.. ?
Removed
Quite a bit of stuff
Notes
- Download and run
M1PPLauncherSetup.exe. - Windows SmartScreen or antivirus warnings may still appear because the executable is unsigned and new.
- M1Lazer is temporarily unavailable, so the lazer option is greyed out.
- This launcher is for M1PP/private osu!stable routing and is not for official Bancho use.
Also, stop ignoring the text and use "M1PPLuncherSetup.exe" to install the launcher
Hotfix 5/27/26 | Relax Patcher now works as intended lol
v3.0b
IF YOU WANT TO INSTALL THE LAUNCHER, USE THE M1PPINSTALLER.EXE, DON'T USE THE OTHERS
M1PP Launcher Beta 3
Lots of bugfixes. You can download files you can find on https://4ayo.ovh/m1pposu/files/launcher/latest/ here on GitHub.
Bugs Fixed
- The uninstall process may trigger some anti-virus software.
- The uninstaller sometimes leaves an empty folder and does not delete it.
- Mods not injecting.
- Installer using corrupted osu! installations.
- Shortcut icons missing.
- Launcher acctidentally corrupting its own osu! installation during updates (your maps and skins were unaffected by this)
Unfixed Bugs
- osu! needs to be launched multiple times on first-time install. This is mostly due to the osu! updater not passing the
--devserverargument to the osu! client after an update (however it is fixable) - It takes a very long time to launch the M1PP Launcher app.
- Linux and Mac are not currently supported.
- The installer looks like it's stuck at 99%
- The launcher needs a logging system so we can diagnose issues more quickly.
- The code needs more documentation and a cleanup.
v2.0b
IF YOU WANT TO INSTALL THE LAUNCHER, USE THE M1PPINSTALLER.EXE, DON'T USE THE OTHERS
M1PP Launcher Beta 2
The first release of the new beta. You can download files you can find on https://4ayo.ovh/m1pposu/files/launcher/archive/BETA2/ here on GitHub.
Known Issues
- osu! needs to be launched multiple times on first-time install. This is mostly due to the osu! updater not passing the
--devserverargument to the osu! client after an update (however it is fixable) - It takes a very long time to launch the M1PP Launcher app.
- The uninstaller sometimes leaves an empty folder and does not delete it.
- Linux and Mac are not currently supported. This is planned, but in the meantime, you can try your luck using WINE.
- The uninstall process may trigger some anti-virus software. We are currently using an extremely hacky implementation with
.batfiles... yeah. - The installer looks like it's stuck at 99%
- The launcher needs a logging system so we can diagnose issues more quickly.
- The code needs more documentation and a cleanup.