# Was Character Type

![](/files/z16J6sUFG8lQuo331aSI)

## Description

Queries a *DeathContext* from the **On Player Killed** or **On AI Unit Killed** event. Checks if the dead AI unit's *Character Type* and *Species* match the specified input.

## Node Type

Nodes fall into two basic categories: Data and Execution. This node supplies Data for an Execution node.

## Inputs

| Input          | Type           | Required | Description                                         |
| -------------- | -------------- | -------- | --------------------------------------------------- |
| Death Context  | Death Context  | True     | Which Death Context to check if kill was an assist. |
| Character Type | Character Type | True     | Checks if killed unit was this Character Type       |
| Species        | Species        | True     | Checks if killed unit was this Species.             |

## Outputs

| Output                  | Type    | Description                                       |
| ----------------------- | ------- | ------------------------------------------------- |
| Are Same Character Type | Boolean | TRUE if killed Unit matches given Character Type. |
| Are Same Species        | Boolean | TRUE if killed Unit matches given Species.        |

\
\
**Contributors**

AddiCt3d 2CHa0s


---

# Agent Instructions: 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:

```
GET https://wiki.thescriptersguild.com/scripting/nodes/death-context/was-character-type.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.