SC2Mapster

So, this is my first tutorial, so I apologize for any inconsistencies or missing information. Also, the sound quality and volume are a bit low.

I have seen questions (and I have HAD questions) on how to make range indicators that activate on selection, such as on the siege tank or the sensor tower. Well, after messing around with them for a while I figured out this method. It's a fairly easy method, but not readily apparent as to make it work. This method also doesn't require using triggers or behaviors as a work around, so it will work for multiple unit selection.

• Credit to Beider for finding the original workaround, here.
• Credit as well to OneTwo for all his video tutorials, as without his help I would never have figured this out.

Any comments, questions, or feedback, let me know.

Edit: Attached the demo map made in the tutorial

video = 10;
audio = 3;

getting result = 10;

thanks for that video, audio was just a bit quiet. keep up the work

@zeropoints: Go

Thanks very much for the feedback.

Thank you for the tutorial!

Just watched the video. Omg you are my lifesaver! Very very nice find! Thank you very much.

@BlacKcuD: Go

Glad I could help :)

@Snappybean: Go

Nice little tutorial on how to accomplish this, not sure where I might need it, but nice to see it covered in case I ever need it, all the editor stuff I'm learning keeps pointing towards use the code and XML, lol :)

@Deadzergling: Go

Thanks for the feedback. I cannot count the times I've used this method since I stumbled upon it. If you ever have need of this info, now you know where to find it! :)

The XML in SC2 is where it's at, for sure. The better you get with that, the more control you will have over your map.

@VindicatorDX: Go

A fix? That isn't a fix. That is EXACTLY how Blizzard does it for Siege Tanks in Siege Mode. This isn't a work around.

If Blizzard went and changed this, they would be breaking their own method and would have to re-implement this in a different way.

There is no need for an irrational fear of an upcoming fix for something that works 100% as intended.

BTW the new XML view makes the exporting stuff obsolete, and even before you could just edit it in raw data, the same way we used to add signal subnames, until Blizzard added support for that in the events ui.

The only "fix" Blizzard would provide would be adding the possibility to select the host name in the ui directly, without the need to manipulate raw data or xml files. This wouldn't break anything, because that would still work, you just wouldn't need it anymore.