> 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/others/reminiscence.md).
# REminiscence
Game engine to play Flashback game.
{% embed url="" %}
## Information
Emulators
Libretro: reminiscence
File folder
📂 roms \ 📂 reminiscence
File extension
.rem
## BIOS
No BIOS required.
## Controls
Retrobat
Reminiscence
D-PAD
Directions
Left analog stick
Directions
START
SELECT
Inventory
Draw/Holster
Use
Action
## System Features
### Game files organization
REminiscence requires original Flashback game files from Delphine Software to work.
DOS, PC-CD, Amiga, Macintosh, or [GOG ](https://www.gog.com/game/flashback)or [STEAM](https://store.steampowered.com/app/961620/Flashback/) versions can be used.
Inside the `roms\reminiscence` folder, create a folder named `Flashback`.
Inside this folder, copy all the files that can be found in the `Flashback_Data\StreamingAssets\data` folder of the Flashback source game:
The game can be launched, but some voices and musics will not work. To add them, one can get the audio files from Raphaël Gesqua and copy them inside the `Flashback` folder:
Finally, for RetroBat to see the game and be able to launch it, create an empty text file inside the `roms\reminiscence` folder, and rename the file to `Flashback.rem` (.rem file extension).
---
# 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/others/reminiscence.md?ask=&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.
