> For the complete documentation index, see [llms.txt](https://daddy-studios.gitbook.io/daddy-studios-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daddy-studios.gitbook.io/daddy-studios-docs/maps/abandoned-hospital.md).

# Abandoned Hospital

### 🏚️ Overview

Deep in the heart of the city lies a secret that few know about. The **Abandoned Hospital MLO** by Daddy Studio is a high-stakes medical operation center built for the criminal underworld.

Designed for **Illegal Doctor RP**, this interior provides everything a "shady" medic needs to patch up criminals who can't step foot in a public hospital.

#### 🎭 Key Roleplay Scenarios

* **Secret Surgeries:** Operate on high-profile criminals in a non-listed medical clinic.
* **Illegal Trading:** Use the underground tunnels for smuggling organs or chemical experiments.
* **Gang Hideouts:** A perfect safe house for gangs requiring internal medical facilities.

***

### 🔥 Features at a Glance

* **Gritty Aesthetic:** Every room is filled with customized "abandoned" props (rusty surgical tools, cracked monitors, derelict furniture).
* **Multi-Level Navigation:** Includes main hospital floors and a vast **Underground Tunnel System.**
* **Secret Entrances:** Hidden pathways allowing for stealthy exits and entries.
* **CFX Escrow Secure:** Fully protected and easy to manage via your Keymaster.

***

#### 📖 Contents

* [Installation Guide](/daddy-studios-docs/maps/abandoned-hospital/installation-guide.md)
* [Technical Breakdown & Performance](/daddy-studios-docs/maps/abandoned-hospital/technical-details.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://daddy-studios.gitbook.io/daddy-studios-docs/maps/abandoned-hospital.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.