dr-input-manager

Input Manager for DragonRuby GTK Projects

Install

Using smaug

Add the following to your smaug dependencies and run smaug install:

dr-input-manager = { repo = "https://github.com/iMacTia/dr-input-manager" }

Manually

Copy the content of the lib folder in your project and require input_manager.rb

Quick Usage

Let's just take a look at how you can use the InputManager to define logical input actions.

First, we need to make sure InputManager is enabled by calling its .update method in your game's tick:

def tick(args)
  InputManager.update
end

Next, we define an action called "jump" in one of our entities (in this example, the player). The action will be triggered by pressing the space bar on the keyboard (binding):

class Player
  def initialize
    @jump_action = InputManager::Action.new(:jump, bindings: 'keyboard/space')
  end
end

You can poll the action to know if it was triggered in the current frame:

class Player
  # ...

  def tick(args)
    puts 'JUMP!' if @jump_action.triggered?
  end
end

And that's it! Now if you run this on your main file, you will see "JUMP!" printed on the DR console whenever you press the spacebar key.

def tick args
  player ||= Player.new
  InputManager.update
  player.tick # make sure you run your entity's "tick" after `InputManager.update`
end

You can find this quick start example under examples/quick_start, and you can run it from the root of this project with smaug run -p examples/quick_start. (NOTE: You'll first need to copy the lib folder from the project root into the examples/quick_start folder).

If you don't use smaug you can copy the example folder next to your dragonruby executable and run it with that.

Core components

Now that we've seen it in action, let's dive deeper into how the Input Manager works under the hood. The Input Manager introduces 4 core components:

Action - Represents an input event that can be triggered (e.g. Jump, Shoot).
Binding - Represents a button/key/input and it's state.
Interactions - Represents how the player interacts with the inputs.
ActionMap - Groups Actions and their Bindings/Interactions together.

Let's take a closer look at each of them.

Binding

A binding represents a specific button, key or input state that can trigger an action. Examples of this are "space on the keyboard pressed", or "mouse button clicked". They depend on what DragonRuby's args.inputs provides.

You can create a binding by specifying the input device and button/key, plus optionally providing a state/modifier as well.

# Example without a modifier.
# Returns true if up is pressed or held on the directional
binding = Bindings::Simple.new(
  :keyboard, # input device
  :directional_up # key/button
)

State vs Value bindings

Not all inputs are simply on/off states. Some provide a continuous value, like the position of a joystick, the coordinates of the mouse pointer, or touch inputs.

InputManager knows which bindings are value-based versus state-based, and handles them appropriately. Value bindings return the current value of the input on each frame rather than a true/false state. This allows actions to use values for things like camera look based on mouse movement or touch drag gestures.

You can access the value of an action directly:

@jump_action.value

Action

Actions are logical events that represent something the player can trigger through input, like jumping, shooting, attacking, dodging, etc. Each action has a name and one or more Bindings associated with it to define how it can be triggered through input.

jump = InputManager::Action.new(
  :select, # the name of the action
  bindings: 'keyboard/enter;keyboard/w' # the ';'-separated list of bindings that trigger the action
)

Note that bindings can be associated with multiple input devices, allowing for alternate trigger methods. The action will trigger when ANY of its specified bindings are activated on the current frame. This allows for flexible input mapping - for example a "jump" action could be triggered by pressing either the spacebar on the keyboard or the A button on a controller.

jump = InputManager::Action.new(
  :jump, # the name of the action
  bindings: 'keyboard/space;controller/a'
)

Interaction

TBC

ActionMap

ActionMaps group Actions together to create logical sets of input bindings for different contexts. A common use case is having different ActionMaps for different game modes or phases, like a "Gameplay" map with actions for movement, attacking etc and a "Menu" map with actions for navigating menus.

However, more complex games might benefit to have more specific ActionMaps for different contexts, like a game where the player can pilot vehicles or enter combats. In those cases you may want separate ActionMaps for "Explore", "Vehicle", "Combat" modes so bindings don't conflict between contexts.

gameplay_am = InputManager::ActionMap.new('Gameplay').tap |am|
  am.register_action(:jump, bindings: 'keyboard/space')
  am.register_action(:fire, bindings: 'mouse/click')
end

# As we saw in the "Quick Start" above, this is ptional but useful.
InputManager.register_action_map(gameplay_am)

Contribute

Bug reports and pull requests are welcome on GitHub at https://github.com/iMacTia/dr-input-manager.

Required Checks

Before pushing your code and opening a PR, we recommend you run the following checks to avoid our GitHub Actions Workflow to block your contribution.

# Run unit tests
$ smaug run --test spec/spec_helper.rb --no-tick

# Check code style
$ bundle exec rubocop

GryphonClaw/dr-input-manager