Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/ASTRA228b/Gorilla-Time-V2/llms.txt

Use this file to discover all available pages before exploring further.

Gorilla Time V2 is a small, focused plugin and contributions of all kinds are welcome. Whether you’ve spotted a bug, have an idea for a new time-of-day preset, or want to improve the code directly, this page explains the best way to get involved. The project is intentionally scoped to time and weather features — keeping that focus in mind when contributing helps maintain a clean, predictable codebase.

​
Reporting issues

If the plugin crashes, a time setting doesn’t apply correctly, or the GUI behaves unexpectedly, open an issue on GitHub so it can be tracked and fixed.

Open an issue on GitHub

Report bugs and unexpected behavior on the Gorilla Time V2 issue tracker.
When filing a bug report, include:
  • Your BepInEx version and Gorilla Tag game version
  • A description of what you expected versus what happened
  • The relevant section of BepInEx/LogOutput.log if the plugin produced an error

​
Suggesting features

Feature requests are also tracked as GitHub issues. Open a new issue and apply the feature request label. Describe the feature, why it fits the plugin’s time/weather scope, and any relevant BetterDayNightManager API details you’ve found. The more specific the proposal, the easier it is to evaluate and implement.

​
Submitting code

Code contributions follow the standard GitHub fork-and-pull-request workflow:
1

Fork the repository

Click Fork on the GitHub repository page to create your own copy.
2

Create a branch

Create a descriptive branch off main for your change:
git checkout -b feature/sunrise-preset
3

Make your changes

Edit the source files. See the project structure and building pages linked below for orientation. Keep changes scoped to time or weather functionality — unrelated refactors or new feature categories are better discussed in an issue first.
Test all changes in a private Gorilla Tag room before submitting. Private rooms let you freely cycle through time settings and trigger rain without affecting other players.
4

Open a pull request

Push your branch and open a pull request against main on the upstream repository. Describe what the change does, which issue it addresses (if any), and how you tested it in-game.

​
Code style

The project follows standard C# conventions as used throughout the existing source:
  • PascalCase for types, methods, and properties (TimeSettings, SystemSwitch, StartRain)
  • camelCase for local variables and parameters (manager, timeSettings)
  • Keep methods short and single-purpose — SystemSwitch, StartRain, and StopRain are good examples of the expected granularity
  • Namespace declarations use the file-scoped form (namespace Gorilla_Time.Core;) introduced in C# 10
When in doubt, match the style of the file you’re editing rather than introducing new patterns.

Project structure

Understand every file, namespace, and the plugin lifecycle before diving in.

Building from source

Set up your environment and compile the plugin locally.

Build docs developers (and LLMs) love

Get started for freeTalk to us