SkyHanni icon indicating copy to clipboard operation
SkyHanni copied to clipboard

Backend + Improvement: Forge Key Events

Open rueblimaster opened this issue 1 year ago • 18 comments

What

Before we just used the last Keyboard.Event each tick to read our inputs. Now we're connected to the normal way of doing this. We use forge events, that means on KeyInputEvent we go and check the keyboard for the event, this is done for all events, tho it's controlled by forge. Same principal applies to the mouse.

Tested cases

  • Keyboard keybinds
  • Mouse keybinds
  • Without a mouse plugged in

Changelog Improvements

  • Keybinds now work when pressing multiple keys at the same time. - rueblimaster

Changelog Technical Details

  • Switched over to forge events to power KeyEvents. - rueblimaster

rueblimaster avatar Apr 22 '25 20:04 rueblimaster

3 Detekt Failures were detected:

github-actions[bot] avatar Apr 22 '25 20:04 github-actions[bot]

There is a 0% chance we're touching this file again

I heard David wants to durability test the new system. Go ahead @DavidArthurCole

rueblimaster avatar Apr 25 '25 15:04 rueblimaster

There is a 0% chance we're touching this file again

I heard David wants to durability test the new system. Go ahead @DavidArthurCole

Yeah sure give me til 2040

DavidArthurCole avatar Apr 25 '25 15:04 DavidArthurCole

1 Detekt Failure was detected:

github-actions[bot] avatar Apr 27 '25 14:04 github-actions[bot]

2 Detekt Failures were detected:

github-actions[bot] avatar Apr 27 '25 14:04 github-actions[bot]

This pull request has conflicts with the base branch "beta". Please resolve those so we can test out your changes.

github-actions[bot] avatar Apr 30 '25 20:04 github-actions[bot]

Conflicts have been resolved! 🎉

github-actions[bot] avatar May 13 '25 16:05 github-actions[bot]

1 Detekt Failure was detected:

  • KeyStateManager.kt#L4: Imports begin with a pre-processed comment, make sure to check the order of the imports. If this pre-processing comment is correct you can baseline this error. If you did accidentally change the order of the imports fix them.

github-actions[bot] avatar May 13 '25 16:05 github-actions[bot]

This pull request has conflicts with the base branch "beta". Please resolve those so we can test out your changes.

github-actions[bot] avatar Jun 06 '25 12:06 github-actions[bot]

Conflicts have been resolved! 🎉

github-actions[bot] avatar Jun 07 '25 17:06 github-actions[bot]

This pull request has conflicts with the base branch "beta". Please resolve those so we can test out your changes.

github-actions[bot] avatar Jun 19 '25 11:06 github-actions[bot]

Conflicts have been resolved! 🎉

github-actions[bot] avatar Jun 20 '25 12:06 github-actions[bot]

This pull request has conflicts with the base branch "beta". Please resolve those so we can test out your changes.

github-actions[bot] avatar Jun 21 '25 12:06 github-actions[bot]

Conflicts have been resolved! 🎉

github-actions[bot] avatar Jun 28 '25 15:06 github-actions[bot]

This pull request has conflicts with the base branch "beta". Please resolve those so we can test out your changes.

github-actions[bot] avatar Jul 12 '25 08:07 github-actions[bot]

Conflicts have been resolved! 🎉

github-actions[bot] avatar Aug 02 '25 15:08 github-actions[bot]

1 Detekt Failure

  • ForgeKeyStateManager.kt#L4 PreprocessingImportOrdering: Imports begin with a pre-processed comment, make sure to check the order of the imports. If this pre-processing comment is correct you can baseline this error. If you did accidentally change the order of the imports fix them.

github-actions[bot] avatar Aug 26 '25 12:08 github-actions[bot]

This pull request has conflicts with the base branch "beta". Please resolve those so we can test out your changes.

github-actions[bot] avatar Nov 14 '25 04:11 github-actions[bot]

I think its just easier if we drop 1.8 support instead of worrying about any small issues in the 1.8 keybind system

NopoTheGamer avatar Nov 25 '25 09:11 NopoTheGamer