If you use it on a CLOSED Polyline, and if you add Circle/Ellipse/Spline entity types as suggested and use it on a Circle or a closed Ellipse or Spline, there will be the irregularity that there will be NO GAP between the arrowhead at the start/end location (zero-degree direction in the case of a Circle) and the tail of the next arrow. That could be accounted for with some editing of the code. Using a LINETYPE defined to look something like this has many advantages. It won't have that irregularity at the start/end location. The overall "path" remains a SINGLE entity. That means that you can select it (to Move, Copy, Erase, etc.) in ONE pick, instead of needing to catch all those independent arrowheads and tails. That also means that if you adjust it in any way (change the radius of a Circle, Extend or Trim the end(s) of something open-ended, Pedit a Polyline, any kind of Stretch, etc.), the whole thing adjusts accordingly. The only real DISadvantage of using a linetype is in arrowhead positioning: it typically won't have an arrowhead AT the one end, but there will be some piece of path entity past that, and often the tail part of the arrow at the other end won't be the same length as the others. But if you can live with that shortcoming, the benefits are significant. Such a linetype could be defined using a Shape for the arrowhead, or a text character. Some symbol fonts such as in the Wingdings family have characters that could be used to look like this. I have a definition that's very like this except for the shape of the arrowhead -- it uses a greater-than character > [I don't this website is going to honor line breaks, so you'll need to get those back in the right places]: *ARROWS,--------> --------> --------> -------- A,4.0,[">",ROMANS,S=1.0,R=0.0,X=-0.95237,Y=-.4285657],-1.0