At least the second half has been confirmed as “by design”, I think. Here’s how it goes.
When you are entangled, your current attack stat is stashed away in a secret place and the attack stat is set to 0.
So if anything interacts with the troop’s attack at that point, it is 0. You can’t “steal attack” from 0, so troops that do that won’t work. Technically devour works: it’s documented as “adding the troop’s attack” and it adds 0 to your attack.
Entangled FORCES your attack to 0. So if you add +100 attack while entangled, nothing happens. Any ability that would increase your attack has no effect, because a troop that is Entangled is defined as having 0 attack.
The weird part is when you lose Entangled, that attack stat from before is restored.
Abilities that add 10 to attack don’t say, “Add 10 to what your attack was before you were entangled”. The sad fact is while you’re entangled, your “current attack” is stuck at 0 until it wears off, so “gain attack” effects are worth nothing.
This has several interesting design impacts:
- Mixing Devour and Entangled on your team is counterproductive.
- Teams that Entangle themselves are sort-of counters to Devour teams.
- Troops that might Entangle like Magnus are risks if you want to use Devour.
- Entangle is a good counter to self-buffing teams.
- Entangling yourself is also a sort-of counter to troops that steal attack like The Wild Queen.