> For the complete documentation index, see [llms.txt](https://exobots.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://exobots.gitbook.io/docs/game-stages/alpha/enemies.md).

# Enemies

### **WATCHER-212**

![](/files/5KEgzw9x1bA1odM9KcpB)

This little drone is one to be wary of! It is able to both keep your party buffs in check and increase its own allies stats! This, along with its mid-range attacks, makes it a support-type foe you'll want to destroy rather quick.

### **WATCHDOG-24**

![](/files/uMsnnONjbf3OQG1815Ox)

Watchdog-24 is able to increase its own stats to improve its lethality, shield itself from the player’s attacks and holds heavy ground and distance control. Don't drop your guard when facing one of these!

### **SQU-1D**

![](/files/9QhWxxiHUeNjEyw5yQzq)

An enemy support particularly troublesome when on the back line. SQU-1D is able to heal its allies, deliver area attacks and keep your squad in check through debuffs. Do not forget about it, or it might be able to turn the battle upside down for you!

### **SAT-72**

![](/files/OxFfXbNEsLHtv3etbmJ6)

Sat-72 is a tougher enemy compared to the rest. It holds high damage abilities, is able to penetrate your Exobots defenses, and it will even heal its team! Analyze carefully the enemy team composition to decide if you should or shouldn't focus on this dangerous foe first.

### **SCORPEK-09**

![](/files/p94XcwW6Ycz1wZ55II7Y)

This dangerous unit is fast and deadly, able to increase its CRIT to ensure putting its foes down. Should its high attack power not be enough, it's also able to infect your Exobots to cause decay on them over time. Double check your deck to be able to countermeasure this before engaging into the fight!

### **PEACEMAKER**

![](/files/Nr5Z5R0glZPW3uokWYaj)

Peacemaker is a boss, meaning you will not fight it as often as any other regular foes, but also meaning it's way more powerful than them!

As he is a full exobot, he also is able to use the cards its parts grant him. It would seem it has a lot of parts from Groundsmasher and Stronghold... maybe from some other as well?

### **VIGILANTE**

![](/files/Q4KFlGiLGv53tycyMBFR)

Vigilante is a boss, meaning you will not fight it as often as any other regular foes, but also meaning it's way more powerful than them!

Being another full exobot, he will have use of the deck built by its parts. He looks a lot like Sumrak and Deathbringer... That's a lot of firepower! Be extremely careful when fighting this foe!

### **CUSTODIAN**

![](/files/1iaFSKykeERcH0LfZRPd)

Custodian is a boss, meaning you will not fight it as often as any other regular foes, but also meaning it's way more powerful than them!

This one seems built from more types of Exobots all in one, so he must be way more versatile and hard to predict. Maybe a veteran Raider would be able to identify all its parts and prepare properly for the fight.


---

# 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://exobots.gitbook.io/docs/game-stages/alpha/enemies.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.
