No way to retreive unit's coordinates?

[Amoebka]

Long story short, I'm trying to create an alien with a "dread aura" that drains morale of nearby x-com soldiers, and I want the intensity to scale with distance between the alien and the soldier. Except there seems to be no way to get unit's XYZ coordinates on the battlescape map? There are ways to get facing direction, and even turret turn angle, but I see nothing for actual position. That can't be right, can it? Any suggestions for a workaround?

[Meridian]

getPosition.getX
getPosition.getY
getPosition.getZ

[Amoebka]

Thanks a lot.

This does, however, bring the question of why I can't see it in the ref linked on ufopaedia. Is it outdated by now? Where do I get the up to date one then?

[Yankes]

What link?
Beside, best place to check for uptodate data is exe itself, when you enable verbose logging, script engine dump all meta data to log, and there you can check actual script API.

[Amoebka]

https://raw.githubusercontent.com/ohartenstein23/Yankes-Scripting/master/yankesScript.txt

It's on ufopaedia, page for ModScript.

[Yankes]

Code: [Select]

[16-09-2019_13-43-50] [DEBUG] Script info for: recolorUnitSprite
From this page, its from 3 years ago.

[Amoebka]

Serves me right for trying to use the wiki. 

If I may, another quick question. I have 2 newTurnUnit scripts, with offsets 11 and 12. Will the game run offset 11 for each unit, and THEN offset 12 for each unit, or will it run 11 and 12 for one unit, 11 and 12 for the next, etc?

[Yankes]

Second version. All global scripts hooks run as one whole operation on one unit. This mean you need finish processing one unit before any thing can be done for next one.

[Amoebka]

Hm. Guess my idea can't work then, because a unit can't know the location of all other units in newTurnUnit and the order doesn't allow passing that information between units. What about local scripts? If I have a newTurnUnit defined on an armor, and another one globally, would that allow "going back and forth" between processing units?

[Yankes]

No, "global" and "local" are called at same moment on same unit, only place where you define them rule set differ.

Overall currently cross-processing of unit in lacking, I had not time to sit down and thing to how best expand scripts to make it easy.
Some workaround is when you process you special unit, you get its position and then search tiles around it, and for each tile see if there is any unit there.
Then you can apply some changes, but be care full, this unit could be in different stage of end-turn processing.

[Amoebka]

Yeah, I thought about that, but I suspect searching 10000 tiles 20 times every half turn isn't going to be very fast.