Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Name:
Email:
Subject:
Message icon:

Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What color is grass?:
What is the seventh word in this sentence?:
What is five minus two (use the full word)?:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: Kulyok
« on: July 08, 2006, 11:40:49 AM »

It's completely fine. I am sorry, I should have made myself clearer: in my last post, I was reassuring users who have both Xan and multiromance patch installed and are now concerned, rather than answering you. Sorry. :)
Posted by: cmorgan
« on: July 08, 2006, 11:31:10 AM »

Sorry, Kulyok, I spoke out of turn ::). I hereby amend that last post to "most mods have troubles; Xan is one of the few that have controlled for a multi-romance path" :)
Posted by: Kulyok
« on: July 08, 2006, 10:32:00 AM »

Quote
I think it is safe to say that any part of multi-romance patches seriously increase the chances of really strange things happening in any installed mod.

Xan BG2 NPC has certain safeguards for this sort of thing, so, yes, your Xan is safe and sound even with multiromance installed. It's been tested extensively, too - the only thing you'll likely miss if you have multiromance installed is a certain graveyard cutscene. The final outcome is the same, however.
Posted by: cmorgan
« on: July 08, 2006, 09:59:36 AM »

I think it is safe to say that any part of multi-romance patches seriously increase the chances of really strange things happening in any installed mod. It appears that many modders even put special scripting in to shut down other active romances to counteract someone trying to do a multi-romance; there are just too many odd pathways/conflicts/potential for trouble to be able to script this sort of thing. Thus the advent of the Romance Player2 content mod, where more than one player gets a chance at romance (just not Player1!).
Posted by: berelinde
« on: July 08, 2006, 12:19:12 AM »

Ah, I see that is the issue. Last time I was playing, I did have multi-romances installed, which is why Anomen kept hitting on pc.

During a recent reinstallation, I elected not to install the multi-romance component, so now Anomen should stop bugging pc.

Thanks for the clarification.
Posted by: Kulyok
« on: July 07, 2006, 01:47:55 PM »

I fully agree with you, and this is exactly why Anomen romance stops the very minute bonded path with Xan begins.

The other Xan romance(a romance that starts in BG2, non-bonded path) continues alongside Anomen's, and stops, when Anomen romance becomes committed. If PC declines Anomen, Xan romance continues and carries over to ToB.

(However, if you have Ease of Use multiromance installed, bonded path can and will continue alongside Anomen romance - committed. Accept consequences at your own risk, however.)
Posted by: berelinde
« on: July 07, 2006, 12:42:12 PM »

First, let me say that I really admire the way you offered 2 completely different romances for Xan, depending on whether or not someone finished BG1 NPC project with Xan in the bonded path or whether the romance did not go that route.

This is kind of a sensitive subject, but Anomen's romance starts and continues whether or not the pc is in the committed phase of the Xan relationship. I realize that Elven marriages might be more or less open, but human relationships are less so. Especially given Anomen's reaction to Maria's infidelity.

In other words, once Anomen notices that <CHARNAME> and Xan are clearly more than just friends, he might be inclined to discontinue his attempts at winning <CHARNAME>.

Just a thought.