I'm posting this under Bugs and Known Issues, because I think it's both a bug ... and very much a known issue.
At the risk of making lots of players who have invested in Magik as a defender REALLY upset ... I'm just going to be blunt. Limbo is broken in regards to Alliance war when Magik is placed as a defender. Base abilities like Regeneration were modified so that they DID NOT scale, with additional health provided by the tile/node. Limbo scales proportionate to the sum total of champion attack AFTER the enhancements from the tile/node are applied.
Unless I'm mistaken, I haven't seen this "officially" addressed anywhere ... aside from people complaining on Line/Discord. Please direct me to a previous post if it has already been discussed. My searches yielded 0 results:
No results for limbo war.
No results for magik war.
Regarding the previous modifications to AW defensive placement and how nodes/tiles impact base stats ... I can only assume that damage based abilities are supposed to behave the same way health based abilities do. Which, it was made very clear by your team, that health based abilities should not scale.
Base Limbo for this particular Magik should yield 289.75 Energy damage per second:

But, in war ... you can clearly see the damage is 485 per tick (defensive player's name has been blurred to protect the innocent)...

To this end ... players are playing perfectly ... yet still die several times without ever once being hit. You've made it clear that you don't want to "isolate" certain champs, and that all champs should be relatively capable of clearing the in-game content. Granted, certain champs have major advantages over others, regarding VERY specific content ... but I don't think, "Use this specific champ" is an acceptable response.


If this is how Limbo is supposed to behave, just say so... and I suppose we'll accept that. But right, dozens (I'm not going to exaggerate and say I've talked this over with hundreds of people) of people I've talked to and discussed this with agree that they do not think Limbo should behave this way.