[Bug] Issue with Sprint Function When Riding Pokémon in Cobblemon + Controlify

Current Behaviour

Dear Controlify Team,
I hope this message finds you well. I am a player who uses the Controlify mod for Minecraft, and I've encountered a consistent issue that I'd like to report.
When using a controller (handheld gamepad), the sprint function works perfectly when I'm not riding any Pokémon. However, once I mount a Pokémon from the Cobblemon mod, the sprint feature stops working entirely—both the double-tap forward on the left stick and the L3 button press fail to trigger a sprint.
I have followed the troubleshooting steps for Controlify and Cobblemon (resetting configs, rebinding keys, checking stamina/scene restrictions) but the issue persists. I believe this may be a compatibility conflict between the two mods regarding controller input handling while riding.
I would greatly appreciate it if you could look into this bug and provide a fix in a future update. Thank you for your hard work on this amazing mod!
Best regards,

Expected Behaviour

The sprint function should work normally when riding any rideable Pokémon from the Cobblemon mod, just like it does when walking on foot. Both double-tapping the left stick forward and pressing the L3 button should trigger the sprint state

Screenshots

No response

Reproduction Steps

1.Install Minecraft with Controlify and Cobblemon mods.
2.Launch the game and connect a controller.
3.Confirm the sprint function works normally on foot (double-tap left stick forward or press L3).
4.Mount a rideable Pokémon from the Cobblemon mod.
5.Try to trigger sprint using the same controller inputs; observe that sprint does not activate.

Logs

Mod Version

Minecraft 1.21.1+Fabric 0.18.4

Controller

No response

Bluetooth

• Yes

Operating System

Windows

ARM

• Yes

Additional Information

No response

Just to make sure...

• I have made sure I am using the latest version of Controlify for the latest version of Minecraft.
• I have made sure there are no other issues describing the same problem on the issue tracker.