> For the complete documentation index, see [llms.txt](https://docs.hology.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hology.app/zh-tw/gameplay/yan-yuan-actors/sheng-cheng-actors.md).

# 生成 Actors

在遊戲運行時在遊戲世界中創建一個 actor 類的新實例被稱為「生成（spawning）」一個 actor。

您可以通過注入 World 服務在代碼的任何地方生成一個 actor。`spawnActor` 函數接受 3 個參數：

* **type** (類型：`Type<BaseActor>)`- 應該從中創建新實例的 actor 類。
* **position** (類型：`THREE.Vector3`) - Actor 在場景中的初始位置。預設值：{x: 0, y: 0, z: 0}.&#x20;
* **rotation** (類型： `THREE.Euler`) - actor 在每個軸上的初始旋轉角度。 預設值： {x: 0, y: 0, z: 0}.&#x20;

以下代碼示例說明了如何創建並返回一個 actor：

```typescript
import { Service, GameInstance, inject, World } from "@hology/core/gameplay"
import ExampleActor from "./actors/example-actor"

@Service()
class Game extends GameInstance {
  private world = inject(World)
  
  async onStart() {
    const actor = await this.world.spawnActor(ExampleActor)
  }
}
```


---

# 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.hology.app/zh-tw/gameplay/yan-yuan-actors/sheng-cheng-actors.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.