Personally given that it implicated a lot of characters in being complicit in genocidal behaviour or the rule of someone who openly used such tactics I could never even begin to enjoy it. There was a lot of character assassination.
-
-
W odpowiedzi do @JamtheBlue @lexstrasza
The only *real* issue I had with BfA was how long it took for the Horde to act. But I understood it from some points of view as to why they didn't do that. At the very least they did have them act it just took them a while to do it. It'd be different if they did nothing.
1 odpowiedź 0 podanych dalej 0 polubionych -
W odpowiedzi do @Skoll_Shorties @lexstrasza
I think two and a half patches of doing nothing after the literal genocide of a people and the destruction of their home was bad enough, but the fact that the Horde were totally okay with taking hostage and enslaving the elves before that paints a bad picture. Horde done dirty.
1 odpowiedź 0 podanych dalej 1 polubiony -
W odpowiedzi do @JamtheBlue @lexstrasza
When it comes to war nothing is going to be exactly pretty. What Saurfang initially wanted was a much better deal and would've ensured total victory against the Alliance on Kalimdor. For the majority of the Horde that's a good thing.
1 odpowiedź 0 podanych dalej 1 polubiony -
Is it messed up? Well to us as outside viewers, yeah. But war even in fiction isn't always about good triumphing over evil or vice versa. The Horde taking the whole of Kalimdor can be viewed as hecka bad but it also can be viewed as them winning and getting to thrive.
1 odpowiedź 0 podanych dalej 1 polubiony -
But yeah. As far as the Teldrassil situation goes the Horde should've acted much sooner and almost immediately after it happened. It didn't sit with a lot of people which is why the Saurfang arc was a lot of people's favorite because -that- was the Horde we wanted.
1 odpowiedź 0 podanych dalej 1 polubiony -
W odpowiedzi do @Skoll_Shorties @JamtheBlue
And once Sylvanas fled and Saurfang died that Horde became possible again.
1 odpowiedź 0 podanych dalej 0 polubionych -
W odpowiedzi do @Skoll_Shorties
It just becomes harder to believe that the Horde Saurfang fought for can be a real thing if large swathes of the Horde repeatedly go along with the genocidal figurehead. I'm also not sure how the justification of war not being pretty explains the stuff with Teldrassil.
2 odpowiedzi 0 podanych dalej 2 polubione -
W odpowiedzi do @JamtheBlue
Sylvanas was a smooth talker. She told Horde Soldiers what they wanted to hear and made them think she was going to deliver it to them. It didn't help she managed to smooth talk Saurfang which convinced others who normally wouldn't fall for Sylvanas would follow Saurfang.
1 odpowiedź 0 podanych dalej 1 polubiony -
W odpowiedzi do @Skoll_Shorties
Let's not write off a nation going in on nationalist rhetoric as anything other than nationalist rhetoric, regardless of who was saying it. The Horde still has a bad look for all of this. The Alliance never went in on the plan of going straight for UC to enslave the Undead.
1 odpowiedź 0 podanych dalej 2 polubione
Obviously, it's a bad look for the Horde and it's not the *best* reason to go to war with the Night Elves. But it's a reason that was at the very least believable. Messed up as all hell. But a very estranged possibility.
-
-
W odpowiedzi do @Skoll_Shorties
That to me is enough to dislike it heavily. The Horde had already gotten a taste of what was wrong with that mindset in MoP. To say that it felt totally out of character for 90% of the characters and races involved is an understatement. Sylvanas should have been deposed for it.
1 odpowiedź 0 podanych dalej 2 polubione -
W odpowiedzi do @JamtheBlue
I'm not disagreeing with you. I'm just saying there was a reason for why it happened. Was the reason good enough? That's a question for you or anyone, honestly. But yes, Sylvanas should've been disposed of earlier on or at least attempted to be disposed of.
1 odpowiedź 0 podanych dalej 1 polubiony - Pokaż odpowiedzi
Nowa rozmowa -
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.