Razor Macro Recorder for UO: Setup, Limits and Tips

VBA & macros · Updated November 22, 2026

Yes. Razor for Ultima Online includes a macro recorder in many classic releases: open its Macros tab, create a macro, start recording, perform supported actions in the game, and stop recording. The result is an ordered sequence of commands, not a perfect recording of every mouse movement or every changing game situation, so review and test it before relying on it.

What Razor Is and What Its Recorder Does

Razor is a third-party assistant commonly used with Ultima Online clients. It provides tools such as hotkeys, item and status displays, and macros that repeat selected in-game actions. Exact features and screen layouts vary between Razor versions and client setups, and some communities use the name Razor for different projects. Check that instructions match the program you installed rather than assuming every version has identical controls.

A macro is best understood as a small, ordered routine. It can tell the client to perform an available action, wait, and then perform another action. The recorder is a way to create some of those commands by carrying out actions while recording. It does not necessarily preserve the full context of what happened: for example, a command that targeted one creature while recording may not automatically choose the right creature during a later run.

Razor records commands that its recorder recognizes. It is not a general-purpose screen recorder, and it does not turn an entire play session into a universally repeatable script. You may need to insert, edit, or remove commands in the macro list after recording.

How to Record a Macro

In a classic Razor interface, the usual workflow is to select the Macros tab, create a new macro, name it, and use the Record control. Carry out the intended actions in the game, then stop recording. Button names and prompts can differ by build, so treat these as general directions rather than a guarantee that every version has the same layout.

  1. Choose a short task with a clear beginning and end. Start with a simple action, not a long routine that depends on several changing targets.
  2. Open Razor’s Macros area and create a new entry. Give it a descriptive name, such as Practice skill or Heal self.
  3. Start recording, switch to the game if needed, and perform the actions at the pace you expect the macro to use.
  4. Stop the recorder, then inspect the resulting command list. Remove accidental actions and check pauses, targeting commands, and the order of steps.
  5. Run the macro once in a safe situation. Watch each step, stop it if it behaves unexpectedly, and adjust it before repeating it.

Keep the first test controlled. A recording can capture an unintended click or action if you interact with the game while it is running. If the recorder does not capture a command you need, use the macro editor’s available command controls instead of assuming the recorder has recorded everything.

What the Recorder Can and Cannot Capture

Depending on the build and action, a recorder may turn supported operations into commands such as using a skill or item, waiting, or issuing a targeting action. Razor’s macro editor may also offer commands that you can add manually. The precise command list is version-dependent; consult the controls in your installed copy rather than following a list written for another release.

Recording is less dependable when an action relies on changing circumstances. A target may move, die, leave range, or cease to be the last target. A spell may require a target prompt, while an item may be in a different container the next time the macro runs. A fixed pause can help with timing, but it cannot guarantee that the game has reached the expected state.

Think of a recorded macro as a repeatable sequence of instructions, not a recording of intent. If you recorded selecting a particular object, the macro may repeat that selection rather than identify the equivalent object in a new situation. Always check whether a command refers to a specific target, a last target, or a general action, where those options are available.

Making Macros More Reliable

Short macros are easier to understand and troubleshoot. Build one task at a time, run it, and only then add another step. If a routine includes a target prompt, include the appropriate targeting action in the correct place. If an action needs time to complete, use a suitable wait or pause command if your version provides one; an overly short delay can cause the next command to arrive before the client is ready.

Useful habits include:

  • Use clear names so you can distinguish similar routines later.
  • Keep commands in the order the game expects them, especially around skills, spells, items, and targets.
  • Remove accidental movement, clicks, or extra commands from the recording.
  • Test with the same client, character, and general conditions in which you plan to use it.
  • Stop the macro and inspect its command list when it behaves differently than expected.

Do not assume a macro will make a task faster just because it automates clicks. A routine that depends on a fixed delay can be less reliable when the server or client responds slowly. A small, well-understood macro is often more useful than a long sequence whose failure point is difficult to locate.

Practical Examples and Limits

A simple practice routine might activate a skill, wait, and repeat it, if the available commands and the rules of the server permit that use. A healing routine might activate the relevant skill and then select the intended target. These examples describe the kind of sequence a player might build; they are not a promise that every Razor version records those exact actions automatically.

Combat routines are more complicated. Targets change, characters move, and actions can depend on range, line of sight, resources, or a response from the server. A recorded target selection that worked once may be inappropriate later. Similarly, a sequence that uses an item can fail if that item is moved or is no longer available. For these reasons, recording is most useful for simple, predictable actions and least useful as a substitute for decisions that need fresh information.

