> For the complete documentation index, see [llms.txt](https://ryanjon2040.gitbook.io/agora-day-night-actor/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ryanjon2040.gitbook.io/agora-day-night-actor/agora-day-night-documentation.md).
# Agora Day Night Documentation
Day night actor is a simple plugin designed to give you a quick way to create day night cycle in your game. This plugin was designed primarily for an RTS game so advanced features like cloud, weather etc are not available yet.
Download and install the plugin from Unreal Marketplace to your desired Unreal Engine. Start a project, and make sure you have the plugin enabled.
If not, enable the plugin and restart.
### PLACING AGORA DAY NIGHT ACTOR
Once the plugin is enabled and Unreal Editor restarted, activate the **Place Actors Panel**.
Inside the **Place Actors** tab, search for Agora Day Night. From the result, drag and drop the actor.
When you select the actor placed in the world, you should see some options on the Details panel where you can enable/disable Day Night cycle, how long (in minutes) should day and night last (individually) and other options.
All options have tooltips added to them, so when in doubt just mouse hover them to see what it does.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://ryanjon2040.gitbook.io/agora-day-night-actor/agora-day-night-documentation.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.