> For the complete documentation index, see [llms.txt](https://eldenro.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://eldenro.gitbook.io/wiki/core-systems/respawn-system.md).

# Respawn System

<figure><img src="https://634904776-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcjHPIjSD61wf6lo7q3QV%2Fuploads%2F4TogfQcp3hX7UdCYzvR8%2Frespawn_system.webp?alt=media&amp;token=bfe88bfd-dd6a-40b6-bd41-c555f08fbd78" alt=""><figcaption></figcaption></figure>

## Respawn System

*Grace remembers the last flame that welcomed you.*

EldenRO uses the **latest Bonfire you rested at** as your normal **Site of Grace** and save point.

After a normal defeat, returning to your save point brings the character back near that Bonfire. Special multiplayer or instance rules may temporarily use a different return flow.

{% hint style="info" %}
**Resting changes your Site of Grace.**

Simply discovering or traveling to a Bonfire should not be treated as confirmation that your save point changed.
{% endhint %}

***

## System Summary

| Property                 | Current Rule                  |
| ------------------------ | ----------------------------- |
| **Normal Respawn Point** | Latest rested Bonfire         |
| **Stored Position**      | Near the Bonfire              |
| **Default Offset**       | 2 cells                       |
| **Resting Restores**     | HP, SP and Flask charges      |
| **Previous Grace**       | Replaced by the newest one    |
| **Player Tomb**          | Remains at the death location |
| **Special Content**      | May use separate return rules |

***

## Setting Your Site of Grace

Interact with the Bonfire you want to use as your normal return point.

When resting, EldenRO:

1. Records the Bonfire's map.
2. Stores a position **2 cells away** from the Bonfire by default.
3. Replaces the previous normal save point.
4. Restores HP and SP.
5. Refills the allocated Crimson and Cerulean Flask charges.

The confirmation message is:

> `You rested at the Site of Grace.`

{% hint style="success" %}
When this message appears, that Bonfire is your new normal return point.
{% endhint %}

***

## After Death

During normal open-world play:

1. Death-related systems are processed.
2. A Player Tomb may be created when the death is eligible.
3. The character returns through the normal save-point system.
4. The latest Site of Grace is used as the normal destination.

Returning does **not** move or recover a Player Tomb.

***

## Site of Grace vs Player Tomb

| System             | Purpose                                         |
| ------------------ | ----------------------------------------------- |
| **Site of Grace**  | Determines the normal return point              |
| **Player Tomb**    | Stores eligible lost Zeny at the death location |
| **Bonfire Travel** | Helps return toward discovered locations        |

Example:

* You rest at Bonfire A.
* You later die at location B.
* Your normal return point remains near Bonfire A.
* Your Player Tomb remains at location B.

{% hint style="warning" %}
Changing your Site of Grace does not move an existing Player Tomb.

The tomb stays where the eligible death occurred.
{% endhint %}

***

## Changing Your Respawn Point

Resting at another Bonfire immediately replaces the previous normal save point.

Only the latest recorded Site of Grace is used by the standard save-point return flow.

Fast travel and Bonfire discovery are separate systems. After reaching a Bonfire, rest there when you want it to become your new Site of Grace.

***

## Recovery at a Bonfire

The current Bonfire interaction restores:

* **100% HP**
* **100% SP**
* Crimson Flask charges up to the current Crimson allocation.
* Cerulean Flask charges up to the current Cerulean allocation.

Resting does not remove Flask upgrades, maximum Flask capacity or the current Crimson/Cerulean allocation.

***

## Special Return Rules

The Site of Grace is the normal save point, but temporary systems can apply their own return behavior.

Examples include:

* **Player Summoning** — a Helper may return to the position recorded before being summoned.
* **Invasions** — the Invader may return to the position recorded before entering the Host's world.
* **Instances** — scripted encounters may control their own death or exit behavior.

These temporary rules do not necessarily replace the character's normal Site of Grace.

***

## Quick Guide

1. Reach the Bonfire you want as your checkpoint.
2. Rest at it.
3. Confirm `You rested at the Site of Grace.`
4. Continue your journey.
5. After a normal defeat, return through the latest Grace.
6. Recover any Player Tomb separately.

{% hint style="success" %}
**Grace controls where you return.**

**The Player Tomb controls what remains behind.**
{% endhint %}

***

## Related Guides

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Bonfires</strong></td><td>Learn how Bonfires are discovered, used and connected through travel.</td><td></td></tr><tr><td><strong>Death and Player Tombs</strong></td><td>Understand what remains at the location of an eligible death.</td><td></td></tr><tr><td><strong>Player Summoning</strong></td><td>Review temporary Helper return rules during cooperative sessions.</td><td></td></tr></tbody></table>


---

# 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://eldenro.gitbook.io/wiki/core-systems/respawn-system.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.
