If you want attribute A to equal attribute B (even when B changes), use a constrain behavior.
Constrain A to B.
tatiangMember, Sous Chef, PRO, Senior Sous-ChefPosts: 11,949
Use a constraint when you have a fluid value such as rotation, position, or velocity. If you're simply changing an integer value such as a score, you don't need to constrain (constantly update) the attribute. In that case, just change both attributes at the same time using two change attribute behaviors.
Comments
If you want attribute A to equal attribute B (even when B changes), use a constrain behavior.
Constrain A to B.
Use a constraint when you have a fluid value such as rotation, position, or velocity. If you're simply changing an integer value such as a score, you don't need to constrain (constantly update) the attribute. In that case, just change both attributes at the same time using two change attribute behaviors.
Also, depending on how your logic works, it may be beneficial to use a rule saying:
when A is > B
Change B to A
But it comes down to what you are trying to accomplish with the values.