AGEOD Forums

Hi chaps, I don't think SelectSubUnits can be used to select only fixed units?

Cheers, Chris

Not for now, right...

It's difficult to come up with an Indian winter quarters event for Indian units that may or may not be fixed.

Not being able to check if they have been unfixed before sending them home for winter can cause a lot of problems - so it would be great to have a fixed check for SelectSubUnits

I'm sure there is a work around though.
Cheers, Chris

I just thought I can use EvalUnqUnit in the event condition to determine if a unit is unfixed. The only snag with this is that I have to have a seperate event for each unique tribe - quite a number of events.

Cheers, Chris

Ok, I added the addition to the command to my list, your ticket is #10, and consider yourself privileged

I do sir!

Thanks, Chris

Pocus wrote:Ok, I added the addition to the command to my list, your ticket is #10, and consider yourself privileged

...and you do 1 per month?




Actually, I see you doing 1 per hour.
Many thanks.

Depends, some task can take sometime or are recurring

Hi Philippe, I screwed up mightily with this one.

2. SelectSubUnits can be used to select only fixed units
http://www.ageod-forum.com/showthread.php?t=13560

I actually needed a change to SelUnqUnit.

The problem is that I have 50 odd Indian units, some active, some fixed and some then unfixed by combat and events. When winter comes and I need to send them back to winter quarters I have no way of knowing if they are still permanently fixed or not. So I have to send all back regardless with a ChangeFixing of 5. In the spring all Indians will become active even if they should be permanently fixed.

After realising I messed up with the change I have written 16 new events that look to see if Indians have been unfixed by event so I have a work around of sorts for the Pontiac scenario but it is very messy and not perfect.

If you ever get time after VGN is released it might be worth adding a fix check to SelUnqUnit though

At least the change to SelectSubUnits may be a useful one.

Cheers, Chris

No problem, it happens

But I don't understand why you can't use SelectSubUnits to select all your indians (select all elements of faction tag IND which are raider for example, it should to the trick).

I need a command that looks at the unique name - they all go to different places for winter.

Cheers, Chris

Ah yes, the shining light of your powerful mind has at last reached me!

I'll see what I can do, you butterfly-bringer-of-doom. (private joke).

Pocus wrote:Ah yes, the shining light of your powerful mind has at last reached me!

I'll see what I can do, you butterfly-bringer-of-doom. (private joke).

you butterfly-bringer-of-doom - a phrase I imagine you never thought you would use

Thanks, Chris

I hesitated in which order I should put the adjectives and names btw. But it will do

Here are two new options (this should summon Lodi and Gray in no time!)

You can select by attributes your elements. So instead of say searching by faction tag you search for a particular attribute. I remind ppl that they can define attributes for their own use (it is better to bound them by * though), like:

*ThisIsMyOwnPrivateAttribute*

With SelectSubUnit(s) you can then use Attributes *Attrib1* *Attrib2* etc. to pick specific elements.

The second option is UniqueName <UniqueName> as in

SelectSubUnit = UniqueName Cherokee Warband

This is completely untested though, so please report troubles...

Pocus wrote:Here are two new options (this should summon Lodi and Gray in no time!)

You can select by attributes your elements. So instead of say searching by faction tag you search for a particular attribute. I remind ppl that they can define attributes for their own use (it is better to bound them by * though), like:

*ThisIsMyOwnPrivateAttribute*

With SelectSubUnit(s) you can then use Attributes *Attrib1* *Attrib2* etc. to pick specific elements.

The second option is UniqueName <UniqueName> as in

SelectSubUnit = UniqueName Cherokee Warband

This is completely untested though, so please report troubles...

This sounds wonderful - but after a day with internal audit I think I will have to give my brain a rest.

But thank you (I think :thumbsup !

Chris

Pocus wrote:Here are two new options (this should summon Lodi and Gray in no time!)

You can select by attributes your elements. So instead of say searching by faction tag you search for a particular attribute. I remind ppl that they can define attributes for their own use (it is better to bound them by * though), like:

*ThisIsMyOwnPrivateAttribute*

With SelectSubUnit(s) you can then use Attributes *Attrib1* *Attrib2* etc. to pick specific elements.

The second option is UniqueName <UniqueName> as in

SelectSubUnit = UniqueName Cherokee Warband

This is completely untested though, so please report troubles...

This command is new?

We can still use SelUnqSubUnit

and

SelUnqUnit

???

Pocus wrote:Here are two new options (this should summon Lodi and Gray in no time!)

You can select by attributes your elements. So instead of say searching by faction tag you search for a particular attribute. I remind ppl that they can define attributes for their own use (it is better to bound them by * though), like:

*ThisIsMyOwnPrivateAttribute*

With SelectSubUnit(s) you can then use Attributes *Attrib1* *Attrib2* etc. to pick specific elements.

The second option is UniqueName <UniqueName> as in

SelectSubUnit = UniqueName Cherokee Warband

This is completely untested though, so please report troubles...

If I understand this correctly :-

Command SelectSubUnit
Param0 Cherokee Warband|0

Is this the correct format?

This would make SelectSubUnit similar to SelUnqSubUnit but with the ability
to select only fixed?

Cheers, Chris

I've tried several syntax, with little sucess:

SelectFaction = $GBR
StartEvent = evt_nam_atribute_select|1|1|NULL|NULL|NULL|NULL

Conditions
MinDate = 1620/01/01

Actions
SelectSubUnit = UniqueName Infantry;
SelectSubUnit = Attributes *countercharge*;
GenMsg

EndEvent

First on selects every unit on map
Second selects nothing

Line 15192: SelectSubUnits 1001548 Braves added, List Count now at: 485
Line 15192: SelectSubUnits finished Regions Selected: 0 SubUnits Selected: 485
Line 15193: SelectSubUnits finished Regions Selected: 0 SubUnits Selected: 0

Hocus Pocus

Lodi, where you have :-

SelectSubUnit = UniqueName Infantry;


Do I actually have to put UniqueName in param0?

Param0
UniqueName|Cherokee Warband|0

Cheers, Chris

Dunno, doesn't seem to work and I tired of trying things until we get "ye olde syntaxe answere"