Allow using Spindash for trick input

This branch introduces an alternate method of Tricking without needing to release and tap the Accelerate button.

While the Spindash button already worked as a Trick input, you would immediately fastfall barring a frame perfect press. In this branch, you can still fastfall out of a Trick with the Spindash button but you'll have to press the button a second time.

trix

I'm not sure if I need to mess with the DEMOVERSION for this so please advise if this is wanted.

changed the description

added 1 commit

• ca487192 - Don't immediately fastfall when using Spindash for trick input

Compare with previous version

changed title from Don't immediately fastfall when using Spindash for trick input, and don't shut off Kickstart Accel when pressing spindash (resolves #96) to Don't immediately fastfall when using Spindash for trick input

changed the description

Split into a different MR upon Toaster's suggestion.

I would love this if this worked for non-Kickstart Accel control setups too, I have acceleration bound to a trigger and having to depress and press it again for tricks feels cumbersome, and pressing Spindash whilst also holding my acceleration button for tricking would be great if it could work.

added 1 commit

• 39d02f6f - Allow the Spindash button as an alternate trick input

Compare with previous version

changed title from Don't immediately fastfall when using Spindash for trick input to Allow using Spindash for trick input

changed the description

added 1 commit

• 05d78bc8 - Allow the Spindash button as an alternate trick input

Compare with previous version

added 1 commit

• 79df7f63 - Allow the Spindash button as an alternate trick input

Compare with previous version

changed the description

added 1 commit

• dbd980b8 - Allow the Spindash button as an alternate trick input

Compare with previous version

changed the description

added 1 commit

• b65dbfa2 - Allow the Spindash button as an alternate trick input

Compare with previous version

mentioned in issue #156 (closed)

Looks good to me, clever approach that should help with some common gripes.

I don't think any staff ghosts would trigger this behavior (since it was almost always undesirable before), so I don't think a compatlevel is necessary, but I've been wrong about that before. I'd like to get at least one other set of dev eyes on this before merge.

I'm pretty much fine with this diff and it works perfectly in testing. However, since 2.3 will already require a compat level increase I think it'd be smart to use it here too, just for sanity's sake. The relevant demo version will be 0x000D, if you want to sub it in.

Otherwise plusone.