Rules and Guidelines

July 11, 2011
  1. We test using only the latest official Windows 32 or 64-bit versions from mamedev.org. If you refuse to learn how to compile, you can get pre-compiled u releases here or here. If you compile MAME by yourself, please use the official compiling tools and MinGW set from mamedev.org.
  2. We DO NOT accept any bug reports tested with unofficially tweaked MAME such like MAMEPlus, MiSFiTMAME, MAME++, MAMEUIFX, MAMEUIXT and many others.
    You can post bugs with the official MAMEUI (formerly MAME32) or SDLMAME, and please re-test your bug in the official command-line MAME before reporting to see if it depends on the build or not.
  3. It is known that old Windows OS such as Windows 98 and Me cause an OS-specific problem. Using any of these OS for testing is not recommended at all.
  4. Please check if your issue has already been reported (use the game's zip file name, minus the ".zip"). For example: Afterburner 2 would be referred to as aburner2. Use MAWS to look up zip names and drivers. Additionally, we request that you check the game's driver in the source code before reporting to see if your issue is already documented by the driver author(s).
  5. Make sure that you do not have any corrupted support files: .CFG, .INI, .NV files (in particular). Ensure you can reproduce the bug with a newly created NVRAM file if the game uses one.
  6. Please be specific! Don't just say 'it's wrong', state exactly what is wrong, and how it should appear.
  7. Finding bugs via "cheats" is discouraged. Sometimes cheats can affect the games in ways that aren't immediately apparent. If you can't get to the point in the game where the bug occurs without cheating, please mention it in your bug report.
  8. Comparisons of home console ports of arcade games to the arcade originals are not valid proof that a bug exists.
  9. Please make a save state right near the point of the "problem" and attach it along with your report so that it is easily reproducible. This is a prerequisite when it takes a long time or needs special technique to reproduce it. Please be kind and .ZIP large files before attaching to your report.
  10. We don't accept reports for games with specific flags. When you start MAME, if there is a problem with a particular set, you will be given a screen which lists the problems out that you must type "OK" to. Based on the message(s), posting a new bug is not desired.
    • "THIS GAME DOES NOT WORK PROPERLY" - Do not submit ANY bugs except heavy regression.
    • "THE SOUND EMULATION IS NOT 100% ACCURATE" - Do not submit sound bugs except heavy regression.
    • "THE VIDEO EMULATION IS NOT 100% ACCURATE" - Do not submit video bugs except heavy regression.
    • "THIS GAME LACKS SOUND" - Do not submit sound bugs.
    Nevertheless, any useful information or a report that will help progress of the development, are welcomed.
  11. When a new release comes out, please take a moment to follow-up and check if the issue(s) you reported has(have) been resolved. Not all fixes are documented in the whatsnew.txt.
  12. We accept direct screenshots taken with the F12 key only. Please do not upload filtered images taken with the Print Screen key unless you have a special reason. If you attach these screenshots, please mention the reason on your report.

Game/driver/issue-specific notes

Please check the FAQ page for more informtation.

Close This Window



Documentations: Rules and Guidelines | Legend and Attributes | Tutorial | User Levels and Roles | FAQ | Credit

©1999 - 2011 MAME Testers.