> For the complete documentation index, see [llms.txt](https://docs.superiormc.cn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.superiormc.cn/elitemobs-wiki/di-san-fang-zhi-chi/worldguard-biao-qian-flag.md).

# WorldGuard 标签（flag）

## elitemob-spawning (allow/deny)

设置精英怪物是否在这个区域内生成。默认情况下精英怪物会在被启用的世界里到处生成，在这时这个标签的作用就是禁止精英怪物在这个区域生成（即标签值为 deny），如果你想让整个世界彻底禁止交易怪物生成，那么我建议你在 ValidWorlds.yml 文件内修改。

## elitemob-only-spawning (allow/deny)

设置是否只有精英怪物才能在指定区域内生成。这不会邮箱精英怪物实际生成的数量，只会阻止非精英怪物生成。

## elitemobs-antiexploit (allow/deny)

设置是否在指定区域内启用 EliteMobs 的反刷怪塔机制。建议在地牢副本中禁用它（将标签设置为 deny）以防止因玩家聚集而无法正常获取掉落物。

## elitemobs-maximum-level

设置精英怪物在指定区域内的最高怪物等级，自定义怪物将会无视这个标签。标签的值只能是整数（例如， `1.5` 是无效值而 `1` 或者 `2` 是有效值）。

## elitemobs-minimum-level

设置精英怪物在指定区域内的最低怪物等级，自定义怪物将会无视这个标签。标签的值只能是整数（例如， `1.5` 是无效值而 `1` 或者 `2` 是有效值）。

## elitemobs-dungeon

设置指定区域内只能生成 EliteMobs 或者其他插件的生物。


---

# 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.superiormc.cn/elitemobs-wiki/di-san-fang-zhi-chi/worldguard-biao-qian-flag.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.