Commands

ACTBASEPOINT command in AutoCAD : Inserts a base point or base point prompt in an action macro

This guide explains in clear, practical steps how to use the ACTBASEPOINT token in AutoCAD Action Recorder macros. You’ll learn what it does, how to insert it when recording or editing action macros, troubleshooting tips when it doesn’t behave as expected, alternative workflows, and best practices to create reliable macros.

What is the ACTBASEPOINT command / token?

ACTBASEPOINT is not a standalone drawing command but a token used inside AutoCAD Action Recorder macros. It inserts a base point or a base-point prompt into an action macro so that, when the macro is replayed, AutoCAD prompts the user to pick a base point (for example, when moving, rotating, or scaling objects).

Key ideas:

  • It is used inside an Action Macro created with the Action Recorder (Manage tab > Action Recorder).
  • It tells the macro to pause and request a base point from the user when the macro is replayed.
  • Typical use: create a generic macro (e.g., Move by reference, Rotate around a chosen point) that requires a user-selected base point at playback.

When and why you use ACTBASEPOINT

Use ACTBASEPOINT when you want your recorded macro to:

  • Prompt the user to pick a base point during playback, instead of hardcoding a specific coordinate.
  • Make the macro flexible across drawings and situations (relative placement).
  • Record actions that rely on a user-supplied origin point (move with reference, rotate around a picked point, scale from a chosen point).
Read Also:  ARRAYPATH command in AutoCAD : Evenly distributes object copies along a path or a portion of a path

Examples:

  • A macro that repeatedly moves selected blocks by a relative amount from a user-selected reference point.
  • A macro that rotates components around a user-selected pivot.

How to use ACTBASEPOINT — Step by step

Below are two common ways to incorporate ACTBASEPOINT: during recording and by editing an action macro.

A — Create macro by recording (recommended for beginners)

  1. Open the Action Recorder: Manage tab → Action Recorder → Record.
  2. Click Record. Give the action macro a name and (optional) description.
  3. Perform the commands you want to record:
    • For example, start the MOVE command, select objects, and when it asks for the base point, pick the point. The Action Recorder will capture the base point event as a token.
  4. Continue with the remaining prompts (e.g., displacement or second point), then finish the command.
  5. Click Stop on the Action Recorder. The recorder stores the recorded steps; the base point you picked will generally appear in the macro as a base-point token (ACTBASEPOINT or similar).
  6. Test playback on a sample object using Play (Action Recorder). When the macro reaches the base-point token, it should prompt you to pick a base point if you recorded it as a prompt rather than a hard-coded coordinate.

B — Edit an existing action macro to add a base-point prompt

  1. Open Action Recorder and locate your macro.
  2. Click Edit (Action Macro Editor).
  3. In the macro editor, find the step where the command needs a base point.
  4. Replace or insert the base-point token (often shown as a parameter or prompt item). The editor displays recorded parameters (coordinates, prompts). Choose the parameter type that forces user input (prompt) rather than a fixed coordinate.
  5. Save the macro and test playback: it should pause and request the base point on replay.

Notes:

  • If you recorded a specific coordinate, the macro may always use that coordinate. To make it prompt on replay, ensure the recorded parameter is set as a Prompt token rather than a fixed value.
  • You can combine ACTBASEPOINT prompts with other prompts (like second point or angle prompts) to create flexible workflows.

Common problems and how to fix them

Problem: Macro does not prompt for a base point (uses the original recorded coordinate)

  • Fix: Edit the action macro and change the recorded coordinate parameter to a Prompt parameter (so it becomes a base-point prompt token). Re-record the step, picking a generic placeholder or choose “Prompt” in the editor.
Read Also:  ADCCLOSE command in AutoCAD : Closes DesignCenter

Problem: Action macro fails or skips the step when replaying

  • Fixes to try:
    • Ensure you are running the macro in a compatible AutoCAD version and with the same toolset.
    • Verify required commands used by the macro are available (some custom or third-party commands may not be recorded correctly).
    • Check that PICKFIRST, OSNAP, and relevant system variables are set appropriately for the macro to function.
    • Confirm the macro wasn’t corrupted when saved—re-record the critical steps.
    • Make sure the macro is not set to use absolute coordinates when relative selection is intended.

