Changing unit type of a Leader?

[quantumfleet]

I have a new question, related to my previous one: How can I remove the undead trait, or at least its effects? Transforming a unit doesn't remove any of its traits, including the undead trait, and I can't find anything on the wiki about removing traits. I tried adding a different trait that added something that looks like this:

Code: Select all

    [effect]
    apply_to=status
    remove=not_living
    [/effect]

But it doesn't remove the immunity to poison, drain, plague effect of the undead trait. (Do new abilities always get applied before preexisting ones? Because if so, that not_living bit gets reapplied after my new trait anyway.)

[Sapient]

You can remove the traits by storing the unit into a variable, using CLEAR_VARIABLE on the traits, then unstoring the unit variable. The attribute generate_traits=yes will cause new traits appropriate to the unit type to automatically be generated.

[quantumfleet]

I'm not entirely sure how, but this code intended to get rid of all traits (especially undead) managed to duplicate them

Code: Select all

[store_unit]
		[filter]
		side={SIDE}
		canrecruit=yes
		[/filter]
		variable=leader
		kill=yes
	[/store_unit]
		{CLEAR_VARIABLE leader.modifications.trait.id}
		{CLEAR_VARIABLE leader.modifications.trait.effect.add}
	[unstore_unit]
	variable=leader
	[/unstore_unit]

[Sapient]

Try this:

{CLEAR_VARIABLE leader.modifications.trait[0]}

Also, make sure you do this after changing the unit's race to something other than undead.

Disclaimer: untested

[WhiteWolf]

Hi

I did not read every post, your problem may be solved.
The problem with modifying only the type, is that the attack, resistance, moves etc. values will remain. But there is another solution:

Code: Select all

[store_unit]
    [filter]
        id=<Your-leaders-id>
    [/filter]
    kill=yes
    variable=leader_stored
[/store_unit]

[unit]
    type=<the new type you want>
    id=$leader_stored.id
    name=$leader_stored.name
    profile=$leader_stored.profile
    side=$leader_stored.side
    experience=$leader_stored.experience
    hitpoints=$leader_stored.hitpoints
    # Max hitpoints and experience will depend on the new type, so it don't have to be set to the original value
    x=$leader_stored.x
    y=$leader_stored.y
    canrecruit=yes
    # In theory, the leader don't have any traits, so there's no need of copying them
[/unit]
    
{CLEAR_VARIABLE leader_stored}

And for removing and creating traits, there is a macro I wrote (of course not by only myself, I got lots of help from others):

Spoiler:

To add a new trait:

Code: Select all

#define ADD_NEW_TRAIT FILTER TRAIT
        # Thanks for boru and Anonymissimus for the help!
        # Note that this macro sets every value to it's maximum!
        [store_unit]
            [filter]
                {FILTER}
            [/filter]

            kill=yes
            variable=trait_stored
        [/store_unit]

        [set_variables]
            name=existing_traits.trait
            to_variable=trait_stored.modifications.trait
        [/set_variables]

        [set_variables]
            name=new_traits

            [value]
                {{TRAIT}}
            [/value]
        [/set_variables]

        [set_variables]
            name=trait_stored.modifications.trait

            [insert_tag]
                name=value
                variable=new_traits.trait
            [/insert_tag]
            [insert_tag]
                name=value
                variable=existing_traits.trait
            [/insert_tag]
        [/set_variables]

        {VARIABLE experience_temp $trait_stored.experience}
        {VARIABLE trait_stored.advances_to $trait_stored.type}
        {VARIABLE trait_stored.experience $trait_stored.max_experience}

        [unstore_unit]
            variable=trait_stored
            find_vacant=no
        [/unstore_unit]

        {MODIFY_UNIT {FILTER} experience $experience_temp} 
        {FULL_HEAL {FILTER}}

        [store_unit]
            [filter]
                {FILTER}
            [/filter]
            
            kill=no
            variable=moves_stored
        [/store_unit]

        {MODIFY_UNIT {FILTER} moves $moves_stored.max_moves}

        {CLEAR_VARIABLE new_traits,existing_traits,trait_stored,moves_stored}
#enddef

Spoiler:

To delete all of existing traits except 1 that you give (in theory you can have only 2 traits, so...)

Code: Select all

#define REMOVE_TRAIT FILTER REMAINING_TRAIT
        # Note that this macro sets every value to it's maximum!
        # Note that the trait you give is the remaining, not the deleting one!
        [store_unit]
            [filter]
                {FILTER}
            [/filter]

            kill=yes
            variable=trait_stored
        [/store_unit]

        [set_variables]
            name=existing_traits.trait
            to_variable=trait_stored.modifications.trait
        [/set_variables]

        [set_variables]
            name=new_traits

            [value]
                {{REMAINING_TRAIT}}
            [/value]
        [/set_variables]

        [set_variables]
            name=trait_stored.modifications.trait

            [insert_tag]
                name=value
                variable=new_traits.trait
            [/insert_tag]
        [/set_variables]

        {VARIABLE experience_temp $trait_stored.experience}
        {VARIABLE trait_stored.advances_to $trait_stored.type}
        {VARIABLE trait_stored.experience $trait_stored.max_experience}

        [unstore_unit]
            variable=trait_stored
            find_vacant=no
        [/unstore_unit]

        {MODIFY_UNIT {FILTER} experience $experience_temp} 
        {FULL_HEAL {FILTER}}

        [store_unit]
            [filter]
                {FILTER}
            [/filter]
            
            kill=no
            variable=moves_stored
        [/store_unit]

        {MODIFY_UNIT {FILTER} moves $moves_stored.max_moves}

        {CLEAR_VARIABLE new_traits,existing_traits,trait_stored,moves_stored}
#enddef