Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
06220 DIP/Input Minor Always May 24, 2016, 22:53 May 25, 2016, 05:04
Tester Ashura-X View Status Public Platform MAME (Self-compiled)
Assigned To Resolution No change required OS Windows XP
Status [?] Closed Driver cv1k.cpp
Version 0.173 Fixed in Version Build Normal
Summary 06220: pinkswts,pinkswtsa,pinkswtsb,pinkswtsx,ibarablk,ibarablka: Inserting coins issue - Coin error or reset screen!
Description Those sets above have coin input issue when trepassing more than 9 credits and pressing the input coin repeatedly.
On Pink Sweets after 9 credits the game give me a coin error screen and on Ibara it does kick you to reset game screen!
Not tried on other games from that driver btw...
Steps To Reproduce
Additional Information
Regression Version
Affected Sets / Systems pinkswts,pinkswtsa,pinkswtsb,pinkswtsx,ibarablk,ibarablka
Attached Files
png file icon 0000.png (1,729 bytes) May 24, 2016, 22:53 Uploaded by Ashura-X
There are no relationsihp linked to this issue.
User avatar
May 25, 2016, 04:48
This isn't a bug.
You can cause it to happen by holding the credit button/trigger down for a short period of time without letting up. This is expected behavior in that the game is simply telling you there is a problem with the coin trigger and needs to be examined before it can be reset. There are a number of boardsets which are programmed to do this by either holding a credit switch down or by holding one '5' while clicking another '6'. You'll get messages ranged from "Coin Error" to "Coin Mech Jammed"
User avatar
May 25, 2016, 04:56
edited on: May 25, 2016, 04:57
The original hardware didn't let you physically insert coins that quickly. If any coin inputs happened that quickly, it'd indicate a problem with the coin mech or someone trying to cheat the system, so the game would error out. Definitely not a bug.

Something to add to the FAQ, I think.

User avatar
May 25, 2016, 05:03
Sadly, we have to set you to Viewer. Try to work out bugs a bit first and make sure they are not user error or, in this case, expected behavior.