Problem: Base point prompt uses wrong Coordinate system (UCS vs WCS)

  • Fix: Lock or explicitly set the UCS before recording, or include a UCS change as part of the macro. In the macro editor, ensure the coordinate tokens reflect the intended coordinate system.

Problem: OSNAP not working during macro playback (cannot pick accurate base point)

  • Fix: Enable the appropriate object snaps before playback or record the macro to include OSNAP settings as part of the actions. You can also instruct users to enable OSNAP when prompted.

Problem: Macro works on one drawing but not another

  • Fix: Check layer, block, or object availability and ensure objects are not on frozen/locked layers. Ensure the macro’s expected entities exist or modify the macro to be more generic.

Alternative methods to ACTBASEPOINT

If Action Recorder or ACTBASEPOINT doesn’t fit your needs, consider these alternatives:

  • Use the BASE command (or -BASE) to set the drawing base point for positioning blocks and exports. Note: this is different from prompting for a base point during a Move/Rotate action.
  • Create a script (.scr) file that includes coordinate placeholders, and manually edit coordinates before running. Scripts are less interactive but useful for repeatable exact operations.
  • Use AutoLISP or VBA/.NET for more advanced, interactive macros. These allow prompting for points, validating input, and robust error handling.
  • Use the built-in COPY/MOVE commands with Reference option during a recorded macro to simulate a base-point operation without tokens.
  • Create a custom command in CUI (Customize user interface) that runs a macro sequence and assign a keyboard shortcut or ribbon button.
Read Also:  3DALIGN command in AutoCAD : Aligns objects with other objects in 2D and 3D

Tips and best practices

  • Always test macros on simple sample objects before using them in production drawings.
  • Use descriptive names and descriptions for macros so users know when a base-point prompt will occur.
  • If your macro requires user selection or precision, include prompts or instructions within the macro description.
  • Manage Coordinate systems: set or lock the UCS if the macro depends on a particular orientation.
  • Save frequently used macros to an Action Recorder library and back them up.
  • When sharing macros across teams, document any required system variable states (OSNAP, PICKFIRST, UCS).
  • For repeatable keyboard triggers, create a custom command in CUI or a keyboard shortcut that calls the macro—this makes it easier for other users to run.
  • When recording, intentionally record a prompt (don’t click exact coordinates if you want the user to supply them later).

Frequently Asked Questions

What is the difference between ACTBASEPOINT and the BASE command?

ACTBASEPOINT is a token inside an Action Recorder macro that prompts the user for a base point during macro playback. The BASE command sets the drawing’s insertion base point (a property of the drawing used for block insertion and some exports). They serve different purposes.

How do I make a recorded macro always prompt for a base point on replay?

Edit the macro in the Action Macro Editor and change the recorded coordinate step to a Prompt parameter (base-point token) rather than a fixed coordinate. Alternatively, re-record the step but don’t complete it with a specific coordinate — record it as a prompt.

Can I assign a keyboard shortcut to run an action macro that uses ACTBASEPOINT?

Yes. Use the CUI (Customize User Interface) editor: create a new custom command, paste the macro or reference to the action macro as the command macro, then assign a Shortcut Key or add it to a ribbon/panel. This creates a reusable, shortcut-invokable macro.

Why does the macro pick the wrong point system (UCS vs WCS) when prompting?

If the macro was recorded with a different UCS or if the playback environment has a different UCS, coordinates may be interpreted differently. Fix by recording the UCS change as part of the macro or instructing users to set/lock the required UCS before playback.

Can I use ACTBASEPOINT tokens in scripts or AutoLISP?

Scripts (.scr) do not support Action Recorder tokens directly. For interactive prompting and more complex behaviors, use AutoLISP or .NET/VBA — these APIs let you prompt for points programmatically and are more flexible than Action Recorder tokens.

The macro doesn’t prompt at all during playback. What should I check first?

  • Confirm the macro includes a prompt token (not a fixed coordinate).
  • Check that you are running the correct macro version and it’s not been overwritten.
  • Verify required system variables and object snaps are set.
  • Ensure the commands used are available on your AutoCAD installation (no missing third-party commands).

You may also like