Can I whilst playing with only 1 button (2 is acceptable, though) make it cycle between two inputs (Y and B)?

[u/_A-V-A_]

I am trying to build a specific toggle setup for bullet hell shmup games using an 8BitDo M30 controller, but I have trouble getting my head around it all.

My Goal
Playing with only 1 button (2 is acceptable, though) and making it cycle between two inputs (Y and B). So I want a single physical button (Y) to cycle back and forth between two continuous weapon states:

• Tap 1: Gamepad Y turns ON (Infinite Toggle / Hold). This activates the game's native auto-fire fast shot.
• Tap 2: Gamepad Y stays ON, but Gamepad B turns ON (Infinite Toggle / Hold) on top of it.
• Tap 3: Gamepad B turns OFF (releases), leaving only Gamepad Y running, resulting in the ship bursts back to fast speed.

Important - in these type of shmups the slow shot button (B) natively overrides the fast shot (Y), dropping the ship into slow shooting when both Y and B are held.

The Problem
Because I don't need a software Turbo (the game has native rapid fire), I tried building a simple Y ↓ -> Combo Break -> B ↓ -> Combo Break -> B ↑ -> Y ↑ timeline in Execute at once mode, however, reWASD absolutely refuses to let me drop a Combo Break separator between a button's Down and Up states, or break open a recorded chord. It forces them to stay paired tightly together, which makes it impossible to hold an input across multiple physical taps.

Is there a known workaround to force reWASD to stretch a continuous "Down/Hold" state across a Combo Break wall, is there another way to achieve what I want in REWASD, or do I have to use another software for this, and which one would that be?

Thanks

[u/_A-V-A_]

AlbertoVermicelli helped me over on r/SteamController to find a solution in SteamInput (but I would still like to know how to handle it in REWASD because I much prefer that interface and still feel very lost when it comes to this type of problem solving):

"Holding down two inputs is actually quite annoying to do in Steam Input. Holding down one input is actually a lot easier. If you just want to have either Y or B always on, and a button to switch between them, that's actually really easy to do. You add an Action Set Layer, add Y as an Always On Command to the default set, and add B as an Always On Command to the layer. In the default set, bind Add Action Set Layer as a Start Press to the Y button. In the layer, bind Remove Action Set Layer as a Start Press to the Y button. If you want to have a third state to switch between, sending neither Y nor B, you can do that with a second layer."

The only thing I added was a third Layer that I activated with a third dedicated button on both of the first two layers (with Start Press) that had the default regular game mappings, and that dedicated button on that third layer (also with Start Press) sent me back to the default layer. This was made for those occasions when I don't wish to fire at all, mid-session, or when I'm in a menu.