~/docs
manual

The manual, in five moves.

A first run from download to executed script, plus the two failures people hit most. No setup wizard and no prerequisites beyond the game itself.

01

Download and unpack nothing

Grab the current build and drop it in a folder you keep. It is a single executable, so an update simply replaces the file. Windows may verify the build on the first launch, which takes a moment.

tip keep the app out of a temp folder, updates replace it in place.

02

Open Roblox first

Dalta attaches to a running process, so the game has to be open and fully loaded into an experience. Sit on the loading screen and there is nothing to attach to.

03

Press Attach

The status light turns amber while Dalta maps the runtime, then green. If several Roblox windows are open, choose the process id you want. Each window keeps its own connection.

04

Load, read, execute

Open the vault and pick a script, or press New and paste code. The vault fills the editor first so you can read what is about to run. Press Execute and the console prints the result.

tip ctrl+enter executes the active tab without touching the mouse.

05

Read the trace when something fails

A red line in the console names the file, the line and the call. Most failures are a typo or a service that does not exist in that game. Fix the line and execute again without reattaching.

trouble

Two things that go wrong.

Attach is greyed out or finds nothing.

The game is not attached yet. Bring Roblox to the front, wait until you are standing in the experience, then press Refresh in Dalta. If the game launched after Dalta, refresh the process list before attaching.

Scripts run but nothing happens in game.

Check the console for a trace. A script written for a different experience will fail on a missing service or object name. The trace names the line; the fix is usually one property or one service.

manual

Read it once. Never again.

After the first attach the loop is muscle memory: paste, execute, read.

Common questions ->