[freezy]

Pre-Fliptronic WPC definitions list each flipper button twice: as the generic cabinet button and as the matrix switch PinMAME mirrors it into. The converter already gives the input action to the generic button and leaves the matrix copy unmapped, but it also reported a "Duplicate input action" diagnostic for every such copy, so a correct import showed two warnings.

That diagnostic is now skipped when an action has exactly one generic flipper button and one other switch. Anything more ambiguous, such as a second matrix switch with the same flipper role, or two switches both claiming a cabinet action like Start, still produces the diagnostic and leaves the extra switch for manual mapping.

Testing

• PrefersGenericFlipperButtonsOverMatrixCopies now runs with and without a conflicting third right-flipper switch and checks the diagnostic count (0 and 2). Both cases fail on the previous converter.
• New ReportsDuplicateCabinetInputActions covers two Start switches.
• VisualPinball.Engine.PinMAME.Test: 58 passed, 2 skipped (corpus-dependent).

[greptile-apps]

Confidence Score: 5/5

[Low impact] The PR appears safe to merge.

Summary

The converter stops reporting duplicate-input warnings for one generic flipper button paired with one other switch claiming the same action. The generic button keeps the action; the other switch stays available for manual mapping.

• Expected flipper-button copies no longer add duplicate warnings.

_{Reviews (1) · Last reviewed commit: "editor: Don't report matrix copies of fl..." · Reviewed by Greptile}