> For the complete documentation index, see [llms.txt](https://gtfo-modding.gitbook.io/wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gtfo-modding.gitbook.io/wiki/reference/nested-types/activeenemywavedata.md).

# ActiveEnemyWaveData

Blood door settings.

## Fields

{% hint style="warning" %}
You should always make sure the group type you're spawning is set to "Hunter", otherwise the enemies will not spawn aggressive.
{% endhint %}

### HasActiveEnemyWave - Boolean

Whether the gate to the zone is a blood door.

### EnemyGroupInfrontOfDoor - UInt32 ([EnemyGroupDataBlock](/wiki/reference/datablocks/main/enemygroup.md))

Enemy group to spawn right in front of the door.

### EnemyGroupInArea - UInt32 ([EnemyGroupDataBlock](/wiki/reference/datablocks/main/enemygroup.md))

Enemy group to spawn anywhere in the area.

By the time the door opens, most enemies will have reached the door.

### EnemyGroupsInArea - Int32

Count of EnemyGroupInArea instances to spawn.


---

# 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://gtfo-modding.gitbook.io/wiki/reference/nested-types/activeenemywavedata.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.