Find your game folder
In Steam, right-click Beetleball, select Manage, then Browse local files. This opens the folder beside Beetleball.exe.
These packages use MelonLoader and target Windows Beetleball, unless the mod explicitly says Demo.
In Steam, right-click Beetleball, select Manage, then Browse local files. This opens the folder beside Beetleball.exe.
If you already have a working IL2CPP MelonLoader installation, keep it. Otherwise follow Spike’s tutorial and the official MelonLoader instructions. Launch once to generate the game assemblies, then close the game.
Official MelonLoader instructionsChoose a mod and read its dependencies, controls and known issues. Demo builds belong in Beetleball Demo. Beta builds live on the beta testers page.
Unzip the package. Copy the mod DLL from its Mods folder, or the top level, into your game’s Mods folder. Keep the folder structure if the package gives additional instructions. Do not copy source or game libraries into Mods.
Keep one DLL for each mod. ChatCommands Plus and Quill Plus replace their originals. Practice Mod Lite replaces the full Practice Mod. Remove old versions before copying the new one.
Restart Beetleball and look for the mod in the MelonLoader console or MelonLoader/Latest.log. Try practice tools in a hosted private/custom match first. Use the shortcuts on each mod page.
Close the game, confirm the DLL is directly in Mods, remove duplicate versions and check MelonLoader/Latest.log for dependency errors. Make sure the package is for the full game or Demo as appropriate.
Some defaults overlap: Page Up is used by TAS and Evil Cape; Page Down by TAS and Goal Speed Impact; F10 by Split Screen and PooTube Shorts. Change configurable bindings or test the mods separately.
Host a private/custom session. Quill commands are host-run, held-ball resets in Practice Lite require hosting, and TAS requires a solo session without bots.
Close Beetleball and remove that mod’s DLL from Mods. Keep a copy of any saves in UserData before deleting settings.