> For the complete documentation index, see [llms.txt](https://wiki.thescriptersguild.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.thescriptersguild.com/knowledge/scripting/guides-and-info/patterns/how-to-kill-players-with-scripts.md).

# How to kill Players With Scripts

## How to kill Players With Scripts

Use the `Damage Player` node, making sure to apply enough damage to kill the player. This can be reliably achieved by reading the players health/shields, adding them together, multiplying that by 2 (to smooth any edge cases), and then applying that value as damage.

Alternatively, the `Delete Object` node will delete the player's biped and register a death for them, putting them into the respawning state and causing them to respawn if their spawns are not blocked. As this deletes their biped, their ragdoll will disappear, jarringly.

**Contributors**

Captain Punch


---

# 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://wiki.thescriptersguild.com/knowledge/scripting/guides-and-info/patterns/how-to-kill-players-with-scripts.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.