I cannot go that way, I should turn back

[timmygrover]

So I've got a weird problem where when I try to exit the imp. sewers at the start of the game, as soon as I exit the sewer door to the imperial isle I get a message, "I cannot go that way, I should turn back." I'm running something like a hundred mods, so I can totally see why I'm having problems but I'm not sure where. The only mod I'm running that should effect the imperial isle directly is UL imp. isle. As far as mods I've not successfully run before I'm trying "the deserts of aquina" "Better cities" (though i've run impeREAL before) "Barthom" "Cyblades" "Tears of the Fiend" "RTT" and then some little armor mods and such.

 

Any ideas?

[David Brasher]

You have so many mods it would be difficult to isolate your problem. It sounds like one of your mods went to TES CS\World\Region\RegionEditor\Tamriel\WaterfrontRegion or CityIsleRegion and checked the box Border Region. That box needs to be unchecked. I don't know if you could make a mod to patch the symptom rather than try to track down the problem. If you are a bit of a modder, and made this mod to correct the problem, it would need to go last in your current load order. (Mods you add in the future can come after it.)

 

If we went by the load order idea, it would seem like the last mod in your current load order would have to be the bad mod. It might be worth investigating. But that sounds too simple. A change early in the load order would be dominant over an absence of change later in the load order. So I guess the last mod in your load order would be no more suspect than the others. Maybe if you made a patch mod which made a slight change to the borders of the WaterfrontRegion and left the box unchecked, and placed this mod last in your load order, it would register as a change and be dominant over the previous bad change which is causing your problem.

 

I guess you could open all your mods one by one and inspect for the improper border region check box.

 

Otherwise you can take the usual approaches:

(1) Hope someone knows exactly which mod causes that problem. (Not often effective.)

(2) Tweak your load order.

(3) Systematically remove mods and play-test until the problem goes away and you isolate the bad mod.

 

Good luck!

[bben46]

Usually you get that message when you try to go outside of the vanilla game boundaries. Try removing the boundries. There are several mods for that, but if you don't want another mod cluttering up your list, disable boundaries in the Oblivion.ini file

 

find the entry bBorderRegionsEnabled=1

change the =1 to =0 and save it.

[timmygrover]

Yeah, I tried removing the borders before I even posted, and then after I posted I deactivated all the mods in obmm and guess what, it still didn't work! so that was fun. I guess I need to start from scratch and test play after i install each mod to find the problem.

[Pronam]

That's odd..did you try using another savegame.

Next note, which .ini did you change...the one at oblivion or the on at your user-folder? As they are 2 different things.

[Branimirzg]

I had same problem...fixed it by deactivating one mod

 

It think that is was OOO

 

I had 5 mods

 

OOO

Oblivion XP

ExnemRuneskulls

Bag of holding

?

[kasurequiem]

I had this same problem and fixed it by disabling the "Stirk" and "Passenger Ships of Cyrodil" mods

[bobbyskel78]

Fire up TES4Edit. Start scrolling through obvious places; world spaces, interiors ... take note of areas highlighted as ya crawl through the tree and which mods are taking precedence over that area (last in sort order of the modified area)

You may luck up and find the problem in a conflict detector. In such situations, the one you want to take priority should be loaded last and also fall lower in the hierarchy ... some just aren't compatible and require a patch.

Fire up the CS once ya think ya found the culprit. Make the culprit the active file. Go to the 'cell view'/'interiors'. active files are always listed first, so ya should see the respective imperial sewer in green or the area close to it.

setting the ini command bEnableBorderRegion=0, turns the borders off. might want to look that up in the CS w/ a potential culprit that's making changes to this game setting ... i would have to guess something that has added something near that area.

not sure if it would work, but you could try and write a simple script:

scn TamDisableBorder

begin gamemode

 

if getgameloaded || getgamerestarted

   con_SetGameSetting bEnableBorderRegion = 0  endifend

Edited June 6, 2020 by bobbyskel78