ppy/osu

This is a cross-platform rhythm game client that manages gameplay across four distinct rulesets (osu!, Taiko, Catch the Beat, and Mania) with significant overhauls to scoring, mechanics, and visual presentation. The system provides comprehensive desktop and mobile interfaces, featuring real-time online connectivity for social interactions, multiplayer rooms, and live leaderboards. It also includes robust local data management for beatmaps, user settings, and replay statistics, supported by a modernized UI framework and extensive localization.

This period focused on a comprehensive modernization of the codebase, introducing a new Realm-based configuration system and a robust database infrastructure. The team significantly refactored core gameplay, UI, and online services, while also overhauling the multiplayer and chat systems to support a new hub-based architecture.

87 changes

This period focused on a comprehensive UI overhaul, introducing a modernized design language across settings, overlays, and the editor. Simultaneously, the codebase expanded to support iOS and Android platforms, integrating platform-specific features like file imports and update notifications.

96 changes

This period focused on a comprehensive overhaul of the online play and matchmaking systems, introducing structured room states, dedicated matchmaking flows, and a new multiplayer spectator architecture. The work also significantly expanded the UI with new card-based layouts, a redesigned wiki and chat overlays, and extensive localisation support.

77 changes

This period focused on the end-to-end implementation of the new Ranked Play multiplayer mode, including backend data models, matchmaking requests, and full screen/UI implementations for card selection and gameplay. Concurrently, the dashboard was enhanced with real-time online user lists and search functionality, while the desktop client added macOS installation verification and local score broadcasting via WebSocket.

13 changes

ppy/osu was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.