[remove_object] bug?

[vghetto]

Hi,

Say you have a unit with a bunch of custom defined [advancement] options that are not inside the [modifications] block, and the unit also has some unrelated [object]s defined inside the [modifications] block.

If you call [remove_object] on one of the objects, the entire [advancement] options list gets wiped out except for the base unit's default amla, if defined.

[octalot]

I can't find anything in the Wiki saying that putting [advancement] into SingleUnitWML is expected to work. Have you tried using EffectWML's apply_to=new_advancement?

[vghetto]

I was writing the [advancement] blocks directly into unit.advancement via [set_variables] followed by [unstore_unit].

I rewrote it to use apply_to=new_advancement instead. This time [remove_object] didn't wipe out the list
thanks