I discovered this in testing, and I wanted to let you all know, as (if it comes up), it may require some coordination and planning to prevent powers from interfering with one another.
An entity can only be in one team at a time.
Naga Song uses Teams to make mobs passive towards certain players.
If another ability were, at the same time as this was active, to set the team of those players and/or those mobs differently, Naga Song would suddenly stop working.
So, be wary if you use Teams in a power; they may conflict with other powers also using Teams.
This is also why we can't install datapacks that use teams, such as Tag or Name Colors, as these overwrite Naga Song and other team-based powers.
Hey future Origins developers.
I discovered this in testing, and I wanted to let you all know, as (if it comes up), it may require some coordination and planning to prevent powers from interfering with one another.
An entity can only be in one team at a time.
Naga Song uses Teams to make mobs passive towards certain players. If another ability were, at the same time as this was active, to set the team of those players and/or those mobs differently, Naga Song would suddenly stop working.
So, be wary if you use Teams in a power; they may conflict with other powers also using Teams.
This is also why we can't install datapacks that use teams, such as Tag or Name Colors, as these overwrite Naga Song and other team-based powers.