Errors when changing cell's location or refs known to a location

[mattbeckpdx]

I've attempted to mod in settlements a couple of times now and run into variations on this issue and no sense of how to resolve it.

 

Basically, if there are refs that are in one location and you move them - or if you change the location that the cell is assigned to you start getting errors in the log.

I don't see how to safely do this, but surely it must be done in other mods.

 

Banging my head around in CK and FO4Edit hasn't gotten me anywhere.

 

Anyone have any suggestions on what stupid thing I've done wrong here?

 

Thanks!

 

Example: Tried setting up a settlement at Mass Gravel and Sand, and it's working but CK is complaining.

MASTERFILE:	<CURRENT> 		LCTN 'MassFusionCoolantDisposalLocation' (001680C6)	Special ref 'MassGravelAndSandMapMarker' (0002BA2E) no longer in location.
MASTERFILE:	<CURRENT> 		LCTN 'MassFusionCoolantDisposalLocation' (001680C6)	Exterior cell (-5, 6) in world 'Commonwealth' (0000003C) is no longer tagged to this location.
MASTERFILE:	<CURRENT> 		LCTN 'MassFusionCoolantDisposalLocation' (001680C6)	Special Ref 'LvlRaider_Handmade_MG' (000A7237) is not in the Special Ref data.
MASTERFILE:	<CURRENT> 		LCTN 'MassFusionCoolantDisposalLocation' (001680C6)	Special Ref 'MB_MassGravelCenterMarker' (02004C55) is not in the Special Ref data.
MASTERFILE:	<CURRENT> 		LCTN 'MassFusionCoolantDisposalLocation' (001680C6)	Special Ref 'MB_MassGravelWorkshopRef' (02004C54) is not in the Special Ref data.
MASTERFILE:	<CURRENT> 		LCTN 'MassFusionCoolantDisposalLocation' (001680C6)	Warnings were encountered validating unloaded ref data for Location 'MassFusionCoolantDisposalLocation' (001680C6).

 

 

[greekrage]

Certain markers/references cant be moved safely if they are tied into other things like quests,location,packages etc...

 

You can try to delete the refrerence links to and from certain markers but you will have to set them up again in the new cell...

 

Also note you dont need or should move the map marker... You can place a xmarkerheading in the preferred cell and linkref to it (no keyword ) so basically it "deflects" to that marker.(this also known as a location marker )

 

Also...filter the warnings to "current" to get a better picture of what your mod is doing. Since the CK reports a cr@pload or warnings and errors that have nothing to do with your mod.

Edited June 17, 2022 by greekrage

[mattbeckpdx]

Thanks for replying.

 

Yeah in this case this was triggered by changing the location of the cell from MassFusionCoolantDisposalLocation to a new one in my mod for the settlement.

For example - the actual Map marker didn't move, but it's no longer in the Location it was in previously since the cell's location change.

 

Setting my new location's parent to MassFusionCoolantDisposalLocation instead of CommonwealthLocation didn't help.

And yeah, absolutely the log would be useless without filtering on Current.

With the filter off, I do see that Bethesda has variations of these same errors in their DLCs so... maybe it's safe to ignore? I just don't like introducing _new_ errors to the pile, or seeing the error warning on opening the mod in CK.

[greekrage]

Thanks for replying.

 

Yeah in this case this was triggered by changing the location of the cell from MassFusionCoolantDisposalLocation to a new one in my mod for the settlement.

 

For example - the actual Map marker didn't move, but it's no longer in the Location it was in previously since the cell's location change.

 

Setting my new location's parent to MassFusionCoolantDisposalLocation instead of CommonwealthLocation didn't help.

 

And yeah, absolutely the log would be useless without filtering on Current.

 

With the filter off, I do see that Bethesda has variations of these same errors in their DLCs so... maybe it's safe to ignore? I just don't like introducing _new_ errors to the pile, or seeing the error warning on opening the mod in CK.

If a cell is "named" and belongs to a location...AVOID using it for your settlement unless youre 100% sure that it supports full settlement options... Example : in one of my mods behind the Corvega plant i also used one of the corvega cells . In that cell vendors would not work due to the location data that the cell was tied into. The only way to fix the issue was to edit the location but in that specific location there were around 10 quests tied to it..so i couldnt risk breaking the quests and had to warn my users NOT to place vendors,jobs etc on that cell. Just checked the cell you are talking about and it has a Institute radiant quest attached to it....and i also had a mod right next to it but luckily i didnt need that cell.Either way you cant use a cell(rename it and change its location reference) if has its own location data since to create a settlement you also need to create your own "location",zone,quest that will point to a specific cell.... Even including certain cells in our build area (primitive)can cause issues...

[mattbeckpdx]

Very helpful, thanks!

[SKKmods]

I have reused existing location FortHagenRedRocket as a full registered workshop settlement which generates editor warnings, but they have never caused any issues;

See Warnings file for more information.
MASTERFILE:	<CURRENT> 		LCTN 'SKK_RRFHFortHagenRedRocketLocation' (00165595)	Special ref 'XMarkerHeading' (0023E552) no longer in location.
MASTERFILE:	<CURRENT> 		LCTN 'SKK_RRFHFortHagenRedRocketLocation' (00165595)	Special ref 'XMarkerHeading' (0023E553) no longer in location.
MASTERFILE:	<CURRENT> 		LCTN 'SKK_RRFHFortHagenRedRocketLocation' (00165595)	Special ref 'XMarkerHeading' (0023E554) no longer in location.
MASTERFILE:	<CURRENT> 		LCTN 'SKK_RRFHFortHagenRedRocketLocation' (00165595)	Special ref 'XMarkerHeading' (0023E555) no longer in location.
MASTERFILE:	<CURRENT> 		LCTN 'SKK_RRFHFortHagenRedRocketLocation' (00165595)	Special ref 'XMarkerHeading' (0023E556) no longer in location.
MASTERFILE:	<CURRENT> 		LCTN 'SKK_RRFHFortHagenRedRocketLocation' (00165595)	Warnings were encountered validating unloaded ref data for Location 'SKK_RRFHFortHagenRedRocketLocation' (00165595). 

Note: these are existing Attack, Edge and OutOfSight markers from the base game cut content workshop. I would not move structual objects like map markers and location center markers between cells without a crap load of validation testing.