> For the complete documentation index, see [llms.txt](https://docs.overdare.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overdare.com/korean/development/api-reference/enums/materialtexturetype.md).

# MaterialTextureType

## Overview

MaterialTextureType은 MaterialVariant에서 사용되는 텍스처 맵의 종류를 정의하는 Enum입니다. PBR 렌더링에 사용되는 다양한 텍스처 타입을 분류합니다.

## Items

| Name         | Value | Description                                   |
| ------------ | ----- | --------------------------------------------- |
| ColorMap     | 0     | 색상 맵(알베도 텍스처)입니다. 표면의 기본 색상 정보를 담고 있습니다.      |
| MetalnessMap | 1     | 금속성 맵입니다. 표면이 금속처럼 반사하는 정도를 정의합니다.            |
| NormalMap    | 2     | 노멀 맵입니다. 실제 지오메트리를 변경하지 않고 표면의 미세한 요철을 표현합니다. |
| RoughnessMap | 3     | 거칠기 맵입니다. 표면이 빛을 퍼뜨리는 정도를 정의합니다.              |
| Max          | 4     | 텍스처 타입의 최대 개수를 나타내는 내부 값입니다.                  |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.overdare.com/korean/development/api-reference/enums/materialtexturetype.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
