> For the complete documentation index, see [llms.txt](https://docs.maplestoryn.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maplestoryn.io/msn-101/classes-and-jobs/magician/luminous.md).

# Luminous

<figure><img src="https://812147040-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLn0ozm6YMyUQeaVEuGOu%2Fuploads%2FmCF0NWVkeSJZW9JiXf2z%2FJob%3D%EB%A3%A8%EB%AF%B8%EB%84%88%EC%8A%A4.png?alt=media&amp;token=6f166d4c-eac6-4429-a6ca-047a0c18b246" alt=""><figcaption></figcaption></figure>

#### The ultimate mage torn between two opposing powers

Luminous is a master of light, but in the battle against the Black Mage, he was corrupted by the villain's darkness. As a member of Aurora, an order of light mages, he joined the heroes to stop this order's former master.

Luminous commands a light/dark system, which combines the powers of light and darkness. When both the light and the darkness grow potent enough, he is able to wield a mighty and absolute power. Luminous is set apart by his ability to selectively use magic of the opposing elements of dark and light, receiving buffs and unleashing a variety of attacks with each element.

* Faction : Hero
* Main Stat : INT (Intelligence)
* Weapons Used : Shining Rod


---

# 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://docs.maplestoryn.io/msn-101/classes-and-jobs/magician/luminous.md?ask=<question>&goal=<user_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.