OOOOO BBBB IIIII W WW W AAAAA N N O O B B I W W W W A A NN N O O BBBB I **** W W W W AAAAA N N N O O B B I **** W W W W A A N N N OOOOO BBBB IIIII W W A A N NN **************************!!!!!!*************************** Star Wars Obi-Wan Only For XBOX In Depth Glitch FAQ By Wassup1444465 Sites that may post this: gamefaqs, neoseeker, and geocities. Contact me at wassup1444465@aol.com or aim pikadude2491. Version 1.2 Version History Version 1.0-March 30, 2002-I started this thing. Version 1.1-April 6, 2002-Added some glitch explanations thanks to the cheese of life. I also made a small graphic in ASCII for the title. It's DM's saber. Version 1.2- May 26, 2002- Its been a while, but you can't procrastinate forever. In the hateful glitch area/section kind of thing, I added some mail from anyone who has e- mailed me. Thank you all for the help. And keep in mind, you could benefit from reading these, since so far all are glitches. Contents: 1) What is a glitch? 2) Why are glitches in Obi-Wan? 3) The hateful glitches 4) The useful glitches 5) The neutral glitches 6) Credits 7) Legal What is a glitch? A glitch is an error in programming that may cause certain things not programmed in a game to happen. Glitches often come from overloading a video game with data, or a mistake when creating the cartridge. Some glitches may be so frustrating that you want to throw your controller. Well, don't, because they cost a lot of money. Some glitches, however, are your best friends, and you use them very often. Some glitches are just little mistakes that really don't affect game play at all. This guide will run through the glitches that are contained in Obi-Wan. Why are glitches in Obi-Wan? As I said before, overloading a game with information causes glitches. This game, if you haven't noticed, is very good in the graphical area. That probably took an overload, and so it will lock-up now and then. I myself am surprised at how this big amount of information fits into that little disk. So, glitches are glitches, and some, when changed, may just cause more, so they are best left alone. The hateful glitches This part of the guide runs through the glitches that you will come to most likely hate. I will describe the glitches, and state how I triggered them. 1)The Black Death This glitch will immediately kill Obi-Wan, or whoever you happen to be if your in the Jedi Battle mode. I was able to trigger it by throwing an object from behind an enemy that was in front of me, and having it hit me. It killed me right away. Here, in ASCII, is what it looked like. !-----------! !V ! !E ! !O ! !-----------! V=Vase E=Battle Droid O=Obi-Wan What happened was, the vase takes a loop around the droid, and it hits me. !-----------! !V >> ! !E ! ! !O</!=Path mark or boundary line. I think that this happens because the game assumes you hit an enemy, but it is you. Since most enemies die with one hit of the object, you die in one hit. It is a very simple concept. It is a pain to deal with on a hard mission, so watch out. 2)The Void of Doom Well, this isn't really a void, but sort of is. What happens is the game freezes as you're in the loading of a halfway point. It has only happened to me on the swamp level. It only happened to me once, and I was at low health. It can be frustrating if you're new to the game. What I think causes it to happen is being at low health. The game thinks you died as it starts to load the next section, so, of course, it can only have one screen at once, but it tries to bring another. This most likely causes the lock-up, and you will have to reset the game. It may however, just be one of the effects of the data overwrite on the game. 3)The Invisible Injury I have noticed that sometimes a bullet will miss me, but I will take the hit anyway. It is very weird, and can be more than a pain in the battlefield. The most likely cause of this is the game thinking that when a bullet narrowly misses you, you got hit by it anyway. It is probably to little of a distance for the game to understand that it missed. It may also be a misprint on some of the data, thinking there were two bullets instead of one. UPDATE: The Cheese of Life has a theory on this: The game detects collisions not for each face, but with an invisible box around each object. While a plasma bolt may not actually touch Obi-Wan, if it touches a face of the box, then a collision is detected and health is subtracted from the meter. 4)The Evil Lightsaber I came across this during the slow time glitch in the useful glitch section. If you throw your saber and make it hit an enemy, sometimes it may not come back. It will just sit there in one spot, and your enemies will slaughter you. It sits longer than normal, leaving you open to any attack. Eventually, it will come back. This is most likely the cause of over-glitching. The game is thinking that you have your saber, and keeps it in one place. It lags a bit, and then realizes that you don't have it, and then it gives it back. This is my first glitch within a glitch. This part is the mail From: alchemeron This is definitely hateful, and only happened to me once (since I never specifically tried to get it again) and it happened on the "Captives of the Federation" level. After you jump some platforms and get atop the palace, there is a pool of water directly ahead, past a grove of trees. To the right you can climb up and kill two sniper-droids. Well I jumped into the water (lightsaber off), and I think I activated my lightsaber just before I hit the water (or just as). Instead of automatically deactivating as you swim, it didn't. It stayed on and I was STUCK IN THE WATER. There was absolutely no way to get out. The game would not allow Obi-Wan to climb out of the water with his lightsaber on, and there was no way that I could turn it off. I suppose the game didn't recognize that I was swimming in the water to allow me the to make that small hop out of the water and grab a ledge, but at the same time, it wouldn't let me deactivate the saber (perhaps it assumed that since there's no way you're supposed to be able to activate it, then there's no need to have the ability to deactivate it?). I tried for quite some time to get out of the situation, but to no avail. I had to re-start the level. my comments: very odd indeed. I suppose your explanation seemed right, but also, I think you aren't able to activate it in the water, as you said, and the game thought there was a bug and for the safety of an xbox, froze itself. From: greemville I beat Darth Maul without completing all of the secondary objectives without a problem. I than decided to try the level again, this time going after the secondary objectives. I got the first four, life, force, accuracy, and nav points. When going after the timed event, I was able to get Darth Maul down to one light saber fairly quickly. At this point Darth Maul lost his light saber completely and he stopped moving. I could take whacks on him but he wasn't registering any damage, just being forced back. My comments: this happens in jedi battle, except it continues on going through the game. I thinkyour not supposed to kill maul like that, and data got mixed up when you beat him, so it thought you did beat him while it knew not to go through a cutscene. I myself tried to reenact what you say happened, and once managed to chip health when he is invincible and his saber is supposed to cut, but not fast enough to kill him. From: redn02 In the battles with the Jedi Masters thereis a nuetral glitch. After you defeat them do a force jump before the cinema starts playing. If you do it correctly as the Jedi Master speaks to you the camera will be pointed at the ceiling. My comments: hmm. The game probably thinks that you are staying still, yet it wants the camera to be pointed at you like normal, so it points at the ceiling. From: chrononerd176 very stupid glitch called: FLOAT IN AIR but it is while your dead... ok so in some level you just jump off of a cliff and when you are in the air you will die and start hovering a bit. My comments: lol, I think that is obvious, but anyway, the game needs to make you die, but it doesn't have enough memory to make a floor very far down, and your not supposed to fall off, so that is what happens. From: Bugeater93 I don't know what caused this one, but I was in the first Naboo level and I ended up on a ledge and I was running along it towards a roof and I jumped. Instead of landing on the roof, as I expected, I actually fell through the roof and died. I didn't fall all the way to the ground, only through the roof (about 4 feet down in Obi-Wan's world...not even the length of his body), yet it still killed me. I haven't tried to recreate it because I can't remember exactly where I was, I just got the game last week and still haven't beaten it. There was also another freezing glitch I had that occurred during A Queen in Peril. It happened after Obi-Wan meets up with Qui-Gon and they're on the overpass walkway thingy waiting for the queen and the droids and assassins and everyone to get there so they could ambush them. Qui-Gon says "Let's go" or something to that effect, and I jump down along with him, but the game freezes when I hit the ground. It happened two or three times before I got pissed off and took out the game and cleaned the surface according to the way it says in the manuals. It worked and now it doesn't freeze during that part. I also have a few problems with the force meter staying on...like I'll want to open a door or do flips and cartwheels and crouch, but the force meter will be stuck on and I'll end up force throwing or force jumping. Sometimes when the force is on and I hit the force button again, it'll turn off...sometimes it'll stay on...and other times, no matter what I try, the force will stay on until it's ready to turn off. It's got a mind of it's own or something. Also, when you catch on fire from one of those fire grenades the tusken raiders throw at you, are you supposed to lose life every time Obi-Wan makes that 'pained' noise? Sometimes I don't lose any life at all when I catch on fire and other times I just lose a bit of life from the grenade exploding, but never from being on fire. Is this another glitch? Anyway, I think that's all I've got for you now. Thanks for writing all this stuff down and posting it...you've been very helpful. My comments: Your welcome for your time. Your fire story: I think it just stings obi-wan enough when he is on fire, but not always the same as to him losing life. The force meter, maybe you are pressing the wrong buttons. Even I do that every once In a while, and maybe you are letting go of the trigger. Or, the alternative, maybe your disc or box needs repair. And I'm not sure, but possibly, you force jumped when Qui-Gon said the lets go, and it killed you, or your disc was dusty and scratched, and you need a new one form the scratches. And I should thank you for informing me of this. Perhaps I should tell Lucas Arts about these things. Boy, I cant imagine the look on their faces when they find an e-mail like that. From: hilbe I've been playing this game nonstop for about 3 months now (trying to get all the medals, I'm 3 medals away). I've come across quite a few big bugs. Here is one: Go to the level with the Tusken Raiders. You'll cross a big bridge just after a downed tie fighter and the tuskens will fall down with some rocks. Kill them and force push the HUGE block across the bridge and past tie fighter (there is a secret up and to the right, if you want to use the big block). I pushed it to the area just before the jumps and the mammoths, there is a out jutting rock. I jumped onto the big block and up onto the ledge. Apparently you aren't supposed to do this, because you can walk into infinity (graphics get all weird). Check it out.... My comments: I guess you aren't supposed to. You are most likely going beyond in game boundaries, and so there is nothing left but for the game to let you walk into infinity. Or is it just Jedi Meditation. ;-) If you have anymore glitches that are hateful and are not listed here, please e-mail me at wassup1444465@aol.com and I will credit you if it's a NEW glitch. The Useful Glitches This part of the section lists how to perform certain glitches, and what may cause them. These glitches can help you through the game; so only use them if you don't mind the help. 1)The Matrix Everyone likes the slow motion. But it only lasts for a few seconds. However, it can last for the entire level or section of a level. Be at full force, and hold the force button the entire time, or it won't work. First, slow time. Then, immediately throw your saber. As time reverts to normal, wait until your force meter reaches just a bit below halfway full. Then, slow time again. After the saber comes back and your force completely drains, and you're sure that the normal slow duration is over, you can let go of the force button. If done right, the game will sound sort of like normal time, but sort of like slowed, and you will move in slow motion. To get out of this, slow time again. Use the lock-on and jump to the side, and do acrobatics, and it is like the Matrix. This glitch may be caused by the game over thinking. Since it will have to keep track of all of your actions, it gets too tired to realize that time is still slowed. But when it slows again to get out of the trick, it remembers to revert it to normal. Big thanks to Mr. Elf on this one. He will be credited. 2)Super Saber This glitch is useful on any Naboo level with force fields, and on the Darth Maul level. You need to have your lightsaber out, and then walk as close as you can to the force field. Throw your saber, and it will go through it, and damage any enemies you see. Here it is in ASCII text again. !---------! ! ^ ! !*^*******! O= Obi-Wan ***=barrier ^=saber thrown ! O ! ! ! !---------! This is probably the game thinking you're past the force field, even though your not. You have to be smack up against it, which also supports my reasoning for it. Big Thanks to Super Nova for this. He will be credited later. The Cheese Of Life has something to say: The force-field clipping does not apply to the lightsaber. Either the programmers were lazy, or they simply forgot to apply this clipping to the object. Without throwing the lightsaber, this error can easily be seen while playing the Darth Maul level; if you move Obi-Wan to the edge of the force field and turn him, the tip of the blade will penetrate the force field. 3)The Penalty This glitch makes all of your enemies die instantly. I only got it to happen once, though, but had a similar effect several times. Do the Matrix on the Secrets of the Black Heth level, and when the second wave of fighters come, force push them when they are still on their platform, and they MAY die. It only worked with me once, and the game made funny sounds as they all collapsed, and then resumed to normal. I guess this is caused by the game thinking you force pushed them all into the platform, even though you didn't, or that you were up there and hit them. I don't know why this happens, but it sure is useful. ;-} Once again, if you have any USEFUL glitches, send them to me a wassup1444465@aol.com or AIM me at Pikadude4491. The Neutral Glitches These glitches are just in the game, and don't effect the gameplay whatsoever. I will not list reasons for them. I will, however, post explanations. 1)Frozen Fire This glitch is hysterical. It most commonly happens in Jedi Battle, although some say it happened during Darth Maul. Sometimes, when you beat your enemy, instead of going into a death sequence, they just stand there. You still get the kill, but they were frozen in a fire, which means stuck in a situation. 2)The Invisible Thief Sometimes, if you do the slow-motion glitch (the Matrix) and kill a battle droid at their arm so their gun flies up, it will look like it is being pulled or carried as it "runs away". It is just a little thing I noticed to make the game more amusing. 3)The Invisible Droid During the slow motion glitch, I went to Betrayal. I killed a droid who had an electroblade (the blue droids with torch thingies), and he collapsed, but the blade stood in mid air like he was holding it. I walked into it, and took no damage. I played the level again doing the same thing, but when I walked into it again, I did take damage. It wasn't a lot, and it wasn't hateful either. It was just noticeable. Thanks to the Cheese of Life for this next one (in his perspective): Once, when my health was almost depleted, I used Force Jump; while I was in the air, a plasma bolt hit me; I fell to the ground and died...but I continued to stand. This has also occurred while my health is greater; I fall to the ground, then stand, unmoving, as my enemies slaughter me. That is all I can think of concerning glitches in this game. E-mail me if you have any more neutral ones. Credits: Super Nova JM and Mr. Elf for two of the glitches. Cheese of Life for a third and some explanations. Legal The usual. You don't post my stuff on a site for profit. You don't rip my name from this, call it yours, and sell it, ect. If you e-mail me asking for it on your site, as long as the site is non-profit and I have the link to it, I will grant permission. (c)2002 Note: I spent a while putting up more than 10 glitches, and an explanation of each, plus the definitions of glitches. Please follow my rules above.