> For the complete documentation index, see [llms.txt](https://wiki.retrobat.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.retrobat.org/systems-and-emulators/supported-game-systems/game-engines/zelda-classic.md).

# Zelda Classic

<div align="left"><figure><img src="https://990680527-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FexdzL60ZuqPLldz2AYta%2Fuploads%2FfopkhLQfmAq9Y6NtSN2B%2Fimage.png?alt=media&amp;token=b71cd590-5109-4dfe-8958-eb126949683d" alt=""><figcaption></figcaption></figure></div>

Game engine - Released: 1999

{% embed url="<https://zquestclassic.com>" %}

Zelda Classic (now called ZQuest Classic) is a game engine that recreates the original *The Legend of Zelda*. Thousands of fan-made adventures, called **quests**, have been created with it. RetroBat plays these quests.

RetroBat does not ship any quest. Quests can be found on the community sites (for example [PureZC](https://www.purezc.net)).

## At a glance

<table><thead><tr><th width="222.75"></th><th></th></tr></thead><tbody><tr><td><strong>Games folder</strong></td><td><code>roms\zeldaclassic</code></td></tr><tr><td><strong>Extensions</strong></td><td>.qst .zip .7z</td></tr><tr><td><strong>Default emulator</strong></td><td>zquestclassic</td></tr><tr><td><strong>BIOS</strong></td><td>None</td></tr><tr><td><strong>Controller configuration</strong></td><td>Automatic, all emulators (player 1)</td></tr><tr><td><strong>Save states</strong></td><td>libretro cores (zc255)</td></tr><tr><td><strong>RetroAchievements</strong></td><td>No</td></tr><tr><td><strong>Netplay</strong></td><td>No</td></tr></tbody></table>

## Which emulator should I choose?

<table><thead><tr><th width="131">Emulator</th><th width="165.5">Quests supported</th><th width="119">Save states</th><th>Notes</th></tr></thead><tbody><tr><td>zquestclassic</td><td>All versions, up to 2.55</td><td>No</td><td>Official ZQuest Classic player (zplayer). Recommended.</td></tr><tr><td>zc255</td><td>2.55 and older</td><td>Yes</td><td>Libretro core (RetroArch): save states, shaders, rewind. A few quests don't support save states.</td></tr></tbody></table>

If the emulator is not installed yet, RetroBat offers to download it when the first game is launched.

## Bios Information

No BIOS required. The engine data, the soundfont and the sound effects are included in both emulators.

## Adding quests

* Put the `.qst` file directly in `roms\zeldaclassic`, or keep it compressed in a `.zip` or `.7z` archive.
* One quest per archive: RetroBat starts the first `.qst` file found in the archive.
* **Enhanced music**: some quests come with music files. Keep them next to the `.qst` file, or in a folder named after the quest followed by `_music` (for `Adventure.qst`: `Adventure.qst_music`). Inside an archive, keep the same layout: RetroBat extracts the whole archive before starting the quest.

```
roms\zeldaclassic\
   Adventure.qst
   Adventure.qst_music\
   Other Quest.zip
```

## Controls

RetroBat configures the controller of **player 1** automatically. Zelda Classic is a single-player engine.

| RetroBat controller           | zquestclassic     | zc255 (libretro)               |
| ----------------------------- | ----------------- | ------------------------------ |
| D-PAD                         | Move              | Move                           |
| Left analog stick             | Move              | Move (see options)             |
| Bottom button (Xbox A / PS ✕) | A                 | A                              |
| Right button (Xbox B / PS ◯)  | B                 | B                              |
| Left button (Xbox X / PS ▢)   | EX1               | EX1                            |
| Top button (Xbox Y / PS △)    | EX2               | EX2                            |
| START                         | Start (subscreen) | Start (subscreen)              |
| SELECT                        | Map               | Map                            |
| L1                            | L                 | L                              |
| R1                            | R                 | R                              |
| L2                            | EX3               | -                              |
| R2                            | EX4               | Refill (only if cheats are on) |
| Guide / Home                  | Engine menu       | -                              |

A, B and the EX buttons are used by the quest itself: their action depends on the quest (sword, item, extra items...).

The **SWAP A/B AND X/Y** option swaps the face buttons, for example to get a Nintendo-like layout.

{% hint style="info" %}
To set your own controls in **zquestclassic**, disable RetroBat's automatic controller configuration for this system, then configure the controls from the engine menu (**Guide** button or **Esc**).
{% endhint %}

### Hotkeys

| Hotkey         | zquestclassic               | zc255 (libretro)                                         |
| -------------- | --------------------------- | -------------------------------------------------------- |
| HOTKEY + START | Quit and return to RetroBat | Quit and return to RetroBat                              |
| Other hotkeys  | -                           | Standard RetroArch hotkeys (savestates, rewind, menu...) |

With the **zquestclassic** emulator, the keyboard keeps the engine's own keys: arrows = move, `Z` = A, `X` = B, `Enter` = Start, `Space` = Map, `Q` / `W` = L / R, `A` `S` `D` `C` = EX1 to EX4, `Esc` = engine menu.

## Saves

Each quest has its own save, created by the quest itself (save points, continue screen...).

<table><thead><tr><th width="165.75">Emulator</th><th width="328.5">Save location</th><th>Save file named after</th></tr></thead><tbody><tr><td>zquestclassic</td><td><code>saves\zeldaclassic\zquestclassic\</code></td><td>the game file name (<code>Adventure.sav</code>)</td></tr><tr><td>zc255</td><td><code>saves\zeldaclassic\</code></td><td>the quest content (<code>zc255-&#x3C;number>.sav</code>)</td></tr></tbody></table>

{% hint style="warning" %}
The two emulators do not share their saves. Keep using the same emulator for a quest.

With **zquestclassic**, renaming the game file starts a new save. With **zc255**, renaming is safe, but a new version of the quest starts a new save.
{% endhint %}

## Options

The cheat options of the core (invulnerability, walk through walls, R2 refills) are not handled by RetroBat. They can be changed in the RetroArch menu, under **Core Options**.

## Specific system information

* **zquestclassic** is the recommended emulator: it is the official player and reads every quest version.
* **zc255** is useful to get savestates and RetroArch features (shaders, rewind...). A few quests do not support savestates.


---

# 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://wiki.retrobat.org/systems-and-emulators/supported-game-systems/game-engines/zelda-classic.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.
