Still opposed to the idea that Azshara had anything to do with Teldrassil, considering not a single person references that whatsoever in BfA and it seems like a tactic to just absolve the Horde from a clearly aggressively villainous act.
-
-
W odpowiedzi do @Necroxis9
The key thing is... as a result... the alliance retaliate by attacking Lordaeron. So any theory of it being anyone but the Horde who burn Teldrassil just doesn't make sense to me.
1 odpowiedź 1 podany dalej 2 polubione -
W odpowiedzi do @therealbuttress @Necroxis9
I still would like it to be Azshara even if its out of the blue (hue hue hue) but personally I would love it if it was Gallywix who went behind Sylvanas' back and wanted to further a reason for more war between the Alliance and Horde for cash.
1 odpowiedź 0 podanych dalej 1 polubiony -
W odpowiedzi do @Skoll_Shorties @therealbuttress
Azshara doesn't really make much sense, there's no lead up for her at all, and nobody talks about Azshara after the fact at any point, ever, regarding Teldrassil.
1 odpowiedź 0 podanych dalej 0 polubionych -
W odpowiedzi do @Necroxis9 @therealbuttress
They could make it ambiguous to the fire starting VIA Horde while as the Alliance think its obviously Sylvanas and the Horde. But Sylvanas in the one cutscene looks really surprised. It could be the obvious or it could be something else, we'll just have to wait and see.
1 odpowiedź 0 podanych dalej 0 polubionych -
W odpowiedzi do @Skoll_Shorties @therealbuttress
So the Naga, who have no role whatsoever outisde of 1 quest where the Horde steamroll over them in Ashenvale, suddenly come at the very end of the entire storyline and burn down the tree instead of the Horde Do you think that's good storytelling? Because that seems laughably bad
1 odpowiedź 0 podanych dalej 0 polubionych
Personally I prefer my own idea of it Gallywix going behind Sylvanas' back were I honest. But if Azshara is somewhat involve but not entirely involved I wouldn't mind is what I am saying.
Wydaje się, że ładowanie zajmuje dużo czasu.
Twitter jest przeciążony lub wystąpił chwilowy problem. Spróbuj ponownie lub sprawdź status Twittera, aby uzyskać więcej informacji.