Record a macro with Macro Recording

What Macro Recording does #

Macro Recording records everything you do on one account while you control it in Point of View: walking, sprinting, jumping, sneaking, looking around, mining, placing, using items, menus, chat and commands. You trim the recording like a video, save it, and the Play Recording step repeats it in any macro, tick for tick, the way you played it. Convert to steps turns a recording into ordinary macro steps you can edit one by one instead.

It works on Java and Bedrock accounts. A recording plays on the edition it was recorded on. The playback runs on the account’s backend, so the dashboard does not have to stay open while a macro plays a recording.

Record #

1. Open the recorder

   Open Macros → Recordings and click New recording. Pick the account, which has to be online, choose a countdown (none, 3 or 5 seconds) and click Open recorder.

2. Take control

   The account’s Point of View opens full screen with the recorder bar at the top. Click the view to control the account, exactly as in Point of View. Esc releases the mouse.

3. Start

   Press R or click Record. After the countdown the bar shows a red REC, the time and the number of actions so far.

4. Play

   Do the job the way you want it repeated. Press M or click Marker to mark a moment you want to find again in the editor. Pause stops recording until you click Resume; what you do in between is left out.

5. Stop

   Press R again or click Stop. The recorder closes and the editor opens on the new recording. Discard throws it away instead. Closing the view while recording also stops the recording and opens it in the editor.

Keys in the bar changes the two hotkeys. Pick a letter or a digit the game does not use; game keys such as W, A, S, D, E, Q, F, T and the hotbar digits are refused. Your keys and the countdown are remembered in this browser.

What is recorded #

Only what you do on the recorded account counts. A chat line, a command or an inventory click you send to that account while it records counts too, also from the Chat or Inventory tab, your Discord bot or the API. Macros, tasks, Mouse Control, Anti AFK, Auto Eat, Spawner Sentry, Auto Sell, the Movement tab and your other accounts are never recorded. The world itself is not recorded either: the playback expects the blocks, chests and menus to be where they were when you recorded.

Trim and edit #

The editor opens after every recording and from Edit on a saved one. The line at the top shows the length, the blocks walked, the number of actions, and the edition, version and server it was recorded on.

Edits never change the original recording, so Reset edits always works, even long after you saved. Where you cut a part out, the playback lines the account up again before it continues. A menu click whose menu was cut out is left out of the playback; the editor says how many.

Save and manage recordings #

A new recording is marked Not saved until you click Save recording. The 3 newest unsaved recordings are kept for 7 days, so save the ones you want. Saved recordings count against your plan: the Recordings tab shows how many of your 25 or 100 you use.

A card shows a small map of the path, the length, the blocks walked, the actions, the edition, version and server, the account it was recorded with and the date. In 1 macro tells you a macro uses it. While an account is still recording, a red row at the top offers Open recorder, Stop and edit and Discard.

The Play Recording step #

Add Play Recording from Add step like any other step, or click Create macro on a recording. The step plays the recording at the speed you recorded it and ends when the recording ends.

Taking control of the account in Point of View pauses the playback at once. When you let go, it walks back to the path if you moved the account and continues. While a recording plays, the account’s other automation pauses as it does for Point of View control; macro waits, loops and schedules keep counting. Chat → Console shows the [macro] lines, ending with how far the account was from the recorded path.

Convert to steps #

Convert to steps in the editor makes a new macro called “name steps” out of a saved recording, built from ordinary steps you can edit:

For example, a 73 second run to a supply chest, three shift clicks, a /home and a walk back became 33 steps. Converted steps walk with the pathfinder, so the route and the jumps can differ from the recording; Play Recording repeats it exactly. Save your edits first: the button works on the saved version.

Limits and tips #

A recording stops by itself when the account disconnects, reconnects or is moved to another server by a transfer. What was recorded until then is kept and opens in the editor.

When a playback stops #

The step’s error appears in Chat → Console and under Active Macros, with the time in the recording where it happened.

Two messages are not errors. “waiting until the account’s Point of View controls are free” means someone controls the account in Point of View or another recording is playing; the step starts when it is free. “recorded on 1.21.11, this account plays 1.21.4; movement can differ” is a warning that the versions differ. In the recorder, “The recording stopped” tells you why a recording ended by itself.