| Value | Description |
|---|
| Core | Bug related to the emulation core. |
| DIP/Input | Bug related to DIP switches and/or input. |
| Documentation | Bug or issue related to source documentation. |
| Gameplay | Bug related to general gameplay. |
| Graphics | General graphic bug. |
| Interface | Bug related to MAME's interface (File I/O, UI, menu, cheat system etc.) |
| Misc. | Miscellaneous bug. |
| Multisession | Bug related to Multisession. |
| Original Reference | Reference to the original material (PCB, spec, datasheet etc.) |
| Save/Restore | Save/restore related bug. |
| Side-by-side | Side-by-side test result (only for old reports) |
| Sound | General sound bug. |
| Speed | Problem of speed and performance. |
| [Bugs That Aren't Bugs] | Bugs that turned out to be also in the original game. |
| Value | Description |
|---|
| Feature | Feature extension. This is discouraged. Please send your suggestions to Devs directly. |
| Trivial | Issue which doesn't affect work of emulation directly.
- Wrong Input definition (duplicated, missing)
- DIP switch info
- In-game ROM/RAM check error
- MAME's in-game message
etc.
|
| Typo | Typographical error in source code or other texts.
- Typo in source code
- Wrong ROM name
etc.
|
| Minor | Cosmetic issue or minor malfunction. This is proper for old green bug. |
| Major |
Problem which disturbs the gameplay in a significant manner. This is proper for old yellow bug.
- Corrupt graphics
- Sound not working
- Totally broken input
- Widespread malfunction
etc. |
| Critical (Game) |
Bug causes the game to crash or freeze (stop working) but MAME still runs. |
| Critical (MAME) | Bug crashes MAME (either hang or outright crash) |
| Name | Description |
|---|
| Platform | Describes what kind of MAME binary was used for testing. We don't officially accept bugs from SDLMAME or MAMEUI, but if we had a field for them, we could allow them to be logged and easily filter them from the results. Then it would be easier to find bugs that only show up in SDLMAME or MAMEUI and get people to reproduce them on the standard Windows build.
|
| OS | Describes what kind of OS was used for testing.
|
| Build | Describes what kind of MAME build was used for testing. |
| Driver | Game driver name. If the bug is not for a specific game, please leave this field blank. |
| Applicable Sets | Game ZIP names with the problem. This will appear in the head of the summary text. Examples:
- pacman
If pacman and clones share the same issue, just write down the master set name.
- mappy and clones
Of course you can write like this.
- rtype, rtypej, rtypejp, rtypeu
The set family is not so big, this is ok.
- All games in bublbobl.c
You can write in this form but you should remember this will not appear in the result of the search by a set name.
- The King of Fighters 2018 (Asia)
Please lookup the set name in MAWS.
|
| Summary | Brief description of the bug. This text will be used in various places to refer to the bug. |
| 64/32-bit specific | Bug elicited only in a 64-bit build or a 32-bit build. |
| Debug build specific | Bug elicited in a debug build. |
| Possible | Suspected phenomenon to be a bug. Needs confirmation with original. |
| Verified with PCB | Bug validated with PCB and/or original reference. |
