> 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/gameplay/actors/spawning-actors.md).

# Spawning actors

To create a new instance of an actor class within the game world at runtime is referred to as a spawning an actor.

An actor can be spawned from anywhere in your code by injecting the World service. The spawnActor function takes 3 parameters.

* **type** (type: `Type<BaseActor>)` - The actor class from which a new instance should be created.
* **position** (type: `THREE.Vector3`) - Where in the scene the actor should initially be positioned. Defaults to {x: 0, y: 0, z: 0}.
* **rotation** (type: `THREE.Euler`) - How the actor should initially be rotated around each axis. Defaults to {x: 0, y: 0, z: 0}.

The code below illustrates how an actor is created and returned.

```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/gameplay/actors/spawning-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.