InputReplayPlugin¶

The InputReplayPlugin is a plugin for the Feather Debugger that lets you record and replay input events (keyboard and mouse) with timestamps. Replay recorded inputs deterministically to reproduce bugs, test sequences, or automate repetitive interactions.

Setup¶

Enable and configure the plugin from feather.config.lua:

return {
  include = { "input-replay" },
  pluginOptions = {
    ["input-replay"] = {
      captureKeys = true,        -- record keypressed/keyreleased
      captureMouse = true,       -- record mousepressed/mousereleased
      captureMouseMove = false,  -- can be noisy
      maxEvents = 10000,
    },
  },
}

Plugin Options¶

🔍 How It Works¶

Recording¶

When you press Record, the plugin records input through Feather's shared callback bus. Each event is stored with:

• Timestamp — seconds elapsed since recording started (high-resolution via socket.gettime or love.timer.getTime)
• Type — which callback fired
• Arguments — all original arguments (key, scancode, isrepeat, x, y, button, etc.)

The original callbacks still execute normally — recording is transparent to the game.

Replaying¶

When you press Replay, the plugin fires the recorded events at their original timestamps through the active LÖVE callbacks. This means:

• Events replay in the exact order they were recorded
• Timing is preserved relative to replay start
• The game receives the same input sequence as during recording
• Replay does not re-record events (avoids feedback loops)

Replay stops automatically when all events have been fired, or manually via the Replay button (toggle).

Save / Load¶

• Save writes the event recording to a JSON file (feather_input_YYYYMMDD_HHMMSS.json) in LÖVE's save directory
• Load reads the most recent saved input file, replacing the current event buffer
• Files are portable — share them with teammates to reproduce bugs

Hook Safety¶

• Recording uses Feather's shared callback bus instead of installing plugin-owned LÖVE callback wrappers.
• During playback, temporary polling shims mirror love.keyboard.isDown, love.mouse.isDown, and mouse position APIs so polling-based controls can observe replayed input.
• Replay does not re-record events, so callback dispatch avoids feedback loops.

🎮 Actions¶

The Feather desktop app shows these controls:

🎮 Usage Examples¶

Basic Workflow¶

return {
  include = { "input-replay" },
}

Then in the Feather desktop app:

1. Press Record and play through a bug reproduction sequence
2. Press Record again to stop
3. Press Replay to replay the exact same inputs
4. Press Save to persist the recording for later

Programmatic Control¶

local plugin = debugger.pluginManager:getPlugin("input-replay")
if plugin then
  local replay = plugin.instance

  -- Start recording from code
  replay:startRecording()

  -- Later, stop and replay
  replay:stopRecording()
  replay:startReplay()
end

Bug Reproduction Workflow¶

1. Record the input sequence that triggers a bug
2. Save the recording
3. Share the JSON file with your team
4. They Load it and Replay to see the exact same bug

Desktop Display¶

The plugin pushes a table with the most recent 200 events (newest first):

The table shows a loading spinner while recording or replaying is active.

Debugger Metadata (getConfig)¶

• Type: input-replay
• Icon: play
• Tab name: Input Replay