> 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/instances-and-bosses/instance-overview.md).
# Instance Overview
*EldenRO instances turn major encounters into isolated trials with their own maps, objectives and encounter state.*
The current instance database registers **five custom MVP trials**, together with two special-purpose instances used by progression and quest content.
Boss trials can be entered in **solo** or **party** mode. Individual mechanics, scaling and encounter rules are documented on each boss page.
{% hint style="info" %}
The five currently registered MVP trials are:
**Golden Thief Bug, Eddga, Moonlight Flower, Phreeoni and Drake.**
{% endhint %}
***
## System Summary
| Property | Current Rule |
| ------------------------- | -------------- |
| **Registered MVP Trials** | 5 |
| **Entry Modes** | Solo / Party |
| **Instance Lifetime** | 30 minutes |
| **Idle Timeout** | 5 minutes |
| **Private Map Copy** | Yes |
| **Manual Destroy** | Enabled |
| **Encounter Mechanics** | Trial-specific |
***
## Registered MVP Trials
| Boss | Instance Name | Entrance |
| -------------------- | ------------------------------- | ---------------------- |
| **Golden Thief Bug** | Golden Thief Bug Trial | `prt_sewb3 (20,185)` |
| **Eddga** | Eddga Lord of the Burning Grove | `pay_fild09 (112,16)` |
| **Moonlight Flower** | Moonlight Flower Trial | `pay_dun03 (127,62)` |
| **Phreeoni** | Phreeoni Trial | `moc_fild17 (198,244)` |
| **Drake** | Drake Trial | `treasure01 (67,179)` |
Each trial creates an isolated version of its encounter map instead of placing every group into the same public battlefield.
***
## Entering a Trial
The current boss trial entrances offer two basic choices:
* Enter alone.
* Enter with a party.
Solo mode creates an instance owned by the character.
Party mode creates an instance associated with the party.
If an instance already exists for the selected owner, the entrance logic attempts to return the player to that active instance instead of creating another one.
{% hint style="warning" %}
Party validation is not identical in every trial.
For example, **Moonlight Flower** explicitly requires the party leader to create or open the party instance.
{% endhint %}
***
## Instance Lifetime
The five registered MVP trials currently use:
> **TimeLimit: 1800 seconds**
This gives each instance a maximum lifetime of:
> **30 minutes**
They also use:
> **IdleTimeOut: 300 seconds**
An instance left idle for **5 minutes** may therefore be destroyed by the instance system.
All five are currently configured as:
> `Destroyable: true`
***
## Encounter Structure
Instances do more than create a private boss room.
Depending on the trial, the encounter may contain:
* Multiple phases.
* Adds or summoned enemies.
* Environmental hazards.
* Safe zones.
* Map objectives.
* Wipe detection.
* Solo or party scaling.
* Encounter-specific recovery or exit logic.
For example:
* **Eddga** uses multiple combat phases and scales according to the number of players.
* **Drake** is structured as a multi-sector fleet encounter with objectives before the final fight.
* **Phreeoni** uses a dedicated encounter controller with several mechanics and phase transitions.
The individual boss guides contain the mechanics that players need for each fight.
***
## Special Instances
The current instance database also contains two EldenRO instances that are not part of the five MVP trials.
### First Grace
> `First Grace`
Map:
> `1@ge_sn`
This instance belongs to EldenRO's introductory progression content.
### Spiral of Frozen Will
> `Spiral of Frozen Will`
Map:
> `1@twig`
This is an individual trial used by the **Arctic Wings** quest line.
{% hint style="info" %}
Not every registered EldenRO instance is an MVP fight.
Quest and introductory content can also use the instance system.
{% endhint %}
***
## Boss Trials vs Open-World MVPs
An MVP being active in EldenRO does not automatically mean that it has a registered custom instance.
This page lists only encounters currently present in the instance database.
Open-world MVPs and other boss content should be documented separately when they do not use the instance system.
***
## Important Rules
* Each trial runs in its own instance map copy.
* Solo and party instances use different ownership modes.
* An existing instance may be re-entered while it remains active.
* The five registered MVP trials have a 30-minute lifetime.
* Idle instances use a 5-minute timeout.
* Encounter mechanics differ between bosses.
* Party restrictions may differ between trials.
* Quest instances should not be treated as MVP trials.
***
## Quick Guide
1. Travel to the entrance of the desired trial.
2. Choose solo or party mode.
3. Complete any trial-specific entry validation.
4. Enter the generated instance.
5. Follow the encounter's objectives and mechanics.
6. Defeat the boss before the instance expires.
7. Review the individual boss guide for detailed mechanics.
***
## Related Guides
Golden Thief Bug
Learn the mechanics of the Golden Thief Bug Trial.
Eddga
Learn the mechanics of the Burning Grove encounter.
Phreeoni
Review the mechanics of the Phreeoni Trial.
Drake
Learn how the Drake fleet encounter works.
---
# 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/instances-and-bosses/instance-overview.md?ask=&goal=
```
`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.