SO ALL ARE AWARE. VERSION 2.0 IS OUT > The Description Page "Changelog Dropdown" is active and will keep track of all update info. PASTEBIN URL Links if extensive changes > Man Those Borders and ALL MTB page content is now in its own dedicated FOMOD > Optional to install Changelog txt files in the FOMOD > Installation/Updating info (per update) will be explained where those changelog txt selection options are in FOMOD > Per line 20 of the v1.8 Pastebin Changelog, MTB source page is not going to become a PatchHub. More detail on that at this Post HERE
Had to disable it for the time being as the Pale outpost conflicted with Heljarchen Farm. Basically the small wooden guard post was inside the guard tower of the Farm upgrade.
Would like options to enable or disable certain borders, in case of using other mods that use the same location or somewhere nearby that would conflist with it's position.
Nothing will be changed per MTB base mod here... Someone would have to make a patch for it "OR" continue off where this Author left off. Their patch would require thorough re-evaluation being it was made up against MTB v1.6. Someone could: fix it for current MTB 2.0 build and submit it back to that patcher, continue off from their patch as base and fix it and ask permission if it could be re-uploaded on another page or can completely DIY and nexus upload it or keep for personal usage Heljarchen Farm - Man Those Borders Compatability Patch
Right on. Nice one.. Just saw it. I don't play myself but its nice to see others patching for this mod bc it does help GoodfellowGoodspring I'm too wrapped up in other things to do MTB dev anymore plus gettin it where its at pretty much meets my initial goals I set out to do... New mods will always produce thus more patches will always be needed so its great to see yours live. Nice one
Anybody running into an issue with freezing in the Helgen-Ivarstead mountain pass? Usually it happens for me right as I'm about to exit or right as I'm about to enter. It's not a CTD. My game legit freezes.
I just now experienced that with the other version of Man Those Borders, I'm kind of thinking it's the DLC-sized vigilant mod. I was hoping it wouldn't happen with this one, but thanks for the comment.
EDIT: I just tried it with this version and it's working as intended. Both are working now. It seems as if Skyrim just has trouble loading in assets sometimes, odd
You would need to load both that and this in xEdit with command argument "VeryQuickShowConflicts" to see the filtered results of only conflicting records it shows. Then, you will know. We haven't checked and unless someone by fluke chimes in with the answer, your better off just checking yourself rather then wait a possible eternity ;-)
There is no direct overlapping conflict between MTB and USSEP... All ussep edits are forwarded where applicable. There is no plugin patch neccessary between the two
You would need to post the error and what info is provided on the error. For anyone to offer advise, that info is needed. Dyndolod has so many possible kinds of errors that can be a result of infinite types of mods combined, without it, nobody knows
There is more technical log data then just that. There are always reasons stated behind the report and that is the valid info needed Loggers don't just say "this mod will cause crash" without the remainder of the reasons why. Its that info that matters which logs. Just put your whole log on pastebin if your unable to discern what info is important behind the 'why' leading up to the moment of the message
Hi, Sorry to bother you about this again but the current version of MTB on Xbox is pretty much unusable. It is acting like a master file and forcing itself to the top of LO, making it impossible to overwrite grass and landscape mods. Furthermore, it seems any existing patches for MTB can’t be enabled as they don’t recognize MTB as the master. I’m not sure if Goodfellow flagged the mod as ESL within the CK but that would explain why the console thinks it’s a master file and why patches can’t find the esp.
I reached out to Goodfellow over a month ago but never got a response. Would you be willing to grant permission for someone else to port a new version? I really love this mod and it has always been a staple on my LO.
That will be up to GoodfellowGoodspring. I have not heard from him nor seen him reply on here for awhile. 2.0 is relatively new and was an update that fixed a few leftover reported issues. Myself at the moment am giving the 2.0 some breathing space to allow the masses to run it and if we get no more reports on any issues, then I can say for sure that 2.0 is final. There is not much point console porting yet until we give MTB and users some time to discover any problems. Hypothetically speaking, lets say 2.0 was ported and then an issue is reported and an update needs to be done again, then its porting all over again which kinda sucks. I am fairly confident though that 2.0 is the final build. That's just my stand and perspective on the whole console porting biz
Given that we have not heard from GoodfellowGoodspring, would you be okay with granting permission for someone else to port 2.0 to console? Totally understand if not but it’s been a few weeks so just thought I’d ask.
Hi there. Its not may place to offer permission in regards to this BUT I TELL YOU WHAT: I will put a Locked Sticky NOTE msg up a bit down the road directed for GoodfellowGoodspring disclaiming that: > MTB 2.0 is FINAL and good to go for console porting. Its been released now for a nice chunk of time and it works well I will also send him a DM on Nexus and his own workshop page (just so he is aware I and users are trying to make contact with him via porting)
That is about the best I can do Once he decides to port it, there will be no place for me really anymore here development-wise. Like a ghost, I will disappear but still pop in time to time to give user help/advisement troubleshooting kinks and what not in post section
Hi, sorry to bother you about this but the MTB port for Xbox is acting like a master file. It makes it impossible to overwrite landscape and grass mods because it forces itself to the top of the LO.
Edit: If you chose to use the CK "flag as ESL" and it converted the mod to a .esl file, it treats it as a master on console. This is making patches impossible to enable.
301 comments
> The Description Page "Changelog Dropdown" is active and will keep track of all update info. PASTEBIN URL Links if extensive changes
> Man Those Borders and ALL MTB page content is now in its own dedicated FOMOD
> Optional to install Changelog txt files in the FOMOD
> Installation/Updating info (per update) will be explained where those changelog txt selection options are in FOMOD
> Per line 20 of the v1.8 Pastebin Changelog, MTB source page is not going to become a PatchHub. More detail on that at this Post HERE
Would like options to enable or disable certain borders, in case of using other mods that use the same location or somewhere nearby that would conflist with it's position.
Someone would have to make a patch for it "OR" continue off where this Author left off.
Their patch would require thorough re-evaluation being it was made up against MTB v1.6.
Someone could: fix it for current MTB 2.0 build and submit it back to that patcher, continue off from their patch as base and fix it and ask permission if it could be re-uploaded on another page or can completely DIY and nexus upload it or keep for personal usage
Heljarchen Farm - Man Those Borders Compatability Patch
EDIT: it's live Y'all
I'm too wrapped up in other things to do MTB dev anymore plus gettin it where its at pretty much meets my initial goals I set out to do...
New mods will always produce thus more patches will always be needed so its great to see yours live. Nice one
EDIT: I just tried it with this version and it's working as intended. Both are working now. It seems as if Skyrim just has trouble loading in assets sometimes, odd
This here : https://www.nexusmods.com/skyrimspecialedition/mods/20474
And if yes, what is correct load order ???
Is it fully integrated?
Thanks.
Loggers don't just say "this mod will cause crash" without the remainder of the reasons why. Its that info that matters which logs.
Just put your whole log on pastebin if your unable to discern what info is important behind the 'why' leading up to the moment of the message
I reached out to Goodfellow over a month ago but never got a response. Would you be willing to grant permission for someone else to port a new version? I really love this mod and it has always been a staple on my LO.
Appreciate any consideration!
That's just my stand and perspective on the whole console porting biz
Given that we have not heard from GoodfellowGoodspring, would you be okay with granting permission for someone else to port 2.0 to console? Totally understand if not but it’s been a few weeks so just thought I’d ask.
Appreciate any consideration!
BUT I TELL YOU WHAT:
I will put a Locked Sticky NOTE msg up a bit down the road directed for GoodfellowGoodspring disclaiming that:
> MTB 2.0 is FINAL and good to go for console porting. Its been released now for a nice chunk of time and it works well
I will also send him a DM on Nexus and his own workshop page (just so he is aware I and users are trying to make contact with him via porting)
That is about the best I can do
Once he decides to port it, there will be no place for me really anymore here development-wise. Like a ghost, I will disappear but still pop in time to time to give user help/advisement troubleshooting kinks and what not in post section
Edit: If you chose to use the CK "flag as ESL" and it converted the mod to a .esl file, it treats it as a
master on console. This is making patches impossible to enable.