Jump to content

Welcome to Obsidian Forum Community
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. If you already have an account, login here - otherwise create an account for free today!
Photo

The List of Continuity Mistakes


  • This topic is locked This topic is locked
280 replies to this topic

#41
Goodwood

Goodwood

    (2) Evoker

  • Members
  • 71 posts
A small correction:

The world of Althir isn't the one at which Canderous rides his Basalisk droid. That world is unnamed in KOTOR I, and Althir is the battle in which Canderous was promoted to lead a subsect of his clan. It later comes up in his side-quest, with Jagi, one of the soldiers under his command at that battle.

#42
Darth_Radnor

Darth_Radnor

    (5) Thaumaturgist

  • Members
  • 416 posts
  • Location:California

Let me see.

Marka Ragnos Tombs is in the image of himself

Nada Sadow isn't even there, but even the Bioware devs fixed that mistake saying it was just a memorial.

The Valley of the Dark Lords isn't two huge building on the edge of a cliff. No the Valley of the Dark lords in hundreds of huge Tombs all with a different look, and all made for one Sith Lord. All embedded in the walls of a Canyon.

If you play Jedi Academy(whether is sucks or not, isn't a question) that is the best continuity representation of the Valley.

The KOTOR/KOTOR 2 Valley is wrong to continuity, and hopefully will be corrected when the KOTOR comic in Star Wars: Tales comes out. ;)

<{POST_SNAPBACK}>


I still don't see what the problem with Naga Sadow's tomb being there is. The Sith would *undoubtedly* build the tomb for their Dark Lords the moment they became the Dark Lord. I mean, you didn't see them going "wait for us to build the tomb before we put Ragnos to rest" did you? No, the tomb was prepared for him *during his life*.

Simply put, it was a tomb that wasn't used. Also the valley of the Dark Lords isn't just the bit we see in KotOR... you'll notice it extends further and also drops down into a deeper level where it extends for ages... it's not "two huge building" as you describe.

Sure, it doesn't really look the same as in the comics but... *nothing* in KotOR "looks" right if we take what Tales of the Jedi made it out to be.

The entire galaxy looked gothic and ancient which was pretty ridiculous when you think about it: I mean, sure it was set 4,000 years before the films, so the artists think "lets make everything look old", but the Republic and hyperspace travel had been in existance for about 20,000 years which doesn't suggest "ancient looking technology" to me.

KotOR makes everything look more similar to the movies, which is probably more accurate in the grand scheme of things.

Actually, KotOR changes a lot of the continuity to mesh more closely with the movies, which is something I really liked - and whilst it kept the names of people like Exar Kun and Ulic Qel-Droma in the background it's obvious that they'd changed the events and the characters themselves.

The Sith War for example, was *nothing* like it was described in KotOR. In KotOR it seems like an actual war that involved hundreds of Jedi/Sith fighting each other and legions of troops facing each other down. Basically it seems like a proper war.

In the comics, the war lasts like a couple of days. I've searched all the way through them to find points where I think "well a lot of time could have passed between here and here" but there are *none*. The war seriously lasts about a week at the most.

Kun brainwashes 20 Jedi (out of HOW many in the galaxy?), who go on to only kill 8 Jedi Masters throughout the galaxy. Wow, how exceptional. As far as KotOR is concerned, he managed to corrupt hundreds, perhaps thousands of Jedi, considerably more awesome I think.

Ulic Qel-Droma gets two armies beneath his command including all of the mandalorians and has *Mandalore* as his right-hand man, but he hardly attacks the *galaxy*. He just gets ****y and goes for Coruscant and gets pillaged by a group of 10 Jedi because he gets stabbed in the back by his Sith-squeeze.

Sith technology is used to devastate a Ossus' surface. Admittedly, that's cool- then all the mandalorians and Ulic and Kun invade it to steal artifacts. Urm, and then Kun leaves, Ulic kills his brother and feels bad and tells the Jedi where Kun is.

They all travel over there and do their "light blocking thang" - Kun sheds his body and his spirit gets trapped in a temple to await Luke Skywalker's Jedi Academy.

