Many, many moons ago I made a WeaponPosition primitive - never did commit it. It since got lost, but I just remade it, and have committed it.

Added a note to the wiki on it:

==== WeaponPosition ====

Sets the position of an accessory explicitly on (or over or under) the landscape.

<accessoryaction type="WeaponPosition">
<position><a>float</a><b>float></b><c>float</c></position><font color=yellow><i>
The coordinates of the position desired for the next accessory</i></font>
<positionoffset><a>float</a><b>float</b><c>float</c></positionoffset> <B>(optional)</B><font color=yellow><i>
A random offset value. The position will be offset by up to +/- each of these coordinates</i></font>
<onground>bool</onground> <B>(optional - default=false)</B><font color=yellow><i>
When set to true the height will be forced to ground level, ignoring any "c" value in position. The offset value can still be used (carefully!)</i></font>
<aimedweapon>Weapon</aimedweapon><font color=yellow><i>
Can be any of the [[#Weapons|weapon accessories]]</i></font>
</accessoryaction>

Side note: Gavin, what's this stuff, anyway:

I just copied another file and started from there, it had that stuff in it... looks like some MS cruft to me, but I have no idea. Something tells me I should remove it....

Quote sounds good, the more actions the better



Don't remove them, these unique guards are required around every header file. They prevent the header file from being included more than once (and thus defining the same class twice). The big load of numbers and letters are just VisualC trying to make sure the identifiers are unique.

Note that VC did not add those directly - rather they are from another .h file that I modified to start this one, so the identifier value is actually the same as another (I think I used WeaponVelocity.h)

Thats fine, just so long as its not the same as the other file. I sometimes copy some and just change the class name.

Perfect - all I did there, same as I have done before, is do a :%s/WeaponVelocity/WeaponPosition/g in vi.

Awesome, I remember us talking about this. Glad to see that make its way into the code. Seemed like we had about 5 different roundabout ways to get an effect to happen somewhere specifically on the map. Its nice to finally have one clear-cut, simple method of placing an event exactly where you want it to. That will make doing things like I did with disabling the shields on 2forts much easier and straight-forward.

Thanks Paul.

No probs, Rob. Glad to finally get it done.


Good to see ya here, stop in again sometime!