Closing Anomen's Romance Variable Correctly

[jastey]

Anomen romance misses some closing variable settings, leading to the romance playing on until it is just silently set to "committed" although the PC most definitely stated that she doesn't love him back.

This is another "only makes bugs in combination with mods" instances.

This is also true for oBGII. Should I open a second thread there?

 

Following instances in BANOMEN.dlg:

Crucial:

State 399: needs ~SetGlobal("AnomenRomanceActive","GLOBAL",3)~

Anomen leaves here forever, so the romance needs to set to broken to give other romances a chance.

State 464: needs ~SetGlobal("AnomenRomanceActive","GLOBAL",3)~

PC just rejected Anomen's love proposal (2nd night talk) (~The future is too uncertain, and I have too much else that I must do. I cannot accept your pledge.~). This is definitely what can be called setting an ending to Anomen's courting and needs a closure because later, the game just sets AnomenRomanceActive to 2, scruwing any other active mod romance.

 

Open for debate

(the Anomen romance is clearly designed to have him bed the PC (or at least offer it) before falling for here. Calling the romance committed at this point is clearly a matter of definition. It would make the whole handling of mod romances much easier, though.)

State 434: could get a ~SetGlobal("AnomenRomanceActive","GLOBAL",2)~

This is after HC accepted first love making night.

 

State 437: could get a ~SetGlobal("AnomenRomanceActive","GLOBAL",3)~

This is after HC rejected 1st lovenight.

[CamDawg]

I think the two "debatable" changes are solid. All of these are in.

[jastey]

Thanks!

[jastey]

btw: in case they aren't these could also go into the BGIIFixpack.

[CamDawg]

Yeah, when we get EEFP out the door I'm going to crosscheck the new fixes against BG2FP and IWDFP and see what can be backported.