Macro to create multiple lines from same base point
Ignore what I said script files do not pause for user input.
HOWEVER I do have a slight change to Steven's macro. After it has called the first pline command change all the other pline commands to a semicolon. I did that and created 20 polylines using that method
^C^CATTREQ;0;_Laymcur;\_INSERT;"Block";\1;1;0;ATTREQ;1;UCS;\;;pline;0,0;\;;;0,0;\;;;0,0;\;;;0,0;\;;;0,0;\;;;0,0;\;;;0,0;\;;;0,0;\;;;0,0;\;;;0,0;\;;;0,0;\;;;0,0;\;;;0,0;\;;;0,0;\;;;0,0;\;;;0,0;\;;;0,0;\;;;0,0;\;;;0,0;\;;;0,0;\;UCS;w;
Howard Walker
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
It will depend on what you are seeing, but macros can definately be affected by osnap points, it's counterintuitive but if there is a snap point and your coordinates in a macro are close enough to that point then a macro will snap to that point exactly as it would when you are moving the mouse cursor even though the cursor doesn't move. So in many cases turning osnaps off before running a macro is sensible, or include the word "non" before every coordinate in a macro to stop that behavior.
Accepted solution
Not wishing to be trumped by "Kermit" 
, and loving a good challenge, I see your 20 plines and raise it to 21 and then without the UCS setting so you can break out with Esc at anytime.
^C^CATTREQ;0;_Laymcur;\_INSERT;"Block";\1;1;0;ATTREQ;1;pline;\\c;;;\c;;;\c;;;\c;;;\c;;;\c;;;\c;;;\c;;;\c;;;\c;;;\c;;;\c;;;\c;;;\c;;;\c;;;\c;;;\c;;;\c;;;\c;;;\c;;;\c;
Resulting in a saving of 67 characters in the code
Accepted solution
"C" closes a polyline, so in effect it draws a segment back to the start point, which is handy when you are drawing around areas, in this case it makes the last point entered the base point again, and by entering ";" that restarts the last command (pline) pressing ";" again will start the new pline from the last entered point. The code is a bit tongue in cheek I usually prefer writing out macros using full words rather than the repeat notation";" it is much easier to read and debug the code that way, and in 3 weeks time when you try and change it and have no idea what it all means that really helps.
One drawback in doing it this way it actually creates a double "line" but it does trick the system into working. And as a point of note exploding the polylines would result in 2 lines, but selecting all these polylines and changing the properties to open would actually remove that extra segment.