Get the plan into Arma 3

Worth knowing

• Two scripts, side by side. The first draws markers that stay put. The second draws markers players can drag and delete in game — handy, and the same click that fixes a misplaced objective also deletes it, with nothing asking first.
• Both are LOCAL EXEC. GLOBAL EXEC is wasted on the first and actively wrong on the second, where the marker names carry the client that made them.
• Running it again replaces the markers from the last run rather than laying a second set over them. Two maps can never delete each other’s.
• A unit’s size arrives as Arma’s own size marker, stacked on the unit as a mission maker would place it.
• Rectangles and ellipses arrive as Arma’s own area markers, filled and turned the way they are drawn. Arma shows no text on an area marker, so their labels stay on the website’s map.
• AOs come across as their borders. The grey mask around them does not: Arma cannot draw a cover with holes in it from a pasted script.
• Arma has no dashed line and draws every line at one width, so a dashed or dotted line arrives as its dashes — one short line marker each, at most 150 per line — and thickness stays on the website. Arrow heads arrive as Arma arrow markers at whichever ends have one.
• A line’s name arrives as text alone at the same place — the middle, or both ends of a phase line — on an invisible marker, because a line marker shows no text in Arma.
• Above the scripts, the panel says how many markers the plan makes and what will not survive the trip.
• The debug console has to be enabled in the mission’s description.ext.