Scooby Docs

RED DEAD REDEMPTION 2 / LUA

Your trail. Your tools.

Build your own interface with Scooby Lua, or start with Vesper: a complete standalone toolbox for your player, horse and travels.

API 2.1.0 Lua54 + LuaJIT

VESPER F7 / LB + DOWN

One window. Five pages.

Player and horse recovery actions, live status, saved travel locations, return travel, weather/time controls and a compact HUD.

Download complete package

MODULES

Make it yours.

Custom outlined buttons, switches, sliders and vector icons. Separate entry point, feature model and view; game actions run in tasks.

Read package instructions

REFERENCE

Check what is available.

4859 typed native bindings from 7130 declarations. Unsupported signatures and reasons remain visible in the downloadable catalog.

Download native catalog

Install Vesper

  1. Use the Scooby host with Lua API 2.1.0 or a compatible newer 2.x version.
  2. Extract the entire Frontier folder into C:\scooby\RDR2\lua. The entry point is Frontier\main.lua; keep its frontier subfolder beside it. Vesper retains the Frontier folder identity to preserve existing saved settings.
  3. Refresh the script list and enable Vesper. Refresh discovers files without stopping running scripts. Reload recreates the selected state.
  4. Press F7 or LB/L1 + D-pad Down. Close the host menu for Vesper controller navigation: LB/RB changes pages, Up/Down selects, A/Cross executes and B/Circle closes.

Choose your runtime

Lua 5.4.6 is the default. The separate LuaJIT 2.1 host uses Lua 5.1 syntax and provides real FFI with compiled traces disabled. Vesper supports both. A LuaJIT host does not parse Lua 5.4 operators or <const> declarations.

Yim compatibility covers selected host conventions and ImGui adapters. GTA scripts still need their game logic ported to RDR2. Read the porting comparison.

Work with game state

Travel uses recorded positions, carries your current horse or driven vehicle, and refuses passenger vehicle moves. Weather/time overrides set by Vesper are cleared during normal script unload. The game and other scripts share these settings.

The shipped tests use fixture game data. Physical controller behavior, game natives, DX12/Vulkan and performance still require acceptance in RDR2 with the exact host build.