
Darth Nuke
Members-
Posts
807 -
Joined
-
Last visited
Content Type
Profiles
Forums
Blogs
Everything posted by Darth Nuke
-
Yeah it is a tiny reference to Jango, but not Boba. Kreia is wrong about the Mandalorians though. They never die.
-
The List of Continuity Mistakes
Darth Nuke replied to Darth Nuke's topic in Star Wars: General Discussion
http://www.joecorroney.com/cgi-local/image...jpg&img=&tt=img that thing in the top right hand corner doesn't look like a Virago Star Fighter to me. -
The List of Continuity Mistakes
Darth Nuke replied to Darth Nuke's topic in Star Wars: General Discussion
That obviously depends on who you ask. My point exactly. Thus, you cannot argue that just because Insider contradicts K2, K2 is wrong. Only the Sith War comics are a valid reference for that, since in the other two, they are just copy-pasting what was displayed in the comics. It would be absurd if in some article they made up their info. However, for creative reasons, it's not. You don't know that. <{POST_SNAPBACK}> Sign up on the offical Star Wars board, and see for yourself. If you don't believe me. Oh and the EG,SWC,and Article contradict KOTOR 2. Get it right. And the Essential Guide and Article are both continuity sources used by the continuity keepers. Both are offical. SWC show the Basilisk, EG tells what it does, and ARticle defines what it looks like(and does). All are continuity sources. (don't believe me, ask LFL) And actually I do know what I'm talking about when it comes to things being offical. Dark Horse has done it before. -
The List of Continuity Mistakes
Darth Nuke replied to Darth Nuke's topic in Star Wars: General Discussion
Everything in that Article was created to complete the Mandalorian history-. The continuity keepers took all the info and put it in the holocron. So when you ask, "what does a Basilisk look like?" Your answer will be," A Beast." Not the Virago Star Fighter, and Insider has as much strenght as the games, novels, and comics. Also the BWD were created in the Sith War comics. So now 3 sources have the Beast War Droid as continuity: 1. Sith War comics 2. Essential guide to Droids 3. Mandalorian Article Virago only has one. Bad thing is, if Dark Horse(comics) were to get ahold of KOTOR 2 and make an adaptation. The Basilisk would indeed be returning to it's original form. Much like will happen when Dark Horse returns the VOTDL to it's original state in the upcoming Tales KOTOR comic. -
The List of Continuity Mistakes
Darth Nuke replied to Darth Nuke's topic in Star Wars: General Discussion
The Virago Contradicts continuity. However it is continuity still, but this just means that this Virago is a version of a Basilisk. But not the actual battle ready Basilisk. It's probably some covert spy vihicle they call a Basilisk. That or Kex didn't know what he was talking about. -
The List of Continuity Mistakes
Darth Nuke replied to Darth Nuke's topic in Star Wars: General Discussion
Because the article defined what a Basilisk is. -
The List of Continuity Mistakes
Darth Nuke replied to Darth Nuke's topic in Star Wars: General Discussion
From Star Wars Insider issue 80: Basilisk War Droid: "Looking like a cross between a Karran beetle and Zalorian rock lion, the Basilisk War Droids were created by the technologically minded Basiliskans, arrogant reptiloids who poisoned their own planet during the Battle of Basilisk. Afterward. th tech- hungry Mandalorians greedily looted countless war droids." All of this was approved by LFL license of course. :D NEVER: LOL. This issue came out in a month after KOTOR 2. Clearly LFL went back on their word. The beast is offical. -
The List of Continuity Mistakes
Darth Nuke replied to Darth Nuke's topic in Star Wars: General Discussion
LOL http://www.galacticholonet.com/Droids/Basi..._War_Droid.html First created in the Sith War comics -
The List of Continuity Mistakes
Darth Nuke replied to Darth Nuke's topic in Star Wars: General Discussion
Actually for Star Wars many things are set in stone. The Basilisk War Droid is one of them. I mean Canderous even rode the Beast in KOTOR. In essence KOTOR 2 couldn't even keep up with KOTOR's continuity either. -
The List of Continuity Mistakes
Darth Nuke replied to Darth Nuke's topic in Star Wars: General Discussion
Because all things are continuity in Star Wars. Unless labeled as infinites -
The List of Continuity Mistakes
Darth Nuke replied to Darth Nuke's topic in Star Wars: General Discussion
Are you talking about the same LFL who approved the BWD in KOTOR 2, and went back and approved the original version for the Mandalorian Article? Which in the end makes offical the way a Basilisk looks. So in reality the Basilisk in KOTOR 2 is still wrong, seeing as the stupid version is now offical. Yeah LFL gave the ok to the Virago Star Fighter being used in KOTOR 2 in place of a the real Basilisk. Cool, but continuity will always concider the Beast as the true Basilisk War droid. Just like the Valley of the Dark Lords. -
The List of Continuity Mistakes
Darth Nuke replied to Darth Nuke's topic in Star Wars: General Discussion
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. 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. <{POST_SNAPBACK}> No I'm not. LFL license has continuity keepers. Keepers of the holocron. These continuity people didn't approve the concepts, some other section of LFL did. Either way the Beast is set in stone. The Beast is a Basilisk, not the Virage. That virago neither was a droid, or beast. IT's wrong, and isn't a Basilisk. It's a virago star fighter. -
The List of Continuity Mistakes
Darth Nuke replied to Darth Nuke's topic in Star Wars: General Discussion
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). -
The List of Continuity Mistakes
Darth Nuke replied to Darth Nuke's topic in Star Wars: General Discussion
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. -
The List of Continuity Mistakes
Darth Nuke replied to Darth Nuke's topic in Star Wars: General Discussion
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. -
The List of Continuity Mistakes
Darth Nuke replied to Darth Nuke's topic in Star Wars: General Discussion
Well... the tomb of Marka Ragnos is in "both" Valleys... maybe the one we see in KotOR is the back entrance. " . <{POST_SNAPBACK}> Not likely. His body is in a huge room filled with great gold treasures. The body itself is entombed in a Statue of him sitting on a throne -
The List of Continuity Mistakes
Darth Nuke replied to Darth Nuke's topic in Star Wars: General Discussion
They could have used a closed cokpit version. Also if they were wearing Mandalorian armor they wouldn't have had a problem either. Canderous speaks of how when he entered Althirs atmo that he only had his armor to protect him during the reentry. That's why Basilisk and Mandalorians are cool, because they do crazy stuff. Either way that Virago isn't a Basilisk. Also the Valleys can be different, because Marka Ragnos tombs in located in the Valley of the Dark Lords. Yet his ACTUAL tombs in the image of himself. You can't just walk up to it like in KOTOR/KOTOR 2. You have to climb a long row of steps to get to the entrace. The valley is just two buildings in KOTOR/KOTOR 2. I actually looked over the edge, and there were no tombs. The Valleys tombs stretch for miles in the Canyon. Developers should abide by continuity. Making stuff look a little modern is fine. KOTOR takes place 40 years after The Sith War, and lots of things could have changed. But the same isn't so for the VOTDL. It's past and future have it as a series of tombs laid out in a Canyon. Of course I could care less about the Valley in reality. The KOTOR tales comic will set things straight with that. Yet a Basilisk is a Basilisk, and that Virago aint' one. -
No need for a new character. A new PC would be bad story telling. Especially in trying to end a trilogy.
-
The List of Continuity Mistakes
Darth Nuke replied to Darth Nuke's topic in Star Wars: General Discussion
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. -
I love idea threads. It's the only reason I can write down my ideas as many times as I wish. Exile should return as the PC. Not that I think he suits the position, but because it seems that KOTOR 3 is leaning towards him anyway. I do hope that Revan will still have a big part, and perhaps the Exile and Revan deal with the True Sith Lord(voiced by Christopher Walken) together. As far as party members go. I'm sticking with the original KOTOR 2 ending that never made it. Party Members: Bastila Jolee Falleen Bothan Feeorin HK(with remote and HK-51 gang) T3 Dustil Onasi Non Party members: Mandalore Carth Admiral Dodonna Cassus Fett: New bounty hunter Vima Sunrider Yuthura Planets: Coruscant Mandalore Alderaan Ithor Hapes or Korus Major Manaan or Unknown World Iago(optionial) New Planet New Species: Kel Dor Falleen Bothan Mandallian Giant Togorian Morgukai Lepi Feeorin Influence system changed or done away with. Changed, meaning that influence can be gained regardless of alignment. Better planet Maps. Abide by the rules of continuity. Basilisk should look like a Basilisk.
-
The List of Continuity Mistakes
Darth Nuke replied to Darth Nuke's topic in Star Wars: General Discussion
And by some miracle when modified, the Basilisk looks exactly like a Virago Star fighter. Modified, ha, you'd think something from the actual Basilisk War droids parts would have been left behind. No claws,no generator rods, no beast form, nothing that makes a Basilisk a Basilisk.Please!! <_< You can't just take a ships and call it a Basilisk War Droid. The Closed pit models would look exactly the same with just a cover over the rider. A Basilisk War Droid is named and made to look like a BEAST. Even the Mandalorian Article in issue 80 of insider, set in stone what a Basilisk is. That THING in KOTOR 2 is not a Basilisk. Plain and simple. It's wrong, just like the Valley of the Dark Lords. Canderous clearly rode the Silly looking beast Basilisk War Droid. Not the Virago Star fighter. -
It's not hard to knock both Revan and Exile in level in a logical way people. To want a new PC is to what everything to repeat it self once again. New PC somehow gets Hawk and Hk New PC has some wierd force problem New PC has to be trained New PC has to butt in on a war that isn't his
-
Should the "real" ending be restored?
Darth Nuke replied to Dehumanizer's topic in Star Wars: General Discussion
Hell yeah, patch up the ending. Regardless of all the stuff put back into it, it's still a cliffhanger. A much better cliff hanger though. One where we know what happened to the characters, and such. A more complete cliff hanger ending -
The List of Continuity Mistakes
Darth Nuke replied to Darth Nuke's topic in Star Wars: General Discussion
THAT basilisk is the only Basilisk. That little Virago would have been destroyed in seconds against an ACTUAL Basilisk War droids. It's those generating rods on the front that are the trick. They charge up to make one big blast that can turn even the mightest ship into a flaming hulk. -
Continuity says so. Csilla is in the unknown regions, the area is never exploreed my many.