ModsFinder

OSU Touch Grass

by caxapexac

OSU Touch Grass brings a copy of osu lazer into Minecraft, so players can play osu beatmaps on a monitor block inside the game world.

NeoForgeClient and serverCustom license1.21.1

What it does

Players run osu lazer inside Minecraft through a CoreCLR runtime embedded in the Minecraft JVM, with both sharing one OpenGL texture. The build tracks osu 2026.505.0 on osu-framework 2026.428.0, and the source is bundled with the mod. Input comes from a pen, mouse or keyboard combined into crafted items that a player holds in hand, and holding Shift lets the player interact with Minecraft while playing.

A monitor block of arbitrary size is placed in the world and launched with a redstone signal, and several independent screens can run at the same time. Score submission, per-world leaderboards with weighted pp rankings, friends, profile pages and presence chat travel over a network transport layer re-implemented on top of Minecraft packets. Beatmaps are imported by dropping .osz files into the osutouchgrass-maps folder.

On first boot the mod extracts about 370 MB of bundled CoreCLR and osu binaries into osutouchgrass-cache. Game data such as beatmaps, scores and settings is stored in an osutouchgrass folder that is isolated per Minecraft instance. The mod is for NeoForge 1.21.1 only and requires Architectury API. It runs on client and server, and the code is under a custom license that is not open source.

Key features

  1. Full osu lazer client

    The game runs as the osu lazer client inside a Minecraft block, not as a reduced imitation.

  2. Monitor blocks

    Monitors can be sized to any rectangle and started with a redstone signal, and several can run side by side.

  3. Crafted input items

    A pen, mouse and keyboard are crafted as items and held in hand to control the game.

  4. Per-world leaderboards

    Scores are submitted and ranked per world with weighted pp, and friends, profiles and chat are included.

Compatibility

Latest build for each game version and loader.

1.21.10.1.0
ReleaseBetaAlphaNot available

Only full game releases are shown. This mod publishes no snapshot builds.

Requirements

Dependencies declared by the latest file for each loader.

Required 1

Architectury APIAn intermediary api aimed to ease developing multiplatform mods.
Required

Use cases

Multiplayer rhythm sessions

Servers can run shared monitors so players compare scores and chat from inside the same world.

Map imports

Owners can add their own beatmaps by dropping .osz files into the maps folder.

Who it’s for: Players who want osu beatmaps inside Minecraft, and server owners willing to host a large client-side game runtime on both sides.

Questions

Does OSU Touch Grass need Architectury API?

Yes. Architectury API is a required dependency and must be installed next to the mod on NeoForge 1.21.1.

Do servers and players both need the mod?

Yes. The server and every player need the mod installed.

Where are beatmaps stored?

Beatmaps, scores and settings are kept in an osutouchgrass folder that is isolated per Minecraft instance.

How large is the first-run extraction?

On first boot the mod extracts about 370 MB of bundled CoreCLR and osu binaries into the osutouchgrass-cache folder.

In the catalog

OSU Touch Grass is one of 29,952 Game mechanics mods on ModsFinder, and one of 12,140 Game mechanics mods for NeoForge. 32,366 mods support Minecraft 1.21.1.

More from caxapexac

All projects

Similar mods

What the author says

Drop.osz files into /osutouchgrass-maps/ to import them. First boot extracts ~370 MB of bundled CoreCLR + osu! binaries to /osutouchgrass-cache/. Game data (beatmaps, scores, settings) are stored at /osutouchgrass/, isolated per Minecraft instance.
caxapexac, on the Modrinth page

Official listing

Owner
caxapexac
Published
2026-05-12
Updated on Modrinth
2026-05-12
Facts verified
2026-10-15

Tags