isXander / isXander/Controlify

[Bug] Once controller has been used in a game session, keyboard has sprint-toggle functionality

Open
#401 4 comments 0 reactions 1 assignee View on GitHub

@isXander is already working on this.

Since Aug 18, 2024.

bug
Dominant language
Java
Stars
341
Forks
97
Avg merge
1h
Merged PRs (30d)
1

Description

Current Behaviour

I play with a controller for a little bit, making use of pressing down the left thumbstick to turn on and off sprint, which will automatically run when i move forward or not depending on its status. Then when I try to play with keyboard, this sprint functionality still persists where I press my sprint key, and it will automatically sprint when I move forward, and pressing it again turns that off. To my testing, this can only be removed when the game is restarted.

Expected Behaviour

When I am no longer using the controller, pressing the sprint key should not have the same toggle functionality as pressing the left thumbstick (default) while the controller was in use.

Screenshots

No response

Reproduction Steps
  1. Open minecraft and connect and use a controller. At least one controller input should do, such that button press instructions come up.
  2. Return to using keyboard. Disconnecting controller is not necessary.
  3. Pressing your keyboard sprint key will now have the same toggle effect as it does when using controller, regardless of how the vanilla sprint behavior is set/changed.
Logs

No response

Mod Version

2.0.0-beta.14+1.21-fabric

Controller

Xbox wireless controller. Can't find exact product page.

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.