Please upgrade your browser for the best possible experience.

Chrome Firefox Internet Explorer
×

Bioware, you suck with continuity

STAR WARS: The Old Republic > English > Story and Lore
Bioware, you suck with continuity

DrMcbeefington's Avatar


DrMcbeefington
12.31.2011 , 12:08 AM | #1
So for the Sith Warrior storyline quest on Korriban, bioware hilariously put Sadow's remains in his own tomb with a lightsaber, forgetting that Sadow was buried on Yavin IV and he never used a lightsaber. Way to do your homework, bioware!

bfishback's Avatar


bfishback
12.31.2011 , 12:12 AM | #2
The entire series is ridden with continuity errors.

That's what happens when the series becomes so big there are multiple time periods.

DrMcbeefington's Avatar


DrMcbeefington
12.31.2011 , 12:14 AM | #3
Quote: Originally Posted by bfishback View Post
The entire series is ridden with continuity errors.

That's what happens when the series becomes so big there are multiple time periods.
The continuity errors have nothing to do with the series being big. It's the fact that someone didn't do their homework and the lazy ***/asses thought people would just ignore this error and continue playing like good little sheep. But TOR has the most continuity errors out of any piece of star wars literature out there.

Bielduwyn's Avatar


Bielduwyn
12.31.2011 , 12:16 AM | #4
Or, y'know, perhaps his backstory has been retconned now and this change happened with the blessings from Lucas Licensing. Perhaps this is the new canon about Naga Sadow.

Or it's an honorary tomb... or whatever.

I certainly wouldn't get too worked up over it personally.

Rhyltran's Avatar


Rhyltran
12.31.2011 , 12:17 AM | #5
Quote: Originally Posted by Bielduwyn View Post
Or, y'know, perhaps his backstory has been retconned now and this change happened with the blessings from Lucas Licensing. Perhaps this is the new canon about Naga Sadow.

Or it's an honorary tomb... or whatever.

I certainly wouldn't get too worked up over it personally.
There's also the possibility that they believe he's buried there but are wrong and it's some other ancient Sith's tomb. Do note that it's been a long time since his death and things are often lost in history.

Avrose's Avatar


Avrose
12.31.2011 , 12:19 AM | #6
Quote: Originally Posted by DrMcbeefington View Post
The continuity errors have nothing to do with the series being big. It's the fact that someone didn't do their homework and the lazy ***/asses thought people would just ignore this error and continue playing like good little sheep. But TOR has the most continuity errors out of any piece of star wars literature out there.
You know what happened when I found that error?

Shrugged.

You know why?

Because it doesn't matter. There is not a single piece of starwars literature where you truly get to know the guy. Frankly at the end of the day hes a cautionary tale for both sith and jedi.

Now on the other hand if you want to get into the argument that his tomb was moved after the actions of the sith empire and someone is spreading misinformation because the empire really didn't like him as a sith well thats a whole new ball park.
"Yes… and what are they without the Force? Take the greatest Jedi Knight, strip away the Force, and what remains?."
―Kreia

Bielduwyn's Avatar


Bielduwyn
12.31.2011 , 12:21 AM | #7
Quote: Originally Posted by Rhyltran View Post
There's also the possibility that they believe he's buried there but are wrong and it's some other ancient Sith's tomb. Do note that it's been a long time since his death and things are often lost in history.
A fair point, even in our history it has happened that ancient tombs get attributed to the wrong person until archaeologists found more evidence that allowed them to correct their mistake, it happened at least once with the tombs of pharaohs, for example.

DrMcbeefington's Avatar


DrMcbeefington
12.31.2011 , 01:27 AM | #8
So instead of chalking it up to laziness and continuity errors, these are the rationalizations that you guys come up with? There's a reason they don't do their homework, because a lot of people don't care. God forbid they actually get the storylines straight. Screaming "retcon!" is idiotic because that assumes they planned the retcon and had the blessing of related parties.

Rhyltran's Avatar


Rhyltran
12.31.2011 , 03:15 AM | #9
Quote: Originally Posted by DrMcbeefington View Post
So instead of chalking it up to laziness and continuity errors, these are the rationalizations that you guys come up with? There's a reason they don't do their homework, because a lot of people don't care. God forbid they actually get the storylines straight. Screaming "retcon!" is idiotic because that assumes they planned the retcon and had the blessing of related parties.
It's something you expect in Star Wars literature. Later books retcon previous books. It's not just books either. It happens and the rules of Canon are flexible to allow this to happen. Why accept it? There's so many different writers it's bound to happen. So the rules allow us to make sense of it. Retcons happen often in SW. Even if those retcons are accidental they still occur.

jmjon's Avatar


jmjon
12.31.2011 , 04:05 AM | #10
Quote: Originally Posted by DrMcbeefington View Post
So instead of chalking it up to laziness and continuity errors, these are the rationalizations that you guys come up with? There's a reason they don't do their homework, because a lot of people don't care. God forbid they actually get the storylines straight. Screaming "retcon!" is idiotic because that assumes they planned the retcon and had the blessing of related parties.


the easiest way to explain away a plot hole is with fridge logic

the second is with a retcon

fridge logic is preferable as it doesn't muck any further with the overall time line, deal with it