Using the location of a unit

[ResExsention]

Hello!

I've been working on a campaign so far (Purger of Evil) and I would like to find a way to call on the location of a specific unit as a variable in a generic event (not one of those moveto events in which $x1$x2 would work fine, but in something like a new turn event, where $x1 and $y1 could refer to anything. I've found out a few ways:

- Store the unit and then somehow call on the coordinates of the stored unit. Don't know how to do that.
- Or use $unitID.x and $unitID.y. It looks like the most promising, but it doesn't seem to be working when spawning units near the leader in a new turn with the [unit] tag going:

Code: Select all

[unit]
	side=2
	type=Lieutenant
	id=unitID1
	name="Lieutenant Lol"
	canrecruit=no
	x=$leaderID.x
	y=$leaderID.y
	
	{IS_LOYAL}
[/unit]

Though nothing happens. Is this how I'm supposed to do it?

I mean, I know you can invoke $unitID.id or maybe type, but I don't really know if calling the preset x y variables of a unit works. Spawning units is failing already. Any ideas? If I've already solved this, please help me out here, and tell me how I figured it out. I haven't found anything in the forums relating to this kind of topic, yet...

Thanks!

[Samonella]

- Store the unit and then somehow call on the coordinates of the stored unit. Don't know how to do that.
- Or use $unitID.x and $unitID.y. It looks like the most promising, but it doesn't seem to be working when spawning units near the leader in a new turn with the [unit] tag going:

The right thing is actually a combination of these: you store the unit to a variable, then use $variableName.x to access the variable and get the coordinate.

Code: Select all

[store_unit]
    [filter]
        <filter by id or however you want>
    [/filter]
    variable=<some variable name>
[/store_unit]
[unit]
	side=2
	type=Lieutenant
	id=unitID1
	name="Lieutenant Lol"
	canrecruit=no
	x=$<some variable name>.x
	y=$<some variable name>.y
	
	{IS_LOYAL}
[/unit]

Happy coding!

[ResExsention]

Ahh. I get it. So this is what it should look like?

Code: Select all

[unit]
	side=1
	type=General
	id=leaderID
	name="General Hello"
	canrecruit=yes
	recruit="Royal Guard, Halberdier, Master Bowman"
	x=50
	y=50
[/unit]

And then:

Code: Select all

[store_unit]
	[filter]
		id=leaderID
	[/filter]
	variable=generalHelloVariable
[/store_unit]

And then when I need to spawn a unit on his position:

Code: Select all

[unit]
	side=1
	type=Lieutenant
	id=unitID1
	name="Lieutenant Lol"
	canrecruit=no
	x=$generalHelloVariable.x
	y=$generalHelloVariable.y
	
	{IS_LOYAL}
[/unit]

Is that how it works? I think it is. Thanks, Samonella!

EDIT: And that's how you manipulate a unit's variables if need be, with [set_variable], right? Like maybe:

Code: Select all

[set_variable]
	variable=generalHelloVariable.goto_x
	value=52
[/set_variable]
[set_variable]
	variable=generalHelloVariable.goto_y
	value=52
[/set_variable]

Is that the basic idea?

[Samonella]

Is that how it works? I think it is. Thanks, Samonella!

Yup, exactly right!

EDIT: And that's how you manipulate a unit's variables if need be, with [set_variable], right? Like maybe:

Code: Select all

[set_variable]
	variable=generalHelloVariable.goto_x
	value=52
[/set_variable]
[set_variable]
	variable=generalHelloVariable.goto_y
	value=52
[/set_variable]

Is that the basic idea?

The basic idea, yes. Two notes:
-That only changes the variable, not the actual unit. To get the changes you made back into the real game you'd have to use [unstore_unit].
-The specific example you used, goto_x/y, doesn't make ai units move anywhere, the ai does whatever it wants with those values. But yeah that's how you use [set_variable].

[ResExsention]

Well then, nothing more needs to be said about this. Thanks, Samonella!

[Celtic_Minstrel]

Side note: The {IS_LOYAL} macro doesn't make a unit loyal. It only makes it look like it's loyal. To actually make it loyal you also need the following code:

Code: Select all

[modifications]
    {TRAIT_LOYAL}
[/modifications]

Or, if you want it to be loyal but not display the loyal trait, you can instead use upkeep=loyal.

You still need {IS_LOYAL} in both cases to add the visual indicator though.

[gfgtdf]

Or, if you want it to be loyal but not display the loyal trait, you can instead use upkeep=loyal.

note that we are considering making upkeep=loyal a 'effect-controlled' attribute in 1.15 so it might be later to use a [object] with a apply_to=loyal effect.

[ResExsention]

Yes, I know about that. I just forgot to add

Code: Select all

[modifications]
     {TRAIT_LOYAL}
[/modifications]