> 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/arcade/dice.md).
# Dice
Discrete Integrated Circuit Emulator
Arcade
List of Dice games:
{% embed url="" %}
## Information
Emulators
Libretro: DICE
File folder
📂 roms \ 📂 dice
File extension
.zip .dmy
## System Features
Retroachievements
Netplay
Controller autoconfig
lr-dice : NO
lr-dice : NO
lr-dice : YES
## Bios Information
No BIOS required to play DICE games.
## Controls
### Arcade stick mapping
Mapping can be found in the [notice](http://retrobat.ovh/notice/notice.pdf).
### Controller mapping
| Retrobat Button | Arcade Key |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- |
| START | START |
| SELECT | COIN |
| Left analog stick | Stick |
| Right analog stick | |
| D-PAD | Stick |
|  | 3 |
|  | 1 |
|  | 2 |
|  | |
| L1 | Dollar |
| R1 | |
| L2 | |
| R2 | |
| L3 | |
| R3 | |
## Specific system information
### Adding DICE games
Some games use zipped ROMs and launch similarly to MAME or FBNeo --- filename is important, [see table](https://docs.libretro.com/library/dice/#compatibility).
Some games (pong, breakout, pinpong, etc) do not have any ROM on the board at all. For these, copy the dummy launcher file from [dummy\_files](https://github.com/mittonk/dice-libretro/tree/main/dummy_files) to your ROM folder.
---
# 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/arcade/dice.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.
