This guide takes you from a clean Gorilla Tag install to a fully working NoLeaves setup. Follow each step in order and you will have leaves removed within minutes of finishing.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/ASTRA228b/NoLeaves.ASTRA-V2/llms.txt
Use this file to discover all available pages before exploring further.
Install BepInEx 5
Download and install BepInEx 5 into your Gorilla Tag directory. Follow the BepInEx installation guide if you haven’t done this yet.After installation, your Gorilla Tag folder should contain:
Download and place the NoLeaves DLL
Download
NoLeaves.ASTRA.dll from the GitHub releases page, then copy it to:Launch Gorilla Tag and check the logs
Start Gorilla Tag through Steam. Once the game has fully loaded, open That line confirms BepInEx found and loaded the plugin. If you see the following line instead, the mod started but could not reach the remote object list:A fetch failure means leaves will not be removed that session. Check your internet connection and make sure no firewall or VPN is blocking the request, then restart the game.Successful operation is silent — if the fetch succeeds, no additional log lines are written and the mod runs in the background automatically.
BepInEx/LogOutput.log in any text editor and look for this line:Play Gorilla Tag
Load into any map. After approximately 2 seconds, NoLeaves fetches the object list and begins its removal loop. Within 5 seconds of that, matching leaf GameObjects are disabled.The mod continues scanning and disabling every 5 seconds for the entire session, so leaves removed after map transitions or respawns will not reappear.
Timing reference
Understanding the mod’s timing helps you know when to expect results:| Event | Delay after game start |
|---|---|
| Mod activates | ~2 seconds |
| First leaf removal pass | ~2–7 seconds |
| Subsequent removal passes | Every 5 seconds |
The 2-second startup delay is intentional. NoLeaves waits for the game world to finish loading before fetching the object list and scanning the scene. If you load in and still see leaves after 10 seconds, check
BepInEx/LogOutput.log for a fetch error.The 5-second polling interval means leaves that appear mid-session — such as after a map change — will be removed within 5 seconds of becoming active. This is by design and not a bug.