Adding Leader to Multileader Puts Multileader onto Current Layer

[rlattaQWEML]

Adding a leader to a multileader object reassigns that object to the current layer. I don't want this happening. I want the object to stay on its original layer. This just started happening recently (I'm on C3D 2025). Is there some system variable I need to adjust?

Thanks!

EDIT: See attached video

[JEBarndt]

THAT WORKS IF YOU KEY IN THE COMMAND, WHAT ABOUT THE RIGHT CLICK SHORTCUT MENU? THAT STILL CHANGES THE LAYER.

[JEBarndt]

I AM ON VER 2025.0.2

[mhaarmannB8YYD]

I'm on the same version and when I click on the multileader and right click, it stays on the object layer. Check your text window and see what command it's running when you right click. Mine's showing the _MLEADEREDIT command.

Try going into your CUI again and scrolling down to the "Partial Customization Files">"ACAD">"Annotate-Leaders">and change the Macro for this and see if it works. I'm wondering if the right click is linked to this location? See if that works.

[JEBarndt]

Same think, if I add a leader it changes the layer.
If I remove a leader it stays on the layer it was created on.
I checked my work...lol...i have what you have in the sameplace.
I tried and even restarted. Same issue. Put all back and still same issue.

[JustinGG5N9H]

Thanks for this. This worked for me, but did not work for another user in out office. I made this Macro Command change for both the Ribbon and the Toolbar and it worked great on my set up. But I tried to recreate the process on another users CAD, and the same steps did not work for him. As a note, there is another user who doesn't have this issue at all. That user is updated to the same version as I am, but they have not had any issues for this item. Anyone run into a reason why this fix works for some people and not others?

[c_haymon]

Have you tried MLEADERLAYER command and set it to the layer you need all of them to be set to?

[JustinGG5N9H]

Update: I was able to get it to work on that second user. They had not updated the software in a while. After Updating to "Civil 3D 2025.2" and "AutoCAD 2025.1.1" the fix became active. I verified that the fix was still needed by using the old command in the macro setting. and then reapplied the fix to be sure. So, in summation, Be sure to update your Civil 3D and AutoCAD first, and then apply the fix. If you are installing any updates later then the two listed above, then try to add a new multileader to your Multi Leader text to see if Autodesk fixed it on there end first. If not, then apply the fix from this thread.

[Cadguru42]

So it worked before the update, you installed both C3D and ACAD updates, then had to run this workaround to the bug? Why bother installing the updates in the first place since Autodesk still hasn't fix it?

[JEBarndt]

Yes and it works, but that is not the way it should work. The simple way is just to change the current layer, but adding a leader if only once in a while.
I just want it to work the way it should. I also opened my autocad 2025.0.1 and it is the same, my C3D is 2025.0.2 I hope autodesk fixes it on the next patch.

[JEBarndt]

LOOKS JUST LIKE YOUR, BUT STILL THE SAME ISSUE. NO MATTER IF I USE THE RIGHT CLICK OR THE RIBBON OR THE GUI, ALL THE SAME. SAME WITH MY OUT OF THE BOX AUTOCAD 2025.1

[JEBarndt]

OUR I.T. PUSHES EVERYTHING AND WE DON'T GET A CHOICE.

[JustinGG5N9H]

Because the fix did not work before the updates. My personal work station had the updates already when I first used the fix.

When I tried to use the work around on another users computer, it did not work. I put the fix in place, and the multileader bug was still present. After I updated them to Civil 3D 2025.2 and AutoCAD 2025.1.1 like my PC was, the fix was able to take over, and the bug was effectively fixed. Not sure why, what, or how, but that is what I found as I worked though the issue.

[JustinGG5N9H]

Talk to your IT or CAD Manager and let them know about he issue and how to fix it, Send them this thread. Also, You have two very old versions, if you're rocking AutoCAD 2025.0.1 and Civil 3D 2025.0.2. You need later versions of both for @mhaarmannB8YYD fix to work.

[JEBarndt]

I AM STUCK, I.T. *(YOU KNOW THE REAL CAD EXPERTS)* 😞 THINK THEY NEED TO TEST EVERYTHING FIRST. SO I'M ALWAYS BEHIND.

[saratBTF8L]

THANK YOU!!!!! 

[MKearney028]

For anyone that prefers LISP, the command that runs when you click the Add Leader button is "AIMLEADEREDITADD". You can add the following couple lines to your ACAD.lsp or ACADDOC.lsp to redefine it: 

(command "undefine" "AIMLEADEREDITADD")
(defun c:AIMLEADEREDITADD()
(command "mleaderedit")
) 

That will replace the broken command with the standard MLEADEREDIT. It still looks like it's going to change the layer while you're in the command, but stays on the correct layer when you finish it.

[JEBarndt]

I TRIED ADDING IT TO BOTH AND IT DIDN'T WORK. I DID RESTART ACAD BOTH TIMES.

[mhaarmannB8YYD]

Unfortunately, you may have to use the MLEADEREDIT command if none of the suggestions worked. Hopefully the command still works for you.

[MKearney028]

A couple of steps to troubleshoot.

1. Did you already make any changes from the previous suggestions that already changed the function of the button? The suggestion to edit the macro would have already disabled this command, so you would need to put it back.
2. Copy and paste those commands into the drawing to see if it works outside of the startup scripts.
3. Assuming that does, double check if there is an ACAD.LSP created by your company that gets saved somewhere else. (That's how I help manage my users and apply fixes like this.) In your Options > File tab > expand the top folder, Support File Search Path. CAD checks these in order, top to bottom, so see if there are any other folders that may have another .lsp file running, and/or verify that the location of the ACAD.LSP that you modified is saved in one of those locations. There may be an issue if there are conflicting lisp files.
4. Less helpful, but you may want to set MLEADERLAYER to an obvious incorrect layer. Either one that doesn't exist and will cause the CAD Standards Checker balloon (if you have CAD Standards set up) or something with a noticeable linetype difference, like dashed or a fence linetype. That will at least be a visual cue that something has changed in case the object layer and current layer are similar.

I hope something here helps.

[JEBarndt]

HI, THANKS BUT I TRIED THAT LONG AGO...NO JOY!