5 replies to this topic

[Miloch]

Sounds like it might be the same issue as in this thread. Might want to do what I suggested there from a command prompt to see which mods touched the areas.

[Miloch]

The OP in there suggested fiddling with changing area exit names.. how can I do that, and more importantly, where..

The graceful way to do it would be for someone to write a WeiDU patch that corrects things but that could be a lot of work. I also suspect you'll run into more issues due to that mod, which should never have been included in the BWP without more validation. What's more, I don't think you can uninstall it gracefully due to the end biffing you have. But I understand you want to try to fix your game, having gotten as far as you have.

I suspect Creepin used an editor like NearInfinity or DLTCEP to fix the exits in his game. You may want to download one or both of those and ask him for better instructions in the other thread.

[Creepin]

Ok, here's how I fixed this for myself.

As Miloch correctly guessed, I used NearInfinity for that end (I had to notice at this point that Infinity Explorer was way more handy for me to use in this case so I checked everything in it first and only edited in NI as IE didn't allow this). The thing to be on lookout for is inconsistent pairs of "entry point" data in travel trigger of area you're leaving and name of actual entry point of destination area. If I remember correctly whole scope of durlag's tower inconsistences are travels from 1st level to 2nd, 2nd to 3rd, to 4 elemental subareas at 3rd leveland from 4th level to Demon Knight area - that's ones that must be fixed. I noticed accidentally that travel from 2nd to 1st level was broken as well but since I didn't planned to return via stairs I never bothered fixing it neither checked if return from 3rd to 2nd etc level was broken as well.

It's worth mentioning that this issue could be fixed in 2 ways - no matter if you edit travel trigger to match entry point or vice versa. I always edited entry points as they're, obviously, in locations I haven't been yet, and I wasn't sure if there's point in editing locations I've already been in because I'm not quite sure how such locations are processed when you load savegame - from override or from savegame data.
So, when you located what entry points needs to be repaired (again, more easy to do so in IE) open NI, find required areas, and export them somewhere just to be sure if you screw something up you have backup. Then open in NI one of exported areas (Game->Open File, Browse, Open in new window), click on "Edit" tab and scroll down until you'll encounter line for needed entry point. Doubleclick it and change it's name to match data in "entry point" field of corresponding travel trigger of previous location. Close entry point window and save area. Do this for all areas needed and then threw them all in your override folder. That's it, you're ready to go!

Actually, there's another way to workaround this issue for those who're completely unfamiliar with Infinity Engine editing tools. Just open Infinity Explorer, find out what's the name of the area you want to go (you could find out your current area name to give you some hint on what to look for by pressing key you've assigned "Miscellaneous:Location" to in BGConfig) and CLUA yourself there. Then Ctrl+J your party to approximate point where you would've landed if used conventional stairs. Can't promise you won't incorrectly trigger anything in the process though.

Hope that helps

Oh, by the way - questions about megamod issues are best asked in megamod section of the forum

Edited by Creepin, 23 May 2009 - 11:51 PM.