Target /Marking issues

Firstly, marking variable names are inconsistent.

Example: Using /mk ignore1 <t> will mark a target to ignore. But to retarget that marked target, you need to use /target <stop1> (Note the different variable names!) However to do the same to mark a target to attack, it's /mk attack1 <t> and /target <attack1> (Note the identical variable names!)

--------------------------------------------------

Also when using macros to mark targets to attack, I've noticed a very strange behaviour:

You can mark targets sequentially from Attack1 through to Attack5 by using the command /mk attack <t>. (The first target you use this command on will get marked as Attack1, the next target gets marked as Attack2, etc etc.) So far this is fine, but it then gets a bit odd depending on whether you use the command out in a world zone or inside a mission instance...

If you mark five foes in this way out in a world zone and one of those five marked targets dies, the mark used on that target gets freed up for you to use again - e.g. if you mark five foes and then the foe marked Attack2 dies, then using the command a sixth time will mark the next foe as Attack2. However if you mark five foes inside an instanced mission and one of them dies, the mark used on that target will NOT get freed up - so using the command a sixth time will no longer mark anything.

(This behaviour caught me out the first time I tried tanking inside a mission instance... it meant I could only mark the first five targets we encountered before the macro stopped working entirely. It's REALLY odd...)