Basically, KotOR makes Kun seem like a really powerful Dark Lord as he is always said to be, whilst the comics make him seem like a pansy who is always falling back on Sith technology to do his work for him.

"use this amulet"

"use this ship"

"I'll use this big aritifact to drain all my warrior's life force and become a ghost"

Also, he's just plain too stupid in the comics.

So I'll take KotOR's interpreation of the "War of Exar Kun" over TotJs "The Sith War" (that wasn't even a war) any day.

Though I do think we were cheated on not getting a proper Basilisk war-droid in KotOR2... and it breaks with KotOR 1 continuity (as has been said, Canderous said he "rode" his basilisk). But I can cope and when it comes right down to it- though I did enjoy TotJ (i mean, i've been using a screenname inspired by Ulic since i was about 12) i enjoy the KotORs much, much more and as far as I am concerned they are the *real* record of the stuff that happened in SW history.

<{POST_SNAPBACK}>


Excellent points, Ulicus. Although I like TOTJ, I find it to be incoherent with its times:

http://forums.obsidi...topic=28729&hl=

#43
Chris Avellone

Chris Avellone

    Inactive

  • Members
  • 156 posts
We kept the valley the way it was in K1. Considering memory constraints, I completely understand why it was modeled the way it was.

The purpose of the ritual and Freedon Nadd was already explained by another poster (thanks, Ulicis). As to whether he was "wiped off the Force map," I have no idea, and no argument you could present to me from Tales of the Jedi would ever make me think that the evil that took place in that location couldn't still be harnessed for further acts of destruction.

The basilisk war droid version presented in K2 was an intentional departure from the ones presented in Tales of the Jedi, and we are happy, because frankly, those look really stupid. This is much the same reason that many of the designs in K1 are a departure from the ship designs in TOJ, and with good reason. So yes, the basilisk droid version was an intentional depature from the older models, and we take full responsibility. It is noteworthy that LucasArts and LucasFilm agreed with our decision on the first pass, much as they agreed with the decisions made with K1's look.

Oh, and someone mentioned Sith holocrons (Radnor?) - Exar Kun did not destroy the last holocron. Sith Holocrons show up repeatedly in the Expanded Universe after the events of the Sith War, and they are Sith holocrons that contain knowledge of Sith - Quinlan Vos retrieves one for Dooku in Star Wars: Republic, they show up repeatedly in the Jedi Quest series, etc, etc.

Regardless, I am certain there are other mistakes. It's a big universe and a big game, you'll find them. I did try to read, play, and watch every piece of Star Wars source material I could find, but I freely admit I make mistakes.

#44
Kissamies

Kissamies

    (4) Theurgist

  • Members
  • 365 posts
  • Location:Land of ter�s k�si
  • Pillars of Eternity Silver Backer
  • Kickstarter Backer
  • Deadfire Silver Backer
  • Fig Backer
I'm not so concerned about Basilisk not looking like its TOJ desing, KOTOR's style is different from TOJ anyways. However, it looking like Virago did tickle my "they must have gotten it wrong" nerve. My first thought was along the lines of "Hey, that's Xizor's ship!" Then I just shrugged and moved along. It's not like it's a real issue.

#45
Goodwood

Goodwood

    (2) Evoker

  • Members
  • 71 posts
I think it was a good call on the Basalisk war droid...

...but then, when I was playing I was too wrapped up in the story to care whether or not it was accurate. And I suspect everyone else was as well...at least at first...

#46
Darth Nuke

Darth Nuke

    (7) Enchanter

  • Members
  • 819 posts

The basilisk war droid version presented in K2 was an intentional departure from the ones presented in Tales of the Jedi, and we are happy, because frankly, those look really stupid. This is much the same reason that many of the designs in K1 are a departure from the ship designs in TOJ, and with good reason. So yes, the basilisk droid version was an intentional depature from the older models, and we take full responsibility. It is noteworthy that LucasArts and LucasFilm agreed with our decision on the first pass, much as they agreed with the decisions made with K1's look.

<{POST_SNAPBACK}>



LA's agrees to everything when it comes to continuity. Proven because they in the Mandalorian Article in issue 80 of insider, sets in stone that the Basilisk is a beast. The Mandalorians Basilisk in TOTJ might look stupid, but regardless it is a Basilisk War Droid. That Virago,which I think looks stupid, isn't a Basilisk. That thing would be destroyed in seconds by the stupid kind.

Even from Canderous discription in KOTOR he speaks of the Beast. I don't like that just because YOU THINK something looks stupid, you feel the right to change it. Of course in the end you didnt' change anything, the Basilisk is still the beast as it should.

I would hope that IF you are making KOTOR 3, you put the ACTUAL Basilisk into the game.

"Regardless, I am certain there are other mistakes. It's a big universe and a big game, you'll find them. I did try to read, play, and watch every piece of Star Wars source material I could find, but I freely admit I make mistakes. "

And the Basilisk was one of them, intentional or not.

#47
Goodwood

Goodwood

    (2) Evoker

  • Members
  • 71 posts
I'm feelin' the love in here... (w00t)

#48
Chris Avellone

Chris Avellone

    Inactive

  • Members
  • 156 posts

The basilisk war droid version presented in K2 was an intentional departure from the ones presented in Tales of the Jedi, and we are happy, because frankly, those look really stupid. This is much the same reason that many of the designs in K1 are a departure from the ship designs in TOJ, and with good reason. So yes, the basilisk droid version was an intentional depature from the older models, and we take full responsibility. It is noteworthy that LucasArts and LucasFilm agreed with our decision on the first pass, much as they agreed with the decisions made with K1's look.

<{POST_SNAPBACK}>



LA's agrees to everything when it comes to continuity. Proven because they in the Mandalorian Article in issue 80 of insider, sets in stone that the Basilisk is a beast. The Mandalorians Basilisk in TOTJ might look stupid, but regardless it is a Basilisk War Droid. That Virago,which I think looks stupid, isn't a Basilisk. That thing would be destroyed in seconds by the stupid kind.

Even from Canderous discription in KOTOR he speaks of the Beast. I don't like that just because YOU THINK something looks stupid, you feel the right to change it. Of course in the end you didnt' change anything, the Basilisk is still the beast as it should.

I would hope that IF you are making KOTOR 3, you put the ACTUAL Basilisk into the game.

"Regardless, I am certain there are other mistakes. It's a big universe and a big game, you'll find them. I did try to read, play, and watch every piece of Star Wars source material I could find, but I freely admit I make mistakes. "

And the Basilisk was one of them, intentional or not.

<{POST_SNAPBACK}>


Hmmm. Okay, I think you're making a mistake here, but no harm done.

Basically, I think you missed what I said in the previous post - the right to change something never rests with me, it rests with LucasArts and Lucasfilm. I suppose you could blame LucasArts if you want, but I think that would be unfair and frankly, another mistake - as I said in the previous post, please keep in mind that everything goes to Lucasfilm for approval. Everything.

I would strongly suggest that if you have a problem with the basilisk war droid, you don't have to stand for it - contact Lucasfilm, they run the show. Maybe they chose unwisely during the approval process when they saw the concepts. I seriously doubt it, but who knows?

#49
Mondo

Mondo

    (3) Conjurer

  • Members
  • 185 posts
  • Location:NYCT
Hey MCA good to see your still around, and everybody makes mistakes, that's why they put erasers on pencils. Not to mention the 500,000 lines of dialouge....etc...

#50
jaguars4ever

jaguars4ever

    Arch-Mage

  • Members
  • 7093 posts
  • Location:Salarian Special Tasks Group
But why the freakin' Virago, Chris? Why? :-

#51
Darth Nuke

Darth Nuke

    (7) Enchanter

  • Members
  • 819 posts

The basilisk war droid version presented in K2 was an intentional departure from the ones presented in Tales of the Jedi, and we are happy, because frankly, those look really stupid. This is much the same reason that many of the designs in K1 are a departure from the ship designs in TOJ, and with good reason. So yes, the basilisk droid version was an intentional depature from the older models, and we take full responsibility. It is noteworthy that LucasArts and LucasFilm agreed with our decision on the first pass, much as they agreed with the decisions made with K1's look.

<{POST_SNAPBACK}>



LA's agrees to everything when it comes to continuity. Proven because they in the Mandalorian Article in issue 80 of insider, sets in stone that the Basilisk is a beast. The Mandalorians Basilisk in TOTJ might look stupid, but regardless it is a Basilisk War Droid. That Virago,which I think looks stupid, isn't a Basilisk. That thing would be destroyed in seconds by the stupid kind.

Even from Canderous discription in KOTOR he speaks of the Beast. I don't like that just because YOU THINK something looks stupid, you feel the right to change it. Of course in the end you didnt' change anything, the Basilisk is still the beast as it should.

I would hope that IF you are making KOTOR 3, you put the ACTUAL Basilisk into the game.

"Regardless, I am certain there are other mistakes. It's a big universe and a big game, you'll find them. I did try to read, play, and watch every piece of Star Wars source material I could find, but I freely admit I make mistakes. "

And the Basilisk was one of them, intentional or not.

<{POST_SNAPBACK}>


Hmmm. Okay, I think you're making a mistake here, but no harm done.

Basically, I think you missed what I said in the previous post - the right to change something never rests with me, it rests with LucasArts and Lucasfilm. I suppose you could blame LucasArts if you want, but I think that would be unfair and frankly, another mistake - as I said in the previous post, please keep in mind that everything goes to Lucasfilm for approval. Everything.

I would strongly suggest that if you have a problem with the basilisk war droid, you don't have to stand for it - contact Lucasfilm, they run the show. Maybe they chose unwisely during the approval process when they saw the concepts. I seriously doubt it, but who knows?

<{POST_SNAPBACK}>


And I'm saying that they agree to everything. KOTOR 2 made the Basilisk the wrong way. Approved or not, LFL went back and approved the Beast in the Mandalorian Article. Definded,pictured, and everthing.

Yet you say LFL changed it, but it was you people who made the concept of the WRONG Basilisk.

Either way there are TWO basilisk now. The Stupid mighty version, and the Virago Star fighter.

I'm sorry you don't like something, but I don't think that gives you the right to remake anything.

I hope whoever Makes KOTOR 3, will put the Stupid mighty version back in.

#52
jaguars4ever

jaguars4ever

    Arch-Mage

  • Members
  • 7093 posts
  • Location:Salarian Special Tasks Group
'Stupid' is such a harsh word...I prefer to use the terms garish and unsubtle - much like the warriors riding them. :cool:

#53
213374U

213374U

    Arch-Mage

  • Members
  • 5316 posts
  • Location:PIGS
  • Pillars of Eternity Backer

The basilisk war droid version presented in K2 was an intentional departure from the ones presented in Tales of the Jedi, and we are happy, because frankly, those look really stupid.

And that's about all the reasons I need.


I'm sorry you don't like something, but I don't think that gives you the right to remake anything.

Well, he is the lead designer after all. If LFL approved his work, he has the right to change whatever he sees fit.
But please tell me who's pointing a gun at your head to buy and play this game. If the continuity 'issues' are so abhorrent to you, you can always get back to reading your vaunted TotJ and forget all about K2. :wub:

#54
Jinx

Jinx

    (1) Prestidigitator

  • Members
  • 37 posts

The basilisk war droid version presented in K2 was an intentional departure from the ones presented in Tales of the Jedi, and we are happy, because frankly, those look really stupid. This is much the same reason that many of the designs in K1 are a departure from the ship designs in TOJ, and with good reason. So yes, the basilisk droid version was an intentional depature from the older models, and we take full responsibility. It is noteworthy that LucasArts and LucasFilm agreed with our decision on the first pass, much as they agreed with the decisions made with K1's look.

<{POST_SNAPBACK}>



LA's agrees to everything when it comes to continuity. Proven because they in the Mandalorian Article in issue 80 of insider, sets in stone that the Basilisk is a beast. The Mandalorians Basilisk in TOTJ might look stupid, but regardless it is a Basilisk War Droid. That Virago,which I think looks stupid, isn't a Basilisk. That thing would be destroyed in seconds by the stupid kind.

Even from Canderous discription in KOTOR he speaks of the Beast. I don't like that just because YOU THINK something looks stupid, you feel the right to change it. Of course in the end you didnt' change anything, the Basilisk is still the beast as it should.

I would hope that IF you are making KOTOR 3, you put the ACTUAL Basilisk into the game.

"Regardless, I am certain there are other mistakes. It's a big universe and a big game, you'll find them. I did try to read, play, and watch every piece of Star Wars source material I could find, but I freely admit I make mistakes. "

And the Basilisk was one of them, intentional or not.

<{POST_SNAPBACK}>


Hmmm. Okay, I think you're making a mistake here, but no harm done.

Basically, I think you missed what I said in the previous post - the right to change something never rests with me, it rests with LucasArts and Lucasfilm. I suppose you could blame LucasArts if you want, but I think that would be unfair and frankly, another mistake - as I said in the previous post, please keep in mind that everything goes to Lucasfilm for approval. Everything.

I would strongly suggest that if you have a problem with the basilisk war droid, you don't have to stand for it - contact Lucasfilm, they run the show. Maybe they chose unwisely during the approval process when they saw the concepts. I seriously doubt it, but who knows?

<{POST_SNAPBACK}>


And I'm saying that they agree to everything. KOTOR 2 made the Basilisk the wrong way. Approved or not, LFL went back and approved the Beast in the Mandalorian Article. Definded,pictured, and everthing.

Yet you say LFL changed it, but it was you people who made the concept of the WRONG Basilisk.

Either way there are TWO basilisk now. The Stupid mighty version, and the Virago Star fighter.

I'm sorry you don't like something, but I don't think that gives you the right to remake anything.

I hope whoever Makes KOTOR 3, will put the Stupid mighty version back in.

<{POST_SNAPBACK}>


So just to clarify... how exactly do you have any say in whether anything from the SW universe is changed or not? If the people with Lucas Arts themselves are ok with the change then what you think doesn't factor into whether Obsidian have the right to or not. Obsidian have the right to change it because LA said they could, that's what licencing is all about. The reason Obsidian have to run everything by LA period is specifically so that they can't butcher the SW universe. You may think LA made a bad decision by aproving the new droid, but at the end of the day it's LA's intelectual property and their responsibilty, to do with as they see fit.

I know when you love a series and then some spin-off product comes along that alters the continuity it can ruin the experience for you. It's a fair point, but the die-hard fans aren't the only ones being taken into consideration. If the droid really looks as stupid as you yourself say it does, then wouldn't it look a bit rediculous to see one drop down into a city during the middle of a firefight? As a gamer, I'd rather have an altered version that I can look at with a straight face than an authentic one that totally ruined the atmosphere.

#55
Darth Nuke

Darth Nuke

    (7) Enchanter

  • Members
  • 819 posts

The basilisk war droid version presented in K2 was an intentional departure from the ones presented in Tales of the Jedi, and we are happy, because frankly, those look really stupid. This is much the same reason that many of the designs in K1 are a departure from the ship designs in TOJ, and with good reason. So yes, the basilisk droid version was an intentional depature from the older models, and we take full responsibility. It is noteworthy that LucasArts and LucasFilm agreed with our decision on the first pass, much as they agreed with the decisions made with K1's look.

<{POST_SNAPBACK}>



LA's agrees to everything when it comes to continuity. Proven because they in the Mandalorian Article in issue 80 of insider, sets in stone that the Basilisk is a beast. The Mandalorians Basilisk in TOTJ might look stupid, but regardless it is a Basilisk War Droid. That Virago,which I think looks stupid, isn't a Basilisk. That thing would be destroyed in seconds by the stupid kind.

Even from Canderous discription in KOTOR he speaks of the Beast. I don't like that just because YOU THINK something looks stupid, you feel the right to change it. Of course in the end you didnt' change anything, the Basilisk is still the beast as it should.

I would hope that IF you are making KOTOR 3, you put the ACTUAL Basilisk into the game.

"Regardless, I am certain there are other mistakes. It's a big universe and a big game, you'll find them. I did try to read, play, and watch every piece of Star Wars source material I could find, but I freely admit I make mistakes. "

And the Basilisk was one of them, intentional or not.

<{POST_SNAPBACK}>


Hmmm. Okay, I think you're making a mistake here, but no harm done.

Basically, I think you missed what I said in the previous post - the right to change something never rests with me, it rests with LucasArts and Lucasfilm. I suppose you could blame LucasArts if you want, but I think that would be unfair and frankly, another mistake - as I said in the previous post, please keep in mind that everything goes to Lucasfilm for approval. Everything.

I would strongly suggest that if you have a problem with the basilisk war droid, you don't have to stand for it - contact Lucasfilm, they run the show. Maybe they chose unwisely during the approval process when they saw the concepts. I seriously doubt it, but who knows?

<{POST_SNAPBACK}>


And I'm saying that they agree to everything. KOTOR 2 made the Basilisk the wrong way. Approved or not, LFL went back and approved the Beast in the Mandalorian Article. Definded,pictured, and everthing.

Yet you say LFL changed it, but it was you people who made the concept of the WRONG Basilisk.

Either way there are TWO basilisk now. The Stupid mighty version, and the Virago Star fighter.

I'm sorry you don't like something, but I don't think that gives you the right to remake anything.

I hope whoever Makes KOTOR 3, will put the Stupid mighty version back in.

<{POST_SNAPBACK}>


So just to clarify... how exactly do you have any say in whether anything from the SW universe is changed or not? If the people with Lucas Arts themselves are ok with the change then what you think doesn't factor into whether Obsidian have the right to or not. Obsidian have the right to change it because LA said they could, that's what licencing is all about. The reason Obsidian have to run everything by LA period is specifically so that they can't butcher the SW universe. You may think LA made a bad decision by aproving the new droid, but at the end of the day it's LA's intelectual property and their responsibilty, to do with as they see fit.

I know when you love a series and then some spin-off product comes along that alters the continuity it can ruin the experience for you. It's a fair point, but the die-hard fans aren't the only ones being taken into consideration. If the droid really looks as stupid as you yourself say it does, then wouldn't it look a bit rediculous to see one drop down into a city during the middle of a firefight? As a gamer, I'd rather have an altered version that I can look at with a straight face than an authentic one that totally ruined the atmosphere.

<{POST_SNAPBACK}>


The point is that LA's didn't change anything. Continuity still holds on to the beast BWD. In Star Wars you never change anything, because there are continuity keepers at LFL who have to work all the crap in. You add to continuity. Just because Obsidian changed the design, doesn't mean the Beast is gone.

LFL goes by the,"Ok whatever," way of thinking. Most of em don't probably even know what a Basilisk is, or don't keep up with the EU enough to care. All the continuity problems that have come in the years, have come because LFL agrees to something without looking it up. I've seen it happen dozens of times.

The Basilisk is defined as a beast in the Mandalorian Article. I would have rather seen the beast fall down on Onderon. It's super powerful, and would have made short work of any military with it's claws and numerous weapons. Those generating rods on the front can charge and fire a powerful beam that could punch a hole in even the most power Battle Ship.

However, if you don't like something I don't think you should change the design. I like the beast, and that Beast is a Basilisk. All Chris did was copy a Virago star fighter and put it in the game. He could have made the Beast Basilisk look less silly in the game(Which I don't think it does anyway).

#56
kirottu

kirottu

    Luchador Ninja

  • Members
  • 4619 posts
  • Location:Finland
  • Pillars of Eternity Backer
  • Kickstarter Backer

Well, he is the lead designer after all. If LFL approved his work, he has the right to change whatever he sees fit.

<{POST_SNAPBACK}>


:cool: Thats cool enough for me.

This reminds me of lotr fans who cried when the dancing-singing-gay-hippie was left out of the movie.

#57
CrashT

CrashT

    (1) Prestidigitator

  • Members
  • 42 posts
  • Location:England
  • Pillars of Eternity Backer
  • Kickstarter Backer

The Basilisk is defined as a beast in the Mandalorian Article. I would have rather seen the beast fall down on Onderon. It's super powerful, and would have made short work of any military with it's claws and numerous weapons. Those generating rods on the front can charge and fire a powerful beam that could punch a hole in even the most power Battle Ship.


Which is precisely why it shouldn't have been used. Such a Basilisk would have made the entire concept of fighting your way to the palace pointless as you could just walk up there in that thing.

I think the decision to change the Basilisk was correct but I also think the design they did use was just as silly as the original concept. The Basilisk War Droid in KoTOR2 fits neither the names Basilisk nor Droid.

#58
Drakron

Drakron

    Arch-Mage

  • Members
  • 2119 posts

The basilisk war droid version presented in K2 was an intentional departure from the ones presented in Tales of the Jedi, and we are happy, because frankly, those look really stupid.


I can say that I am not exactly a fan of then and I do think they look a bit stupid.

However if you just name it something else we would not have such arguments, like it or not someone made the Basilisk War Droid look that way and its set in stone.


This is much the same reason that many of the designs in K1 are a departure from the ship designs in TOJ, and with good reason. So yes, the basilisk droid version was an intentional depature from the older models, and we take full responsibility. It is noteworthy that LucasArts and LucasFilm agreed with our decision on the first pass, much as they agreed with the decisions made with K1's look.

<{POST_SNAPBACK}>


Now I can say I am not overall a fan of the "Star Destroyer wannabe with what looks like battle damaga", some ship designs of the comics is wierd but I find the Ship Battleship design quite nice.

http://www.wizards.c...deart/Ships.jpg

#59
NeverwinterKnight

NeverwinterKnight

    (9) Sorcerer

  • Members
  • 1320 posts
  • Location:Canada

And I'm saying that they agree to everything. KOTOR 2 made the Basilisk the wrong way. Approved or not, LFL went back and approved the Beast in the Mandalorian Article. Definded,pictured, and everthing.

Yet you say LFL changed it, but it was you people who made the concept of the WRONG Basilisk.

Either way there are TWO basilisk now. The Stupid mighty version, and the Virago Star fighter.

I'm sorry you don't like something, but I don't think that gives you the right to remake anything.

I hope whoever Makes KOTOR 3, will put the Stupid mighty version back in.

<{POST_SNAPBACK}>


considering people "in charge" at lucasarts and lucasfilm okayed the idea, i think thats more "canon" than you telling us they shouldnt have changed it. i might agree with your stance if lucasarts and lucasfilm told obsidian not to do it, but obsidian ignored them and put in the change anyways. but they got the okay from the PEOPLE WHO COUNT.

The point is that LA's didn't change anything. Continuity still holds on to the beast BWD. In Star Wars you never change anything, because there are continuity keepers at LFL who have to work all the crap in. You add to continuity. Just because Obsidian changed the design, doesn't mean the Beast is gone.

LFL goes by the,"Ok whatever," way of thinking. Most of em don't probably even know what a Basilisk is, or don't keep up with the EU enough to care. All the continuity problems that have come in the years, have come because LFL agrees to something without looking it up. I've seen it happen dozens of times.

you also contradict yourself in your next post by saying first that lucasfilm will say yes to ANYONE and ANYTHING, but then later go on and say that lusasfilm have people to watch for continuity to make sure it is kept. so which is it? if lucasfilm have someone to watch to ensure continuity is kept, then obviously they didnt feel that the change would be a huge detriment to the star wars universe.

#60
Darth_Radnor

Darth_Radnor

    (5) Thaumaturgist

  • Members
  • 416 posts
  • Location:California

The basilisk war droid version presented in K2 was an intentional departure from the ones presented in Tales of the Jedi, and we are happy, because frankly, those look really stupid.

And that's about all the reasons I need.


I'm sorry you don't like something, but I don't think that gives you the right to remake anything.

Well, he is the lead designer after all. If LFL approved his work, he has the right to change whatever he sees fit.
But please tell me who's pointing a gun at your head to buy and play this game. If the continuity 'issues' are so abhorrent to you, you can always get back to reading your vaunted TotJ and forget all about K2. :p

<{POST_SNAPBACK}>


Numberman speaks for me.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users