How to get your Gamepad's Unique Extension Triggers

This extension works differently than a lot of other extensions out there, because it dynamically creates triggers based off of what gamepad is plugged in! To view these extensions, go to your bridge.

When you connect your bridge, and connected + press a button on your gamepad, a table of entries is generated for each button and analog stick present on your device. Try clicking some buttons, you'll see their names and values light up!

To use your gamepad within SAMMI, Create a button with an extension trigger that looks like this:

GAMEPAD - Suffix to all "Gamepad Triggers" extension triggers.
{inputname} - The input's generated name shown in the bridge
{action} - The action you wish to capture. Check below for the types of actions you can set for buttons and analog sticks!

Extension Trigger Types & Pull Data

Controller

For the "Controller" category, these are full extension trigger commands and not actions.

CONNECTED

The GAMEPAD CONNECTED extension trigger fires when you connect your gamepad for the first time.

Example usage: GAMEPAD CONNECTED fires the SAMMI button when I connect my Smashbox gamepad.

DISCONNECTED

The GAMEPAD DISCONNECTED extension trigger fires when you disconnect your gamepad. Example usage: GAMEPAD DISCONNECTED fires the SAMMI button when I connect my Smashbox gamepad gets disconnected because I suck at melee.

Buttons

For the "Buttons" Category actions, you have PRESS, and RELEASE.

PRESS

the "PRESS" action fires whenever the button's value goes above zero. this counts as a press, so if "PRESS" is appended after your extension trigger's button name, the SAMMI button will fire on button press.

Example extension trigger: GAMEPAD DPAD_UP PRESS fires the SAMMI button when the d-pad up button is pressed.

RELEASE

The "RELEASE" action fires whenever the button's value sets back to zero. This counts as a release of the button, so if "RELEASE" is appended after your extension trigger's button name, the SAMMI button will fire on button release.

Example extension trigger: GAMEPAD FACE_3 RELEASE fires the SAMMI button when the face_3 (x button for me) button is released.

Button Trigger Pull Data

the "PRESS" and "RELEASE" extension trigger actions, when applied, send over an object of data every time its fired. to access this data, put a Trigger Pull Data command in your SAMMI button. This will retrieve the object. If you leave the Pull Value section empty, all of this data will be returned in an object to SAMMI. otherwise, you only get the one value you specify.

{primary}

Analog Sticks

For the "Analog Sticks" Category actions, you have START, CHANGE, and END.

START

the "START" action fires whenever the analog stick's value goes above zero. If "START" is appended after your extension trigger's analog stick name, the SAMMI button will fire when the stick moves from zero.

Example extension trigger: GAMEPAD LEFT_ANALOG_STICK START fires the SAMMI button when the left analog stick starts moving from its dormant position.

CHANGE

the "CHANGE" action fires whenever the analog stick's value changes. The way this works is tricky but the bread and butter to getting live updates on where your analog stick's position is. This action will not fire if the stick is being held in the same position the next frame, so it won't continue to spam the button if nothing is changing. it only detects change.

Example extension trigger: GAMEPAD LEFT_ANALOG_STICK CHANGE fires the SAMMI button when the left analog stick changes from any value that isn't the same as it's current value.

END

the "END" action fires whenever the analog stick's value returns to zero. If "END" is appended after your extension trigger's analog stick name, the SAMMI button will fire when the stick moves to be zero (dormant).

Example extension trigger: GAMEPAD LEFT_ANALOG_STICK END fires the SAMMI button when the left analog stick returns to it's dormant position, not being used.

Analog Stick Trigger Pull Data

the "START", "END", and "CHANGE" extension trigger actions, when applied to your extension trigger, send over an object of data every time its fired. to access this data, put a Trigger Pull Data command in your SAMMI button. This will retrieve the object. If you leave the Pull Value section empty, all of this data will be returned in an object to SAMMI. otherwise, you only get the one value you specify.

{primary}