Razor does not make a game action valid merely by automating it. It also does not guarantee that a macro will work on every shard. The server, client, Razor build, and its rules all affect what is possible and permitted.

Razor, Razor Enhanced, and Client Differences

Search results and forum posts may use Razor and Razor Enhanced as though they were interchangeable. They are distinct projects, and their interfaces, macro systems, and supported commands may differ. A guide showing a classic Macros tab and Record button may not describe the scripting or macro tools in another project or release. Confirm the application name and version before using installation, editing, or troubleshooting instructions.

The game client matters too. Razor commonly appears in setups using traditional Ultima Online clients, but compatibility depends on the particular client and Razor release. If the recorder is missing, a control is disabled, or commands do not run, first check whether the installed combination is supported by the project’s current documentation. Do not download an unrelated executable just because a search result uses a similar name.

Macro files and settings may be stored differently depending on the release and how it was installed. If you want to move a macro to another computer, use the version’s own export or file guidance where available, and keep a backup before changing configuration files. A macro made for one command set may not import or behave correctly in another.

Rules, Safety, and Responsible Use

Whether a macro is allowed depends on the server or shard and the action it automates. Rules can differ between official services and private communities, and they may distinguish between ordinary convenience macros, unattended play, automation that affects other players, and prohibited third-party features. Check the current rules for the specific server before recording or running a macro. Do not assume that a feature being available in Razor means its use is permitted.

Be especially careful with unattended repetition. Some servers restrict or prohibit unattended gameplay even when a macro performs only actions that a player could otherwise perform. Other rules may limit particular forms of automation or require a player to remain present. When the policy is unclear, ask the server’s staff or consult its published rules rather than relying on an old forum post.

Use software only from a source you can verify, and avoid tools or scripts that claim to bypass server protections. Keep macros limited to permitted actions, and monitor them when required by the rules. This is both a compliance issue and a practical safeguard against a loop continuing after the game state changes.

Common Problems and Fixes

If pressing Record does not produce a useful macro, confirm that you started recording before performing the action and stopped it afterward. Some actions may not be captured, and a click on Razor itself may not become the in-game command you intended. Try a small test, then inspect the recorded list rather than immediately repeating a long session.

If a macro starts but stops working midway, look for a target prompt, an item that has moved, a missing resource, or a delay that is too short. Test one command at a time to identify where it fails. If a hotkey does not launch the macro, verify the hotkey assignment in the relevant Razor controls and check for a conflict with the game client or another program.

If the Macros tab or recorder control is absent, you may be using a different Razor project, a different build, or a client combination with different support. Consult documentation for the exact version. Reinstalling or changing files without checking compatibility can create a new problem, so back up existing settings first.

Alternatives to Recording

For a very simple repeated action, the game client’s own macro features may be enough, if the client supports the commands you need and the server permits them. Razor’s editor can be more convenient when you want to arrange supported client commands in a sequence. In either case, manual construction can be clearer than recording if the recorder captures unwanted clicks or omits a needed step.

Razor Enhanced and other UO assistants may provide different macro or scripting approaches, but they are not drop-in replacements for classic Razor instructions. Compare compatibility, documentation, and shard rules before switching. Choose the simplest permitted method that works with your client; changing tools will not remove the need to test targets, waits, and changing game conditions.

Frequently Asked Questions

Does Razor have a macro recorder for Ultima Online?
Many classic Razor releases have a recorder in the Macros tab. The exact controls depend on the release, and other projects such as Razor Enhanced may use a different interface or workflow.

Where is the Record button in Razor?
In the classic interface, look in the Macros tab after opening Razor. If you do not see it, check your version and project documentation; instructions for one Razor build may not match another.

Can Razor record every action I perform?
No. It records supported actions as macro commands, not necessarily every mouse movement, screen change, or decision. Review the command list and add or correct steps as needed.

Why does my recorded macro fail when I play it back?
Common causes include a changed target, a missing or moved item, a target prompt, insufficient delay, or a command not supported by that version. Test short sections and check the server’s response.

Are Razor macros allowed on every UO server?
No universal rule applies. Each official service or private shard sets its own policies, including rules about third-party tools and unattended play. Read the current rules for the server you use.

Related

Try it: the Column Letter to Number: aA is 27, XFD is 16,384. Converts both ways.

More in VBA & macros

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.