Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
06345 Gameplay Minor Always Aug 8, 2016, 22:01 Aug 12, 2016, 15:11
Tester izius View Status Public Platform MAME (Official Binary)
Assigned To Resolution Open OS Windows XP
Status [?] Confirmed Driver seta.cpp
Version 0.176 Fixed in Version Build Normal
Summary 06345: gundhara, gundharac: [possible] Player duplicated and wrong palette on a specific occurrence
Description In level 3, if you have the armor and get bitten by the dragon (level boss), the armor absorbs the hit and the player survives, but the game still counts it as a death and spawns another player in the playfield (messing up the palette), or triggers the name entry/continue sequence if there are no lives left.
Steps To Reproduce Get the armor at the beginning of level 3, then keep it (avoid getting hit) until you reach the boss. Defeat its statue form; when the dragon appears shoot off its arms and avoid its lightnings. Eventually it'll come closer, trying to bite you; get hit by that attack.
Additional Information The extra player persists in the next level, reappearing at the top of the screen, until you get a game over, or until you reach the end of that section. Just before entering the lab (halfway level 4), the game freeze for an instant and resets to the title screen.

I recorded 2 inps, showing the game behaviour if there are lives left or not when the bug is triggered.

Most likely it happens also on the PCB.
Flags Possible
Regression Version
Affected Sets / Systems gundhara, gundharac
Attached Files
zip file icon gundhara (3 lives left).zip (131,109 bytes) Aug 8, 2016, 22:01 Uploaded by izius
zip file icon gundharac (no lives left).zip (117,733 bytes) Aug 8, 2016, 22:01 Uploaded by izius
png file icon 0000.png (33,223 bytes) Aug 8, 2016, 22:03 Uploaded by izius
2x player and wrong palette
png file icon 0001.png (31,070 bytes) Aug 8, 2016, 22:04 Uploaded by izius
Continue sequence with alive player
There are no relationsihp linked to this issue.
User avatar
Senior Tester
Aug 9, 2016, 08:29
I'd agree with this most likely happening on the PCB too, looks like something the developer didn't consider.