Does anybody have a tip on how to get the friggan talk about his problems with the jedi? I have done anything I can think of...even used the savegame editor and set max influence and still he wudnt open up to me.

 

Plz help

 

-jim

Um, who?

Oh yah I meant the Disciple

 

lol SORRY

 

-jim

had same problem ..

although I sense a Team America revelation .. he was raped by Jedis when he was young perhaps!?

I KNEW they had a reason for taking the children!

Have the talk before you turn him Jedi, or that thread closes. Probably a bug.

He seemed like a likely canidate for some man love

Oh I see. I had the same problem too. Thanks.

Have the talk before you turn him Jedi, or that thread closes.  Probably a bug.

<{POST_SNAPBACK}>

 

Unfortunately I tried this. I even tried holding off the conversation/conversion to Jedi until I'd gained as much influence as possible, and I still got influence failure *sigh*

Is the question still there, or has it disappeared.

I think it just disappears if you reach a certain point of influence or have already gone down certain dialogue trees - Bug perhaps, as mentioned? Dunno.

 

Anyway it's not a very long tree - you ask and he says something, you respond, that's it.

,Mar 17 2005, 03:35 AM]Does anybody have a tip on how to get the friggan talk about his problems with the jedi? I have done anything I can think of...even used the savegame editor and set max influence and still he wudnt open up to me.

 

Plz help

 

-jim

<{POST_SNAPBACK}>

 

That "influence" text is very misleading since it doesn't necessarily have to do with influence at all when it fails. There is an influence check, but it is combined with a check if you've already talked about that subject before. If you've talked about it once, you'll get "influence failure" if you try to talk about it ever again.

 

Since that particular subject is included in the things you can talk with him about when you first run into him in the Enclave Sublevel library, before he joins, chances are you've already talked to him about it before. And as such you get the "failure" message.

 

I assume it was an oversight on Obsidians part that they used two different checks on the same conversation node. Makes no real sense otherwise.