[Clarifying] Moving Units + Some Questions

Problem 1!
When moving units to a location to imitate missile effects, they appear to hug contours of the terrain. I think someone said if you use:


Rather than


It will not hug the contours of the terrain. I would like to clarify if using the X-Y coordinates will ignore contour hugging but still move the unit and possibly if I don't have to clean up a leak using the X-Y coordinates.

Problem 2!
Is there a custom script condition to check for the height of a point in the terrain? I have UMSWE so I can GUI any condition I feel necessary.

Problem 3!
How exactly is missile speed measured? Pixels moved per second?

Problem 4!
Last time I made a *more advanced* laser tag map, I used an artificial missile collision system by giving a set of units something like...


And I gave the laser units the Damage Upon Death ability... I faced a very peculiar problem that the units would deal damage, but would not have any ownership sources... allied heroes did not gain experience from deaths and my test messages did not have a name to display for "Owner of Killing Unit"

My problem here is do I have to trigger the damage from a more permanent source, or am I using the wrong things? If I'm using the wrong things, what do I use instead?
___

Those are my problems for now, I hope for positive responses, and thanks ahead!

1) you have to use SetUnitX\Y natives, jass only
2) GetLocationZ() - return real jass only
3) Hardcoded range per second, if your unit have 600 attack range - 600 missile move speed == hit after second.
This called patching cells, not pixels.
4) Use damage upon death from goblin mines.

For GetLocationZ... would it be something like...


I don't know, I don't use JASS, I need a condition example of it of something like... Gets the Z of TempPoint and if it's equal to or less than...
___

I have no clue on how to use JASS for things other than memory leak fixing, so I need something like an example of what I'm trying to do... moving a unit in relation to it's facing angle...

Well, you have to pick apart the PolarProjection stuff to get new x/y coordinates, like so:
So, in your case, you'd probably do something like this:

As for GetLocationZ(), you'd probably do this:

I'll be running a trigger 100 times per second, and it needs both of those to be incorporated, so the *code* must be optimal. In UMSWE it allows custom script to be used in comparisons and conditions.

I'll toy around with this for my map... I might be back with some more comments/questions if it's within a week. If this rotates behind the first two pages, I'll start a new topic.
___

This trigger is a decelerated version of what I'm using:

Hugs terrain contours.

A 0.01 second repeating timer is completely unnecessary. 0.03 or 0.04 at least will be sufficient.

*apologizes*

The frequency is not exactly the point, it's hugging the terrain contours.
___

I'm having a very f**king weird problem now... I remade the trigger to make HERO units to slide across an area, and so far this is what I have got:



And here's the trigger with the SPFX bug-debugger attached to it:

[OffTopic]I never understood 'complex GUI', why would someone continue to use GUI when they know jass and know that jass is better?[/OffTopic]

Because he uses Mac OS X and there's not much motivation to learn JASS because you can't use vJASS or have a decent syntax checker.

Hahahahahahalolhahahaha did you read the first few posts?

Pyro is very correct about why I don't want/feel like learning JASS. Though it would be very nice if someone could back up onto the topic and tell me why my move system is being retarded...

Oh yeah, on some parts after the curl-glitch is finished, the unit may travel backwards...

Wow, I didn't even notice that there was a problem; didn't see your edit.

At any rate, there does not appear to be a flaw in your trigger, so I don't know what the error is... You are leaking a location with the SFX, though.

And it would be more optimized if you simply did this:

EDIT: You don't have any triggers that set a unit's facing? Anywhere? The fact that there are 2 symmetical curls would suggest that you do.

At your edit, what exactly do you mean triggers that set a unit's facing? Force them to look somewhere? I'm just setting up the main frame of the movement so far...

Any trigger that set's a unit's facing or orders your dummy units to cast a spell anywhere (which would cause it to face that point). Issuing point orders at places, etc..

Things like that.

Nope, none of that.

I integrated your optimization to the trigger, and now it's like the units are running against a very, very heavy eastward wind and they will try to run west, but keep getting blown west anyway.

The direction does not change, but at least it's a constant, non-loopy-loopy thingimajig.
___

*Begins the tearing out of the hair*



That has been decelerated...

What is the Icy Manipulator?
The Icy mage is a simple modification off the Archmage with a model of Jaina and a few stats changes. No movement speed changes have been made.

EDIT! - The one on the left started facing 180 degrees, and the one on the right started facing 0 degrees, but it appears there is a 135 degree difference between them.

EDIT! - I messed up the (left) and (right) tips, the one on the right is the curls, the one on the left is arcs.

Mac OS X Macs sucking... i dunno who need them. PCs owns. if you are "gamer" never buy a Mac...

words of true lamer ! if you got needed knowledge you can make the same + better than any preprocessor tool can. it's a question of desire.
vJass making people less thinking aka makes them stupid. it's a known fact. but it's makes many things more handly in expirienced hands.