This was also my first question I was coming to the forums with. But I think I solved it for us.BadLuckBurt wrote: ↑Wed Oct 16, 2019 9:02 pm...
I know the LocationId is only used when you specifically target a location in a quest but I was just wondering what would happen when two people pick the same location id for different locations?
...
So for quest actions...Hazelnut wrote: ↑Mon Oct 14, 2019 2:39 pm Locations
New locations should be named 'locationnew-LOCNAME-RR.json' where RR is the region index the new location will be in, and LOCNAME is your file name for this location. e.g. 'locationnew-archcrypt1-17.json' … A unique location index will be assigned internally when loaded in the game, and this could be different each time depending on other mods, so you cannot rely on it being a particular value and should set the corresponding data elements to zero as shown below.
...
It may be best practice then to only use LocationIndex (NOTE: not LocationId or unknown2) when dealing with DF default locations.
Code: Select all
worldupdate location at <locationIndex> in region <regionIndex> variant <variant>
Code: Select all
worldupdate locationnew named <locationName> in region <regionIndex> variant <variant>
So I assume any quest would use this name The Newarch Vaults also:
LocationIndex.txt tells us "17, 1260: The Gaerhart Vaults" so...
Code: Select all
worldupdate location at 1260 in region 17 variant <variant>
Code: Select all
worldupdate building ARCH001.RMB 1 at 1260 in region 17 variant <variant>
Then if it was a new location...
Code: Select all
worldupdate locationnew named The Newarch Vaults in region 17 variant <variant>
This is what I can sort out thus far.
I wonder if we can have two "ins:" (New Location names; "The Times We Live In" or "Where to begin")
Code: Select all
worldupdate locationnew named The Times We Live In in region 17 variant <variant>
Code: Select all
worldupdate locationnew named Where to begin in region 17 variant <variant>