tutorial:keybinds
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| tutorial:keybinds [2020/12/05 18:07] – formatting majavah | tutorial:keybinds [2025/10/22 16:50] (current) – revert that codeblock cassiancc | ||
|---|---|---|---|
| Line 8: | Line 8: | ||
| Adding a key-bind is easy. You'll need to: | Adding a key-bind is easy. You'll need to: | ||
| + | * open or create a Client [[documentation: | ||
| + | * create a Keybinding.Category object | ||
| * create a KeyBinding object | * create a KeyBinding object | ||
| * react to the key being pressed | * react to the key being pressed | ||
| - | See [[https:// | + | See [[https:// |
| + | |||
| + | ==== Preparing an Entrypoint ==== | ||
| + | |||
| + | If you already have a Client entrypoint created and you are familiar with how it works, you can safely proceed to the [[#Creating your Keybind|next section]]. Otherwise, stick around for a quick overview! | ||
| + | |||
| + | In order to create a Client entrypoint, we'll need to do a couple of different things to let Fabric know that we intend to specify code that only needs to be executed by the physical client [[tutorial: | ||
| + | |||
| + | <code java[enable_line_numbers=" | ||
| + | /* package */ | ||
| + | /* imports */ | ||
| + | |||
| + | public class ExampleClientEntrypoint implements ClientModInitializer { | ||
| + | |||
| + | // The KeyBinding declaration and registration are commonly executed here statically | ||
| + | |||
| + | @Override | ||
| + | public void onInitializeClient() { | ||
| + | |||
| + | // Event registration will be executed inside this method | ||
| + | } | ||
| + | } | ||
| + | </ | ||
| + | |||
| + | So, what are we doing here? Fabric entrypoints for most use cases are designated by implementing a special interface unique to the side or sides that the code in the entrypoint should be run on. For our Client, we simply have our class implement the '' | ||
| ==== Creating your Keybind ==== | ==== Creating your Keybind ==== | ||
| - | Declare | + | Declare these in an area of your preference: |
| <code java> | <code java> | ||
| private static KeyBinding keyBinding; | private static KeyBinding keyBinding; | ||
| + | private static final KeyBinding.Category CATEGORY = KeyBinding.Category.create(Identifier.of(" | ||
| </ | </ | ||
| - | FabricKeyBinding | + | KeyBindingHelper |
| <code java [enable_line_numbers=" | <code java [enable_line_numbers=" | ||
| Line 29: | Line 56: | ||
| InputUtil.Type.KEYSYM, | InputUtil.Type.KEYSYM, | ||
| GLFW.GLFW_KEY_R, | GLFW.GLFW_KEY_R, | ||
| - | | + | |
| + | | ||
| )); | )); | ||
| </ | </ | ||
| - | If you want a sticky key, add '' | + | On versions older than 1.21.9, |
| + | |||
| + | Sticky keys can also be created with '' | ||
| | | ||
| '' | '' | ||
| Line 39: | Line 69: | ||
| ==== Responding to your Keybind ==== | ==== Responding to your Keybind ==== | ||
| - | The code here will print "Key 1 was pressed!" | + | The code here will print "Key 1 was pressed!" |
| + | |||
| + | For versions since 1.19: | ||
| + | <code java> | ||
| + | |||
| + | ClientTickEvents.END_CLIENT_TICK.register(client -> { | ||
| + | while (keyBinding.wasPressed()) { | ||
| + | client.player.sendMessage(Text.literal(" | ||
| + | } | ||
| + | }); | ||
| + | </ | ||
| + | |||
| + | For versions below 1.19: | ||
| <code java> | <code java> | ||
| Line 50: | Line 92: | ||
| </ | </ | ||
| | | ||
| - | Keep note that this is entirely client-side. To have the server respond to a keybind, you'll need to send a custom packet and have the server handle it separately. | + | |
tutorial/keybinds.1607191629.txt.gz · Last modified: 2020/12/05 18:07 by majavah