> For the complete documentation index, see [llms.txt](https://morphic.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://morphic.com/docs/id/desain-game/train-a-style-model.md).

# Latih Model Gaya

Berikut tutorial singkat tentang cara melatih model gaya gaming di Morphic:

{% embed url="<https://youtu.be/F0CUOZuTesw>" %}

1. Buka dashboard Morphic Anda
2. Klik "Model" dari panel kiri
3. Klik tombol “+ Model” di pojok kanan atas
4. Pilih “Model Gaya”
5. Berikan nama pada model Anda (Anda akan menggunakannya saat melakukan prompting)
6. Unggah 2–150 gambar referensi dengan gaya yang Anda inginkan
7. Klik “Mulai Pelatihan” untuk memulai

Setelah Style Model Anda selesai dilatih, Anda akan mendapatkan email dan notifikasi di dashboard Morphic Anda. Untuk menggunakannya, buka file apa pun dan pilih Style Model Anda saat melakukan prompting, lalu hasilnya akan otomatis mencerminkan gaya yang Anda latih.

Begitulah cara Anda melatih Style Model di Morphic.

***

Jika Anda mengalami kendala atau memiliki pertanyaan, jangan ragu untuk menghubungi kami. Kami dengan senang hati akan membantu. Tulis kepada kami di [**support@morphic.com**](mailto:support@morphic.com)**.**


---

# 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://morphic.com/docs/id/desain-game/train-a-style-model.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.