Switches that need debounce before and after pull up

[DaveX]

There are different flavors of debouncing depending on which end of the noisy transition you want to trigger on. Perry's code gives the result at BOUNCE_TIMEOUT past the end of the noise, which is the sort of debouncing you appear to want.

It differs from the leading edge detecting that some folks favor.

A collection and comparison of some of both methods are in this thread:

Leading edge debouncing

I've often thought of debouncing like debouncing an interrupt trigger - #3 by mikalhart than most of the examples of debouncing I've seen in Arduino code. In looking at the builtin Arduino Debounce and several of the debounce libraries, the debounced signal triggers after debouncing delay as a minimum pulse width. While the interrupt debouncing form triggers and acts on the first edge and ignores repeated interrupts for a period of time. Here's a Wokwi with the two different methods together…

Your code looks derived closely from this:

Debounce on a Pushbutton | Arduino Documentation

... but extended to use an array of buttons.

As for the LOW vs HIGH, all the methods typically debounce both ends of a signal, and when they are processing the change, they test for HIGH or LOW and make the appropriate changes. Does this part of your code not act on transitions to HIGH properly?

@deronbutler

        // only perform the following code if the new switch state is HIGH
        if (switchState[i] == HIGH) {
          //  Add to score, etc.
        }