14 replies to this topic

[Chevalier]

A know (forgotten?) bug. Was it fixed? Did you use all the patches??

I use a CLUAConsole:MoveToArea("[location number]"


Edit: I have not yet got there this play though will let you know when I do.

Edited by Chevalier, 24 September 2004 - 12:56 AM.

[seanas]

please tell me you didn't experience the Nalia's Keep bug, guest? that bug has been fixed so many times its not funny... it was, for example, fixed in the BP-BGT-NEJ 3.13 patch

could you detail which installation you are using (BGT, BP-BGT, BP-BGT-NEJ) and how you installed?

[solomonk]

please tell me you didn't experience the Nalia's Keep bug, guest?

sorry, but i have same problem...

could you detail which installation you are using (BGT, BP-BGT, BP-BGT-NEJ) and how you installed?

i use BP-BGT-NEJ-313... and can`t enter in Nalia Keep

[Arturcic]

Same here, but CLUAing into the keep doesn't solve the problem, cos the map is as if Torgal were dead and the keep were my stronghold. All chests empty, no enemies, and the Major Domo telling u about the keep's afairs. Any solution?
Thx.

[seanas]

yep, that solution is easy: you CLUA'ed to the wrong area. you want AR1302; NOT AR1306.

[Sir BillyBob]

Same here, but CLUAing into the keep doesn't solve the problem, cos the map is as if Torgal were dead and the keep were my stronghold. All chests empty, no enemies, and the Major Domo telling u about the keep's afairs. Any solution?
Thx.

CLUA solves the problem if you go to the right area.

You need to move to AR1302, which will drop you next to the forge. If you went to AR1306, this is the area after you earned the keep.

I don't understand how you all get this bug. I and Horred both had never encountered it. I know these maps well and this weird bug was never a problem. Okay, time to take a look...

These globals can lock the door.
Global("RoenalControl","GLOBAL",1)
Global("NaliaKeepControl","GLOBAL",1)

The first one shouldn't be possible yet. I assume the second comes from a Nalia dialog, I will have to go through her dialog files.

Is Captain Arat in the palisade? He won't be if the above are true. What are you all actually seeing on the map? Cyclops? Bridge up or down? Captain Arat? I need to know what the game thinks is going on. By default, that doorway should be available to you. You don't even need Nalia or the captain to tell you about it.

[Arturcic]

In the map are the cyclops, Arat and the bridge closed, NaliaKeepControl is 0, same as RoenalControl.

[Sir BillyBob]

In the map are the cyclops, Arat and the bridge closed, NaliaKeepControl is 0, same as RoenalControl.

Okay, the only way I think I can do this is to look through your game file. I need a saved game of your team on the AR1300 map, without talking to the captain or trying to open the secret door. Send it to [email protected]. I will see what the other globals are so I can try to rule out a script problem. At this point we don't know if it is the area script or a bad transition between the two areas.

[Rattledagger]

Have a vague recollection of reporting this bug half a year ago or something before the old forums went belly-up, and haven't played BP since then, but AFAIK the v3.13-patch was total crap for this bug, being worse than unpatched. :bash:


Anyway, to fix this bug, extract ar1300.are from the original AREAS.BIF-file and use this instead of the buggy supplied by BP.

[Sir BillyBob]

Hi,

I also had this bug in my game. The problem I have found is that the trigger point Tran1302a, (which is the secret door to the basement), is setup as Proximity trigger. If you change this to travel trigger, it will work. You can do this with Near Infinity.

I did this in my save game after I had opened the "door" and could enter.

The globals seems to be setup ok.

And some of us have never had this problem, before or after 3.13. So I don't know why some of you are seeing it. Proximity or travel, it can't change based on moon phases (can it?). So we may want to watch this for awhile.

[Rattledagger]

Well, if remembers correctly the only problem before v3.13-patch was random crashes while sleeping outside Nalias keep, but as already mentioned it's some months ago...

Anyway, to prove the v3.13-patch has the wrong "proximity trigger" instead of "travel trigger" very easily, download the patch, extract to a temporary directory, navigate into BP-BGT-NEJ_PATCH313\auto and copy ar1300.are to your override-folder, and afterwards load up NI and look on ar1300.are...
Double-click under "Points of interest", Tran1302a is now... "Proximity trigger (0)" (2nd line)

And you're standing outside Nalias keep :bash: trying to enter...

[Sir BillyBob]

Well, if remembers correctly the only problem before v3.13-patch was random crashes while sleeping outside Nalias keep, but as already mentioned it's some months ago...

Anyway, to prove the v3.13-patch has the wrong "proximity trigger" instead of "travel trigger" very easily, download the patch, extract to a temporary directory, navigate into BP-BGT-NEJ_PATCH313\auto and copy ar1300.are to your override-folder, and afterwards load up NI and look on ar1300.are...
Double-click under "Points of interest", Tran1302a is now... "Proximity trigger (0)" (2nd line)

And you're standing outside Nalias keep :bash: trying to enter...

Rattledagger, I fully agree that 3.13 gave us this bug, but I thought it was around long before that. Horred had mentioned that he couldn't find the problem and I copied from the area for my mod (obviously during a 3.12 build). So it looks like the bug is consistant for all as of 3.13. I just did a clean build with the new s&h patch and see that the door is still broken.

So here is a fix for anyone that needs it: